Performance Testing - Example Performance-related NFRs
Performance test requirements are established to define the parameters within which a system operates; these are identified collaboratively by programs and the organization.
They must be relevant, specific, testable, and measurable.
An example set of NFRs could include:
| Area | Title | Description | Examples |
|---|---|---|---|
| Capacity | Capacity Growth | The projected base volume of data stored within the database is anticipated to be XX at the end of year XXXX. This is expected to increase by the following amounts over the following X years: • End of Year X: Base + X% • End of Year X: Base + X% • End of Year X: Base + X% The system should be sized to cope with the end of year X volumes from the outset. |
The projected base volume of data stored within the database is anticipated to be X TB at the end of 2025. This is expected to increase by the following amounts over the next 3 years: • End of Year 2026: Base + 31% • End of Year 2027: Base + 11% • End of Year 2028: Base + 7% The system should be sized to cope with the end of year 3 volume from the outset. |
| User population | Total expected user size | The registered user base is anticipated to be X users during year XXXX with growth of X% year on year until year XXXX. The system should be sized to meet with the end of year X volumes from the outset. | The anticipated user base in year 2025 is expected to be 2,700 with growth of 5% year on year until 2027. The system should be sized to cope with the end of year 2027 growth from the outset. |
| User population | Anticipated number of concurrent users during peak usage times | The system should be able to service XXX currently authenticated users whilst still meeting the screen responsiveness NFRXXX. This should be achievable with the database volumes equivalent to year XXXX. e.g. The system should be able to service 275 currently authenticated users whilst still meeting the screen responsiveness requirements NFR045. This should be achievable with the database volumes equivalent to year 2027 predictions. |
The system should be able to service 275 currently authenticated users whilst still meeting the screen responsiveness NFR045. This should be achievable with the database volumes equivalent to end of year 2027. |
| Responsiveness | Screen Response Times | Transaction response times should be no greater than X seconds at the X percentile when: • experiencing peak hour transactional load of XXXX total volume • peak concurrent users are as per NFR045 • database data volumes are equivalent to year XXXX predictions |
Transaction response times should be no greater than 3 seconds at the 95th percentile when: • experiencing peak hour transactional load of 8,500 (model equivalent predictions) • concurrent system users are as per NFR045 • database data volumes are equivalent to end of year 2027 predictions OR Transaction response times should be no greater than 1 second at the 95th percentile when: • experiencing peak day transactional load of 20,500 (volume predictions) • concurrent system users are as per NFR045 • database data volumes are equivalent to end of year 2027 predictions |
| Responsiveness | Completion Times | The ETL job XXXXXXX should, from the point of 1. criteria 1 2. criteria 2 3. criteria 3 |
The ETL job • whichever system is used for the patient ID should be predicted for the year end 2027 volumes • patient tracking audit file received during the peak hour • database data volumes are equivalent to end of year 2027 predictions |
Published: 27 February 2026
Last updated: 17 March 2026
Page Source