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

Requirements attributes are metadata: priority (MoSCoW), source (which stakeholder), status (proposed/approved/implemented), stability (how likely to change), complexity (high/medium/low). These attributes support filtering, impact analysis, change management, and stakeholder communication.

**Why not A:** Technical specification attributes attached to coded features describe implementation metadata, not requirements attributes. Requirements attributes are metadata about the requirements themselves, such as priority, source, status, and stability, used for tracking and management throughout the requirements lifecycle.

**Why not B:** The grammatical parts of a requirements sentence describe linguistic structure, not requirements attributes. Requirements attributes are metadata fields associated with each requirement that support management activities like filtering, impact analysis, and change control.

**Why not C:** Formatting guidelines for requirements documents describe document standards, not requirements attributes. Requirements attributes are information fields like priority, source, status, and complexity that are tracked alongside each requirement to support management, communication, and decision-making.