CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities

Non-functional requirements specify quality attributes: how well the system performs its functions. Examples: 'The system must respond within 2 seconds' (performance), 'Data must be encrypted at rest' (security). They constrain solution design.

**Why not A:** Non-functional requirements are critically important and cannot be ignored. Neglecting NFRs is a leading cause of solution failure — a system that meets all functional requirements but is too slow, insecure, or unavailable under load fails to deliver acceptable business value. The term "non-functional" refers to quality attributes, not to unimportance.

**Why not B:** Non-functional requirements are not optional enhancements — they are mandatory constraints on how the solution must perform. Security requirements, performance thresholds, and availability targets are baseline expectations that the solution must satisfy, not nice-to-have features that can be deferred or skipped without consequence.

**Why not C:** The classification of a requirement as functional or non-functional is determined by what the requirement specifies — whether it describes a system behavior (functional) or a quality attribute (non-functional) — not by who submitted it. Requirements from non-users can be either functional or non-functional depending on their content.