Home/ Majors directory/Software Engineering/Software Requirements Analysis
Software Requirements Analysis
Major: Software Engineering
Code of subject: 6.121.00.O.030
Credits: 5.00
Department: Software
Lecturer: Dr. Science, professor Hrytsiuk Yuri Ivanovych
Semester: 5 семестр
Mode of study: денна
Завдання: The study of the academic discipline involves the formation of the following competencies in the students of education:
INT: The ability to solve complex specialized tasks or practical software engineering problems characterized by complexity and uncertainty of conditions, using theories and methods of information technology.
General competences:
1) Ability to abstract thinking, analysis and synthesis (K01);
2) Ability to apply knowledge in practical situations (K02);
3) Ability to search, process and analyze information from various sources (K06);
4) Ability to work in a team (K07).
Professional competences:
1) Ability to identify, classify and formulate requirements (FC1);
2) Ability to formulate and ensure software quality requirements in accordance with customer requirements, specifications and standards (FC4);
3) Ability to adhere to specifications, standards, rules and recommendations in the professional field when implementing life cycle processes (FC5);
4) Ability to apply and develop fundamental and interdisciplinary knowledge to successfully solve software engineering tasks (FC8);
5) Ability to evaluate and take into account economic, social, technological and environmental factors affecting the field of professional activity (FC9);
6) Ability to accumulate, process and systematize professional knowledge regarding the creation and maintenance of software and recognition of the importance of lifelong learning (FC10);
7) Ability to implement phases and iterations of the life cycle of software systems and information technologies based on relevant models and software development approaches (FC11);
8) Ability to algorithmic and logical thinking (FC14).
Learning outcomes: As a result of studying the academic discipline, the student must be able to demonstrate the following learning outcomes:
1. Ability to demonstrate knowledge and understanding of the fundamentals of various approaches to the development of user and system requirements for software that relate to the area of existing problems and the area of decision-making, respectively.
2. The ability to demonstrate knowledge of the basics and methods of system modeling of various features of the subject area for which it is necessary to develop software requirements on the basis of both the general process of developing requirements and its specific cases - the area of existing problems and the area of decision-making.
3. Ability to demonstrate in-depth knowledge of the principles and methods of advanced analysis of relationships between software requirements and their attributes, which applies to different hierarchical levels of complex PS, as well as its various components.
4. The ability to develop requirements for complex software systems based on a general process with a possible combination of principles and methods of other alternative approaches.
5. Ability to use knowledge of typical methods: identification and formalization of software requirements; analysis of requirements and their coordination with interested parties; management of changes in software requirements;
6. To justify the specifics of use: different types of software requirements at different levels of software project implementation; existing methodology for verification of software requirements; modern software tools for determining and analyzing software requirements.
As a result of studying the academic discipline, the student must be able to demonstrate the following program learning outcomes:
PR05. Know and apply relevant mathematical concepts, methods of domain, system and object-oriented analysis and mathematical modeling for software development.
PR07. Know and apply in practice the fundamental concepts, paradigms and basic principles of the functioning of linguistic, instrumental and computing tools of software engineering.
PR11. Select input data for design, guided by formal requirements description and modeling methods.
PR12. Apply effective software design approaches in practice.
PR14. Apply in practice instrumental software tools for domain analysis, design, testing, visualization, measurement and documentation of software.
PR23. Be able to document and present the results of software development.
Required prior and related subjects: Introduction to software engineering
Software design
Software modeling and analysis
Software architecture and design
Software quality and testing
Management of software development projects
Summary of the subject: The discipline involves the study of basic concepts of software requirements and their analysis, some problems of developing software requirements and their management features, the structure of the general process of developing software requirements, as well as the use of system modeling for their development. Special attention is focused on the technique and principles of formulating software requirements and their analysis, on the development of user requirements in the field of existing problems and system requirements in the field of decision-making, on the use of the method of advanced analysis of requirements to display the relationships between them, as well as on the features of managing the software requirements development process.
Опис: 1. Introduction. Introduction to the discipline AVdoPZ.
2. Basic concepts of software requirements and their analysis.
3. Problems of developing software requirements.
4. The structure of the general process of developing requirements for the software system.
5. Use of system modeling to develop software requirements.
6. Peculiarities of formulating software requirements and their review.
7. Development of user requirements for software in the field of existing problems.
8. Development of system requirements for software in the area of decision-making.
9. Use of advanced analysis of relationships between software requirements.
10. Peculiarities of managing the software requirements development process.
11. Automation of the software requirements management process.
12. Rational DOORS is an effective software requirements management tool.
13. Automation of the decision-making process when analyzing software requirements.
14. Automation tools for object-oriented design of software systems.
15. Requirements engineering for software systems.
Assessment methods and criteria: 1. Oral survey in laboratory classes.
2. Control tests in laboratory classes.
3. Protection of laboratory works.
4. Examination control (written component (tests), oral component).
Критерії оцінювання результатів навчання: 1. Laboratory works - 35 points
2. Control tests in laboratory classes - 10 points
Total for PC – 45 points
Examination control:
1) written component (tests) – 50 points
2) oral component – 5 points
A total of 100 points per discipline.
Порядок та критерії виставляння балів та оцінок: 100–88 points – (“excellent”) is awarded for a high level of knowledge (some inaccuracies are allowed) of the educational material of the component contained in the main and additional recommended literary sources, the ability to analyze the phenomena being studied in their interrelationship and development, clearly, succinctly, logically, consistently answer the questions, the ability to apply theoretical provisions when solving practical problems; 87–71 points – (“good”) is awarded for a generally correct understanding of the educational material of the component, including calculations, reasoned answers to the questions posed, which, however, contain certain (insignificant) shortcomings, for the ability to apply theoretical provisions when solving practical tasks; 70 – 50 points – (“satisfactory”) awarded for weak knowledge of the component’s educational material, inaccurate or poorly reasoned answers, with a violation of the sequence of presentation, for weak application of theoretical provisions when solving practical problems; 49-26 points - ("not certified" with the possibility of retaking the semester control) is awarded for ignorance of a significant part of the educational material of the component, significant errors in answering questions, inability to apply theoretical provisions when solving practical problems; 25-00 points - ("unsatisfactory" with mandatory re-study) is awarded for ignorance of a significant part of the educational material of the component, significant errors in answering questions, inability to navigate when solving practical problems, ignorance of the main fundamental provisions.
Recommended books: 1. ENMK in the discipline "Analysis of software requirements" certificate № 02539, registration number and date E41-163-151 / 2021 from 28.06.2021. Available from: https://vns.lpnu.ua/course/view. php? id = 8633
2. Hrytsiuk Yu.I. Analysis of software requirements: textbook. manual / Y.I. Hrytsiuk. – Lviv: Lviv Polytechnic National University Publishing House, 2018. – 456 p.
3. Hrytsiuk Yu.I. IEEE Software Requirements Guidelines: Textbook manual. Lviv: Lviv Polytechnic National University Publishing House, 2018. – 160 p.
4. Analysis of software requirements: guidelines for laboratory work in the discipline for students in the direction of training 6.050103 "Software Engineering" / Encl .: O.Ye. Bilas, NB Melnyk - Lviv: Lviv Polytechnic National University Publishing House, 2018. – 70 p.
5. Wigers K. Development of software requirements: per. from EnglishMoscow: Publishing and trading house "Russian Edition", 2004. – 576 p.
6. Wigers K., Beatty D. Development of software requirements: per. from English - 3rd ed., Add. – M.: Publishing and trading house "Russian Edition"; SPb .: BHV-Petersburg, 2014. – 736 p.
7. Koburn A. Modern methods of describing functional requirements for systems. – M.: Lori, 2002. – 263 p.
8. Coburn Alistair. Modern methods of describing functional requirements for systems (Writing Effective Use Cases): per. from English E. Borisova. – M.: OZON Status, 2012. – 264 s
9. Kornipaev Ilya. Requirements for software. Recommendations for collection and documentation. – M.: OZON Status, 2013. – 118 p.
10. Hull Elizabeth, Jackson Ken, Dick Jeremy. Requirements development and management. Practical user guide: per. Ilya Kornipaev. – 2nd ed. – M.: Telelogic. – 2005. – 229 p.
11. Kroll P., Krachten F. Rational Unified Process is easy. RUP Practitioners' Guide: trans. from EnglishMoscow: KUDITS-OBRAZ, 2004. – 432 p.
12. Laffingwell D., Widrig D. Principles of working with software requirements: Unified approach: per. from EnglishMoscow: Izd. house Williams, 2002. – 448 p.
12. Somerville Ian. Software Engineering: per. from English - 6th ed. – M.: Izd. house Williams, 2002. – 624 p.
13. Standard for Software Verification and Validation Plans (ANSI / IEEE standard 1012-1986).
Уніфікований додаток: Lviv Polytechnic National University ensures the realization of the right of persons with disabilities to obtain higher education. Inclusive educational services are provided by the Service of accessibility to learning opportunities "Without restrictions", the purpose of which is to provide permanent individual support for the educational process of students with disabilities and chronic diseases. An important tool for the implementation of the inclusive educational policy at the University is the Program for improving the qualifications of scientific and pedagogical workers and educational and support staff in the field of social inclusion and inclusive education. Contact at:
St. Karpinsky, 2/4, 1st floor, room 112
E-mail: nolimits@lpnu.ua
Websites: https://lpnu.ua/nolimits https://lpnu.ua/integration
Академічна доброчесність: The policy regarding the academic integrity of the participants of the educational process is formed on the basis of compliance with the principles of academic integrity, taking into account the norms "Regulations on academic integrity at the Lviv Polytechnic National University" (approved by the academic council of the university on June 20, 2017, protocol No. 35).