Having solid NFR (Non Functional Requirements) makes the difference between successful business IT projects and IT disasters. Below a list of NFR requirements that are ready to be (re)used within your project:

 

A test specification for the system must be available
Name of REQA test specification for the system must be available
TypeBusiness Requirement
despcriptionA test specification for the system must be available in order to perform test of the created system.
PriorityCould
Tag(s)Documentation, NFR
Data logging:Sensitive data is not logged in clear text by the application.
Name of REQData logging:Sensitive data is not logged in clear text by the application.
TypeImplementation
despcriptionSensitive data is not logged in clear text by the application.
PriorityCould
Tag(s)NFR, Security
Database connections, passwords, keys, or other secrets are not stored in plain text.
Name of REQDatabase connections, passwords, keys, or other secrets are not stored in plain text.
TypeBusiness
despcriptionDatabase connections, passwords, keys, or other secrets are not stored in plain text.
PriorityCould
Tag(s)NFR, Security
Disaster Recovery
Name of REQDisaster Recovery
TypeBusiness Requirement
despcriptionThe solution will be configured to be split across the two data centers where possible with failover from data center to data center in the event of a disaster, In addition, each data center needs to be able to run in a self sufficient manner should it become isolated from the other.
PriorityCould
Tag(s)NFR
Documentation must be available in an open document format
Name of REQDocumentation must be available in an open document format
TypeSystem Requirement
despcriptionAll system documentation must be made available in open document format. System documentation is (not exhausted) operational manuals, code documentation, test specs and test reports, installation manuals.
PriorityCould
Tag(s)Documentation, NFR
High Availability
Name of REQHigh Availability
TypeBusiness Requirement
despcriptionAll components should be configured in a high availability configuration to eliminate single points of failure, and minimize solution outages.
PriorityCould
Tag(s)NFR
Maintainability
Name of REQMaintainability
TypeBusiness Requirement
despcriptionThe system should allow for easy software upgrades with minimal outage. The outage should be restricted to no longer than one day, and allow for the use of a back up system for service continuity while the upgrade the taking place.
PriorityCould
Tag(s)NFR
Maintainability
Name of REQMaintainability
TypeSystem Requirement
despcriptionAny solution must be maintainable by the affected maintenance team, both initially and throughout its lifecycle. Unnecessary complexity in maintenance, such as by requiring additional / unusual skills or tools or having a complex solution design, adds risk to the solution’s supportability and must be justified.
PriorityCould
Tag(s)maintainability, NFR
Manageability
Name of REQManageability
TypeSystem Requirement
despcriptionAll solutions must be managed throughout their lifecycle, including startup, shutdown, backup, updates, security / permission changes, etc. Administrators and support personnel must be able to conduct such routine activities effectively in order to ensure that the solution does not incur excessive cost or experience unnecessary outages.
PriorityCould
Tag(s)manageability, NFR
Minimize Footprint
Name of REQMinimize Footprint
TypeBusiness Requirement
despcriptionStack multiple components within single operating system instances where possible to minimize both the number of physical and virtual servers required to run the solution.
PriorityCould
Tag(s)NFR
Service levels
Name of REQService levels
TypeSystem Requirement
despcriptionThe required service level(s) for any solution affect its design, cost, maintenance and support. As such, these must be known.
PriorityCould
Tag(s)NFR, service levels
Supportability
Name of REQSupportability
TypeIT Requirement
despcriptionAny solution must be supportable by the affected operations and maintenance teams, both initially and throughout its lifecycle. Unnecessary complexity in support, such as by requiring additional / unusual skills or tools, adds risk to the solution’s supportability and must be justified. The maintenance support team will be responsible for the success of the solution during its production life. As such, they require training, mentoring and appropriate transition measures to ensure they are able to successfully support the new component in the production environment.
PriorityCould
Tag(s)NFR, supportability
The certificate must be an X.509v3 certificate
Name of REQThe certificate must be an X.509v3 certificate
TypeBusiness
despcriptionThe certificate must be an X.509v3 certificate. The certificate must be within the valid period. The certificate must be verified and validated through authentication. The system will not issue digital certificates. Users will present trusted third party-issued certificates that are valid and verifiable by the system.
PriorityCould
Tag(s)NFR, Security
User ID must be unique and passwords must be stored in irreversible encrypted form
Name of REQUser ID must be unique and passwords must be stored in irreversible encrypted form
TypeBusiness
despcriptionUser ID must be unique. Passwords must be stored in irreversible encrypted form, and the password file cannot be viewed in unencrypted form. A password must not be displayed on the data entry/display device. Passwords must be at least eight characters long. Passwords must be composed of at least three of the following: English uppercase letters, English lowercase letters, numeric characters, and special characters. Password lifetime will not exceed 60 days Users cannot use the previous six passwords. The system will give the user a choice of alternative passwords from which to choose. Passwords must be changed by the user after initial logon.
PriorityCould
Tag(s)NFR, Security
NFR Requirements list