What you should be able to do
- Distinguish stakeholder need, requirement and design decision.
- Identify ambiguity and missing acceptance evidence.
02 / REQUIREMENT ENGINEERING AND ANALYSIS MODELING / L07
Requirement Engineering
Requirements engineering discovers, negotiates, specifies, validates and manages change in what the system must achieve.
How do needs become requirements that can be checked?
Terms to use precisely
Common mistakes
- Treating the first request as the final requirement.
- Ignoring conflicting stakeholder goals.
Classify the statement before you model it.
A stakeholder need, a functional requirement, a quality target and a technical constraint are different things.
The system shall let a student download a generated UML revision sheet.
Choose the most accurate classification.
Ask two questions: what must the system do, and how well or under what restriction must it do it?
CHECKED LEARNING LINKS
Watch the part that solves the gap.
Each link is matched to this lesson. Start with a quick video when available. Open the full lecture when you need the academic explanation.