5.2.3.1 Requirements Documentation
Requirements documentation describes how individual requirements meet the business need for the project.
Requirements may start out at a high level and become progressively more detailed as more about the requirements is known. Before being baselined, requirements need to be unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders. The format of a requirements document may range from a simple document listing all the requirements categorized by stakeholder and priority, to more elaborate forms containing an executive summary, detailed descriptions, and attachments.
Components of requirements documentation can include, but, are not limited to:
Business requirements, including:
Business and project objectives for traceability;
Business rules for the performing organization; and
Guiding principles of the organization
• Stakeholder requirements, including:
Impacts to other organizational areas;
Impacts to other entities inside or outside the performing organization; and Stakeholder communication and reporting requirements.
• Solution requirements, including:
Functional and nonfunctional requirements;
Technology and standard compliance requirements;
Support and training requirements;
Quality requirements; and
Reporting requirements, etc. (solution requirements can be documented textually, in models, or both).
Project requirements, such as:
Levels of service, performance, safety, compliance, etc.; and
Acceptance criteria.
Transition requirements.
Requirements assumptions, dependencies, and constraints.

Impacts to other organizational areas, levels of service, and acceptance criteria are typical components of which document?

0 Discussions

Trending Exams