Solution Requirements: Features, Functions, and Product Characteristics

PMBOK v8 Definition

Solution requirements describe the features, functions, and characteristics of the product, service, or result that will meet the business and stakeholder needs. They are further grouped into functional requirements (behaviors of the product, including actions, processes, data, and interactions) and nonfunctional requirements (performance, security, and operational criteria essential for product effectiveness and user satisfaction, such as reliability, security, performance, safety, level of service, supportability, and retention/purge). This concept belongs to the Scope Management knowledge area.

Why It Matters for the Exam

The PMI exam frequently tests your ability to distinguish between requirement types, especially functional versus nonfunctional requirements. Questions appear in both multiple-choice and scenario-based formats where you must identify which category a given requirement belongs to or recognize when a requirement has been misclassified. Mastering this distinction is essential because it directly impacts scope definition, quality planning, and stakeholder satisfaction.

Key Points to Remember (for the exam)

• Three Main Requirement Categories: Business requirements (strategic objectives), Stakeholder requirements (needs of stakeholder groups), and Solution requirements (features, functions, characteristics)
• Functional vs. Nonfunctional Split: Functional = what the product does (behaviors, actions, processes); Nonfunctional = how well it performs (performance, security, reliability)
• Solution Requirements Definition: "Features, functions, and characteristics of the product, service, or result that will meet the business and stakeholder needs"
• Nonfunctional Examples: Reliability, security, performance, safety, level of service, supportability, retention/purge
• Transition and Readiness Requirements: Temporary capabilities needed to move from current state to future state (data conversion, training)
• Key Documentation Tool: Requirements traceability matrix, which links requirements to business needs, project objectives, WBS deliverables, product design, test strategy, and detailed requirements
• Requirement Quality Criteria: Unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders

Typical PMI Exam Example

A project manager is gathering requirements for a new payment processing system. Stakeholders specify that the system must process transactions within 2 seconds, maintain 99.9% uptime, and encrypt all customer data. The project manager correctly classifies these as nonfunctional requirements because they describe performance, reliability, and security criteria essential for product effectiveness, not specific product behaviors.

PMI Exam Traps

• Trap: Confusing functional requirements with nonfunctional requirements

• Reality: Functional = behaviors/actions (what the product does); Nonfunctional = performance/quality criteria (how well it does it)

• Trap: Thinking business requirements and solution requirements are the same

• Reality: Business requirements = strategic objectives and high-level organizational needs; Solution requirements = specific features, functions, and characteristics of the product

• Trap: Assuming stakeholder requirements are the same as solution requirements

• Reality: Stakeholder requirements describe needs of a specific stakeholder or group; Solution requirements describe what the product will do to meet those needs

• Trap: Overlooking transition and readiness requirements as part of requirements classification

• Reality: These are a separate category describing temporary capabilities (data conversion, training) needed for the transition from current to future state

Important PMI Connections

Quick Review Questions

1. A requirement stating "the system must support 10,000 concurrent users without performance degradation" is classified as which type of requirement?

2. What are the two subcategories of solution requirements, and what distinguishes them?

3. Which requirements classification describes temporary capabilities needed for data conversion and training?

4. What are the five quality criteria that requirements should meet before being baselined?

5. A stakeholder says "I need the system to send me an email alert when inventory drops below 100 units." Is this a functional or nonfunctional requirement?

PMBOK v8 Reference

Section 4 – Inputs and Outputs (Requirements classification and traceability matrix content)