|
1 |
Discipline name |
Applied systems analysis |
|
2 |
Year of study, |
2, |
|
3 |
Semester of study |
4 |
|
4 |
Number of credits |
2 |
|
5 |
Lecturer |
Kiryl Atrokhau |
|
6 |
Study objectives |
Obtain knowledge and practical skills required to elicit, gather, design and prototype requirements for IT products as well as work as business analyst in software development teams |
|
7 |
Prerequisites |
None |
|
8 |
Discipline contents |
IT product. Business models. Foundations of systems engineering. Lifecycle of systems and products. Classification of IT companies. Software. Software development methodologies. Waterfall, Agile, Scrum, Lean. Team roles. Systems analyst and business analyst. Principles of business analysis. Software requirements. Requirements elicitation and gathering. Stakeholders. Types of requirements. Use cases. User stories. Prototypes. Requirements specification. Requirements managements and tools. |
|
9 |
Recommended readings |
1. BABOK Guide (Version 3) 2. Wiegers K., Beatty J. Software requirements 3. Yayici E. Business analysis methodology book (Kindle edition) 4. Robertson S., Robertson J. Mastering the Requirements process: Getting requirements right 5. Leffingwell D. Agile software requirements: Lean requirements practices for teams, programs, and the enterprise |
|
10 |
Format |
Lectures, seminars, labs, distance learning |
|
11 |
Teaching languages |
Russian |
|
12 |
Forms of assessment |
Labs and computer tests |
|
13 |
Grading |
Credit |