Subject
Analysis of software requirements
| 1. | Course Title |
Analysis of software requirements Software requirements analysis |
||||||||||||
| 2. | Code | F18L2S002 | ||||||||||||
| 3. | Study Programme | Software Engineering and Information Systems | ||||||||||||
| 4. | Organizer of the study programme (unit, institute, department or division) | Faculty of Computer Science and Engineering | ||||||||||||
| 5. | Degree level (first, second, third cycle) | First Cycle | ||||||||||||
| 6. | Academic year / semester | 4 / Summer | ||||||||||||
| 7. | Number of ECTS credits | 6 | ||||||||||||
| 8. | Teacher | — | ||||||||||||
| 9. | Prerequisites for enrolling in the course | Object-Oriented Analysis and Design or Software Engineering | ||||||||||||
| 10. | Objectives of the course programme (competences) | Upon completion of the course, the student is expected to understand and have in-depth knowledge in the application of techniques for extracting knowledge from the client, to understand techniques for documenting software and business requirements, to understand and has in-depth knowledge in the application of change management techniques for software and business requirements. |
||||||||||||
| 11. | Course content | Defining requirements (e.g., product, project, constraints, system boundaries, external and internal) Requirements Engineering Process Layers/levels of requirements (e.g., needs, goals, user requirements, system requirements, and software requirements) (1) Requirements characteristics (for example, testability, unambiguous, consistent, accurate, traceability, and priority) (1) Analysis of the quality (nonfunctional) requirements (for example, safety, security, usability, and performance) (1) Software Requirements in the Context of Systems Engineering Evolution of requirements, tracking, prioritization, trade-off analysis, risk analysis, and impact analysis (1) Requirements management (for example, consistency management, release planning, and reuse), Interaction between requirements and architecture Requirement elicitation, sources for extraction (e.g., stakeholders, domain experts, and operational and organizational environments), elicitation techniques (for example, interviews, questionnaires/surveys, prototypes, use cases, observation, and participation techniques) (1) Requirements specification and documentation, basis for requirements documentation (e.g., types, purpose, structure, quality, attributes, and standards) (1) Techniques for specifying software requirements (e.g., requirements documentation for plans, decision tables, user stories, and behavioral specifications) (1) Requirements validation, reviews and inspections, prototyping to confirm the requirements (1) Design for acceptance testing, verification of product quality attributes, analysis of requirements interaction (e.g., functional interaction), analysis of formal requirements |
||||||||||||
| 12. | Learning methods | Lectures supported by slide presentations, interactive lectures, exercises (using equipment and software packages), teamwork, case studies, guest lecturers, independent preparation and defense of a project assignment and seminar paper, learning in an electronic environment (forums, consultations). | ||||||||||||
| 13. | Total available time | 6 ECTS x 30 hours = 180 hours | ||||||||||||
| 14. | Distribution of available time | 30 + 45 + 15 + 15 + 75 = 180 hours | ||||||||||||
| 15. | Forms of teaching activities |
|
||||||||||||
| 16. | Other forms of activities |
|
||||||||||||
| 17. | Assessment method |
|
||||||||||||
| 18. | Grading criteria (points / grade) |
|
||||||||||||
| 19. | Requirement for obtaining a signature and taking the final exam | Regular class attendance (up to 3 absences), timely submission of all homework assignments, seminar papers, forum discussions, and the project. | ||||||||||||
| 20. | Language of instruction | Macedonian and English | ||||||||||||
| 21. | Method for monitoring the quality of teaching | internal evaluation and survey mechanism | ||||||||||||
| 22. | Literature |
|
