Non Functional Requirement Document

Non Functional Requirement Document

Purpose of NFR Document:

The purpose of the NFR document is to collect, analyse and finalise the requirement for performance testing. The project team (or client) provides the non-functional requirement, may be in the layman term. A performance tester gathers all the basic and required information regarding non-functional test and then prepares a non-functional requirement document. This document provides a quantitative NFRs which helps to build a correct workload model during the scenario creation phase.

When to prepare?

NFR gathering activity starts just after the successful completion of the risk assessment. A performance tester finalises the scope of performance testing during the risk assessment and then starts gathering the non-functional requirements against the in-scope components. Non-Functional Requirement Gathering phase comes at second place in the Performance Testing Life Cycle. A performance tester gets all the NFRs from the project/client and converts them into the testable NFRs. Once the requirements are clear then the next phase i.e. Performance Test Planning can be started.

Who does prepare?

Performance Test Manager or Lead has a responsibility to collect, analyse and finalise the non-functional requirements.

NFR Document Template:

The performance testing non-functional requirement document template is available here.


Leave a Reply

Your email address will not be published. Required fields are marked *