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.
Know it well enough for the exam? Questions on Non-Functional Requirements are scenario-based, not definitional.
Practice it freeExplanation
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 plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Power Interest Grid (Power/Influence Grid)
The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.
Critical Path Method (CPM)
The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
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.
Part of
CAPM-Specific Concepts
Practice Non-Functional Requirements
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.