It is assumed that, unless otherwise stated, all techniques are applied to software/systems with baselined requirements. Non-functional requirements should be defined as early as possible in the software development life cycle.
Unless otherwise stated, all techniques in this standard are applicable to the testing of both newly-developed software/systems and operational software/systems.Guidelines are available, which provide background information on these techniques.
Examples of the application of the definitions can be accessed directly via the domain-technique matrix.
The following non-functional testing techniques have been identified. Choose the technique that you wish to see the definition for:
| Definitions are available for those techniques shown in green. |
| Definitions requiring review are shown in yellow. |
|
Techniques shown in red are currently undefined. If you can provide a definition, please contact the working party through the Feedback Form |