|
1 |
Introduction to software requirements engineering. Definitions, levels, and types of requirements (business, user, functional, non-functional). Product vs. project requirements.
|
|
2 |
Requirements from the customer''s perspective. The expectation gap, customer–developer partnership, Requirements Bill of Rights and Responsibilities.
|
|
3 |
Good practices for requirements engineering. The business analyst role, essential analyst skills and knowledge.
|
|
4 |
Establishing business requirements. Vision and scope document, business objectives, success metrics, scope representation techniques (context diagram, feature tree, event list).
|
|
5 |
Finding the voice of the user. User classes, user personas, product champions, and connecting with user representatives.
|
|
6 |
Requirements elicitation techniques: interviews, workshops, focus groups, observations, questionnaires, document analysis, and system/user interface analysis.
|
|
7 |
Understanding user requirements. Use cases, user stories, and business rules. Classifying and documenting customer input.
|
|
8 |
Midterm exam.
|
|
9 |
Software requirements specification (SRS). Documenting functional requirements, writing quality requirements, SRS templates and conventions.
|
|
10 |
Requirements analysis and modeling. Data flow diagrams, entity-relationship diagrams, state-transition diagrams, dialog maps.
|
|
11 |
Prototyping, quality attributes (usability, performance, security, reliability), and specifying non-functional requirements.
|
|
12 |
Requirements validation and verification. Reviews, inspections, walkthroughs, acceptance criteria, and testing requirements.
|
|
13 |
Requirements management. Baselining, version control, requirements attributes, and managing scope creep.
|
|
14 |
Change management and traceability. Change control process, change control board, requirements traceability matrix, RE tools, and risk management.
|
|
15 |
Final exam.
|
|
16 |
|
|
17 |
|
|
18 |
|
|
19 |
|
|
20 |
|