Available under Creative Commons-ShareAlike 4.0 International License.
The formulation of quality requirements (performance, reliability, usability, flexibility...) should also be testable. This implies most often that you set a measurable, numeric goal, for example: “The system must be available to end users at least 98% of the time in any given week.” This cannot necessarily be tested directly before the system goes live. However, you r design must include a way to keep track of whether the performance objective is being met.
The Software Engineering Institute has developed an entire design methodology driven by quality requirements that explains this process in detail (reference required).
- 1264 reads
