because of the discipline the student has
– Know:
- types of requirements for software;
- methods to identify and formalize requirements the software;
- methodology verification requirements;
- requirements analysis methods and their coordination;
- methods managerial of risks.
– Be able to:
- the sources of requirements for software;
- functional distinguish neither not functional requirements for software;
- allocate requirements of quantitative and qualitative assessment;
- enter contradiction between the requirements of the software and to resolve conflicts between customers and software developers;
- develop data requirements for software;
- perform verification and certification requirements for software;
- to analyze the requirements for the software;
- use modern software to perform tasks on the software requirements analysis;
- use software to track and manage software requirements.
– Be able to present research results advanced analysis requirements software to display the connections between them and justify their conclusions.
– Have an idea the main directions of development and prospects of practical application requirements and software features of the analysis.

- Fundamentals of software engineering.
- Group dynamics and communication.
- Configuration management.
- Documentation requirements for software.
- The quality of the software.
- Project management in IT-industry

Introduction. Basic concepts of requirements software and the analysis. 1) The problem of development requirements software and management features. 2) The structure of the overall development process requirements software system. 3) Use of system modeling to develop requirements software. 4) Engineering and principles of writing requirements software and analysis. 5) Develop custom requirements software in these problems. 6) Develop system requirements Software in decision-making. 7) Using advanced analysis to show the links between requirements software. 8) features development process management requirements software. 9) Automation of management requirements software. 10) DOORS – an effective tool for managing requirements software. 11) Automate decision-making process in the analysis of requirements software. 12) Automation of object-oriented design software system.

1. Hrytsiuk Ju.I. Analiz vymoh do prohramnoho zabezpecennia : navc. posibn. / Ju.I. Hrytsiuk. – Lviv : Vyd-vo NU "Lvivska politechnika", 2016. – 500 s.
2. Vigers K. Razrabotka trebovaniy k programmnomu obespecheniyu : per. s angl. – M. : Izd.-torg. dom "Russkaya Redaktsiya", 2004. – 576 s.
3. Vigers K., Bitti D. Razrabotka trebovaniy k programmnomu obespecheniyu : per. s angl. – Izd. 3-e, [pererab. i dop.]. – M. : Izd.-torg. dom "Russkaya Redaktsiya"; SPb. : BHV-Peterburg, 2014. – 736 s.
5. Kobern Alister. Sovremennyie metodyi opisaniya funktsionalnyih trebovaniy k sistemam (Writing Effective Use Cases) : per. s angl. E. Borisova. – M. : OZON Status, 2012. – 264 s.
5. Kroll P., Krachten F. Rational Unified Process – eto legko. Rukovodstvo po RUP dlya prakti-kov : per. s angl. – M. : KUDITs-OBRAZ, 2004. – 432 s.
6. Leffinguell D., Uidrig D. Printsipyi rabotyi s trebovaniyami k programmnomu obespeche-niyu: Unifitsirovannyiy podhod : per. s angl. – M. : Izd. dom "Vilyams", 2002. – 448 s.
7. Sommervill Ian. Inzheneriya programmnogo obespecheniya : per. s angl. – Izd. 6-oe, [pere-rab. i dop.]. – M. : Izd. dom "Vilyams", 2002. – 624 s.
8. Kornipaev Ilya. Trebovaniya dlya programmnogo obespecheniya. Rekomendatsii po sboru i do-kumentirovaniyu. – M. : OZON Status, 2013. – 118 s.
9. Hall Elizabet, Dzhekson Ken, Dik Dzheremi. Razrabotka i upravlenie trebovaniyami. Prak-ticheskoe rukovodstvo polzovatelya: per. Ilya Kornipaev. – Izd. 2-oe, [pererab. i dop.]. – M. : Telelogic, 2005. – 229 s.
10. Standard for Software Verification and Validation Plans (ANSI / IEEE standard 1012-1986. [Electronic resource]. – Mode of access http://standards.ieee.org/findstds/standard/1012-1986.html

- current control (45%): Reports of laboratory work, test papers;
- final control (55% of exam).