Requirements documentation
“Requirements Documentation” is an output for the process “Collect Requirements”.
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.
“Requirements Documentation” is an input for the process “Define Scope”.
This documentation will be used to select the requirements that will be included in the project.
“Requirements Documentation” is an input for the process “Create WBS”.
Detailed requirements documentation is essential for understanding what needs to be produced as the result of the project and what needs to be done to deliver the project and its final products.
“Requirements Documentation” is an input for the process “Validate Scope”.
The requirements documentation lists all the project, product, and other types of requirements for the project and product, along with their acceptance criteria.
“Requirements Documentation” is an input for the process “Control Scope”.
Requirements should be unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders. Well-documented requirements make it easier to detect any deviation in the scope agreed for the project or product.
“Requirements Documentation” is an input for the process “Plan quality management”.
Requirements documentation captures the requirements that the project shall meet pertaining to stakeholder expectations. The components of the requirements documentation include, but are not limited to, project (including product) and quality requirements. The requirements are used by the project team to help plan how quality control will be implemented on the project.
“Requirements Documentation” is an input for the process “Plan Procurement management”.
Requirements documentation may include: – Important information about project requirements that is considered during planning for procurements,
and – Requirements with contractual and legal implications that may include health, safety, security, performance, environmental, insurance, intellectual property rights, equal employment opportunity, licenses, and permits?all of which are considered when planning for procurements.
This definition was found in the PMBOK V5
Go back to the Glossary or to the Mapping