How to read and document requirements
Requirements follow the SMART principle. SMART is an acronym that aims to make requirements clear and testable.
A (Attainable or Achievable)
T (Time-bound, Traceable or Testable, literature differs here)
To document SMART non-functional or quality requirements, we describe them in scenarios that follow a certain structure.
Who (user or system) triggers an event?
What happens, what is the event?
Where does it happen?
What system component is involved?
What is the response from the system?
- Response measure
How is the response measured? It should be a number, but a clear
nois also acceptable.
Quality requirements are categorized into eight different characteristics as standardized in ISO 25010.
Imagine yourself being a tester of APPUiO Cloud and you would like to do a quality examination. How would you test and verify the requirements? Writing down those requirements in form of scenarios help to make them measurable or verifiable.