Requirement documentation
So far, you have captured notes on the users’ needs and wants. These are all the potential requirements – they are still vague and need structure so that they can be understood by both the stakeholder as well as your technical, testing, and training team. Our job is to transform and document them into high-quality, well-formatted requirements. The final documented requirements we produce will be well-written, clear, concise, and descriptive enough to avoid conflicts and confusion.
For stakeholder and project team members to be able to understand the requirement consistently in the same way, the requirement shall be written in to conform to the following attributes:
- Unambiguous
- Testable
- Original stakeholder understands and agrees
- Conforms to fit criteria
- Provides rationale
- Reviewed and agreed for completeness by technical and test leads
For documenting requirements, there are many templates available and your...
