| author | title |
|---|---|
Neil Ernst |
Requirements Analysis topics |
Analysis and modelling are the phases of the RE lifecycle where we start trying to understand what we have learned and putting it into written or diagrammatic form. Software Verification and Validation (V&V) is the process of ensuring that
- The software being developed or changed will satisfy functional and other requirements (validation) and
- Each step in the process of building the software yields the right products (verification)
- Characterize the relevance of requirements analysis and where it sits in the lifecycle.
- Demonstrate capability in different modelling and analysis techniques like social models, use case models, data flow diagrams, and UI models.
- Apply these models to the project.
- Differentiate between modelling approaches and analysis outcomes in order to prioritize requirements.
- Appreciate the difference between validation and verification.
- Identify V&V activities and where in the software lifecycle the occur.
- Apply formal methods when appropriate.
| # | Topic | Readings | Exercises |
|---|---|---|---|
| 3-1 | Prioritization | Text, Ch 16 | Kano/Food Apps |
| 3-2 | Early RE | Horkoff Kids Help Phone slides - look at Lectures/3_Modeling2.pdf | SD models |
| 3-3 | Data modeling | 12 (up to DFDs), 13 (up to reports) | Sketch out entities and relationships in project |
| 3-4 | Traceability, Change Management, and Reuse | chapter 28, 29 | |
| 3-5 | Feasibility Analysis | ||
| 3-6 | RE in practice: embedded systems | state diagram for course registration |