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.
Know it well enough for the exam? Questions on Functional Requirements are scenario-based, not definitional.
Practice it freeExplanation
Functional requirements specify the actions, processing, and outputs a solution must deliver. They describe the "what" of the solution in concrete, observable terms. Examples include user authentication workflows, calculation rules, data entry validations, report generation capabilities, and notification triggers.
Functional requirements are typically documented using techniques such as use cases, user stories, process flows, and requirements specification documents. Each functional requirement should be written so that it can be independently verified through testing. A well-written functional requirement follows a structured format, such as "The system shall [perform action] when [condition] so that [benefit]."
On the CAPM exam, you need to distinguish functional requirements from non-functional requirements clearly. Functional requirements describe observable behavior and features. If a requirement describes what the system does in response to an action, it is functional. If it describes how well the system performs or a quality constraint, it is non-functional.
Key Points
- •Describe what the solution must do in terms of features, behaviors, and processing
- •Documented through use cases, user stories, and requirements specifications
- •Must be independently testable with clear acceptance criteria
- •A subcategory of solution requirements along with non-functional requirements
Exam Tip
If the requirement describes an action the system performs (e.g., "calculate," "generate," "send"), it is functional. If it describes a quality attribute (e.g., "within 2 seconds," "99.9% uptime"), it is non-functional.
Frequently Asked Questions
Related Topics
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.
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.
Elicitation Techniques (Business Analysis)
Elicitation techniques are structured methods used by business analysts to gather requirements and information from stakeholders, including interviews, workshops, observation, surveys, document analysis, prototyping, and brainstorming.
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 Functional Requirements
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.