Non-Functional Requirements Analysis
Requirements structure – (From BABOK® Guide v2.0)
- Business Requirements
- Stakeholder Requirements
- Solution Requirements
- Functional Requirements
- Non-functional Requirements
- Transition Requirements
What Are Non-Functional Requirements?
Capture conditions that do not directly relate to the behavior or functionality of the solution Instead, they describe environmental conditions under which the solution must remain effective or qualities that the systems must have Quality or supplementary requirementsCan include requirements related to:
- Capacity
- Speed (Response time, Throughput)
- Security
- Availability
- Scalability
- … and more
What Is Requirements Analysis?
Describes how business analysts prioritize and progressively elaborate stakeholder and solution requirements in order to enable the project team to implement a solution that will meet the needs of the sponsoring organization and stakeholders- Includes non-functional requirements
- Includes non-functional requirements
What Is Non-functional Requirements Analysis?
BABOK® Guide v2.0, section 9.17The purpose of non-functional requirements is to describe the required qualities of a system, such as its usability and performance characteristics. These supplement the documentation of functional requirements, which describe the behavior of the system.
Categories (ISO 9126)
- Reliability
- Performance Efficiency
- Operability
- Security
- Compatibility
- Maintainability
- Transferability
- Include one or more measures of success
- How do we know we met the requirement
- Requires to adequately test requirement
- The system shall …
Importance – Why Bother?
Essentially describe the target quality of the system, so …Missing non-functional requirements (missing quality) impacts every functional requirement
- Could affect adoption
- Could be compliance issues
- Careful! Too much could impact time and cost
- Could be done by System Analysts
