Non-Functional - Introduction
Last Updated on Tuesday, 13 April 2010 10:52 Written by Phil Bailey Monday, 12 April 2010 21:02
Purpose of the Template
The purpose of the template is to provide a framework to enable the capturing of non-functional requirements for a new system or to define additional non-functional requirements for a change to an existing system.
In what circumstances should you use the templates?
Non-functional requirements should always be defined for an IT system. It is highly recommended that where you are defining a new IT system that you define a full set of non-functional requirements.
It is also recommended that if you are introducing new functionality to an existing system that you define the appropriate subset of non-functional requirements that relate to the change you are making (for example if you are not adding new roles to the system then do not define any security requirements).
Where no non-functional requirements have ever been defined for a system then defining non-functional requirements for a change can be problematic. This is especially the case because defining, updating the system to make it compliant and testing the non-functional requirements for a whole system does add a lot to the budget for a small change project! At the end of the day it is down to your powers of persuasion
What information does the template allow you to capture?
Both templates have been designed to capture the following requirement types:
- Security Requirements
- Reliability Requirements
- Performance Requirements
- Maintenance Requirements
- Online user Documentation and Help Requirements
- Legal and Compliance requirements
- Interface Requirements