What you should be able to do
- Classify common quality attributes.
- Rewrite vague statements into testable requirements.
- Explain trade-offs between qualities.
02 / REQUIREMENT ENGINEERING AND ANALYSIS MODELING / L14
Non-Functional Requirements
Non-functional requirements constrain how well the system must work. They need a measure, target and condition.
How do you make a quality expectation measurable?
Terms to use precisely
Common mistakes
- Writing “fast”, “secure” or “user friendly” without a measure.
Turn “good” into something testable.
A quality requirement needs an attribute, a measure, a target and the condition under which it matters.
TESTABLE REQUIREMENT
The system shall meet performance by keeping response time at 3 seconds for 95% of requests during peak revision week.
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.
WATCH FIRSTquick video
Functional and Non-Functional Requirements: Understand the Difference in Software Development
Separate system behaviour from measurable quality constraints using examples.
GO DEEPERfull lecture
Lecture 15: Introduction to requirement specification
Use the broader lecture when you need requirements specification context.