Requirements Documentation

Posted on September 8, 2009 by


Understanding the individual requirements for a project and how they each support the business need is the purpose of Requirements Documentation—an output of the fourth edition PMBOK®’s Collect Requirements process.

According to the PMBOK, this documentation can include many things, such as business need for the project, traceability requirements, functional requirements, non-functional requirements, quality requirements, acceptance criteria, business rules, impact, support and training requirements, assumptions, and constraints. This documentation is most similar to the BABOK® 2.0’s Validated Requirements, which are an output of the Requirements Validation process. These are requirements that have been demonstrated to provide business value and work together to meet the project’s objectives. Before being validated, they have been verified for quality to assure that they are cohesive, complete, consistent, correct, feasible, modifiable, unambiguous, and testable.  A separate BABOK process, Determine Assumptions and Constraints, is where the assumptions and constraints for these requirements are determined.

The other outputs of the Collect Requirements process can be found described in the earlier postings of Requirements Management Plan (posted August 4, 2009) and Requirements Traceability Matrix (posted August 28, 2009).