Non-Functional Requirements
Non-functional requirements describe the quality attributes, constraints, and performance standards a solution must meet, specifying how well the system should perform rather than what it should do.
Explanation
Non-functional requirements define the conditions under which a solution must operate and the quality standards it must achieve. They address attributes such as performance (response time, throughput), reliability (uptime, mean time between failures), scalability (concurrent users, data volume), security (authentication, encryption), usability (accessibility, learnability), and maintainability.
These requirements are often more difficult to elicit than functional requirements because stakeholders may assume certain quality levels without explicitly stating them. The business analyst must proactively ask about performance expectations, security constraints, compliance requirements, and scalability needs. Non-functional requirements are typically documented alongside functional requirements but may also appear in a separate quality requirements section.
Non-functional requirements are critical because they significantly impact solution architecture and design decisions. A system that meets all functional requirements but fails non-functional ones (such as being too slow or unreliable) will not satisfy stakeholders. On the CAPM exam, you must be able to identify non-functional requirements and distinguish them from functional ones.
Key Points
- •Cover quality attributes: performance, reliability, scalability, security, usability, and maintainability
- •Describe how well the system performs, not what it does
- •Often implicit and must be proactively elicited from stakeholders
- •Significantly impact architecture and design decisions
Exam Tip
Non-functional requirements describe qualities and constraints. Look for keywords like "within X seconds," "99.9% availability," "support N concurrent users," or "comply with [standard]" to identify them.
Frequently Asked Questions
Related Topics
Functional Requirements
Functional requirements describe the specific behaviors, features, and capabilities a solution must provide, defining what the system should do in response to inputs or conditions.
Solution Requirements
Solution requirements describe the characteristics, features, and capabilities that a solution must possess to meet business and stakeholder requirements. They are divided into functional and non-functional requirements.
Stakeholder Requirements
Stakeholder requirements describe the needs of individual stakeholders or stakeholder groups, including what they need the solution to do for them in order to meet the business requirements.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Burndown Chart
A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.
Resource Leveling
Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Stakeholder Mapping
Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Cost Performance Index (CPI)
Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.
Schedule Performance Index (SPI)
Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.
Earned Value Management (EVM)
Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.
Power/Influence Grid
The power/influence grid is a stakeholder classification model that groups stakeholders based on their level of authority (power) and their active involvement or ability to affect the project (influence).
Part of
CAPM-Specific Concepts
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.