Part 193: Requirements Documentation
(OUTPUT Project Scope Management: Collect Requirements)

  • The Requirements Documentation describes how an individual requirement meets the business need for the project
  • At the beginning of the project it starts out at a high level, and becomes more detailed as more information is known
  • Each requirement must be measurable, testable, traceable, complete, consistent, acceptable
  • The format of the documentation can be simple or complicated
  • Requirements can be categorized, and could include
    • Business Requirements (Project Objectives, Guiding Principles, What does the business hope to accomplish with this project?)
    • Stakeholder Requirements (Impacts to other organizational areas, impacts to other entities inside or outside, stakeholder communication requirements)
    • Solution Requirements (What will the product do and what are its features?)
      • Functional Requirements = behaviors of the product, what the product will do, how it will interact with others.  For example, we are designing a vehicle that can travel 100 miles per hour.
      • Non-Functional Requirements = environmental conditions, product safety & reliability, performance.  For example, our vehicle will go 200,000 miles before it needs an oil change, and the oil change will take only 1 hour to complete.
      • Transition & Readiness Requirements = temporary capabilities like data conversion and training.  For example, we will train the mechanics to change the oil and maintain the vehicle.  We only need to train them once, even though we will continue to manufacture vehicles.
      • Project Requirements = conditions that the project must fulfill.  For example, this vehicle will be developed in six months.
      • Quality Requirements = other conditions required.  For example, this vehicle must be energy efficient and must comply with EPA guidelines.