This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.

Scenario A: Requirements are implemented, validated and delivered


  • An interesting set or collection of requirements has been identified for inclusion in a product. We assume that the requirements process is complete and the requirements have been approved and planned for inclusion in the product. How that came to be is not dealt with here.


  1. The requirements are broken down into change requests
    1. Each requirement is linked to one or more change requests
    2. Each change request could further be broken down into smaller change requests
    3. The change requests are assigned for completion
  2. A test plan to validate these requirements is created
    1. The test plan is linked to the requirement set
    2. Test cases are written to validate each requirement
  3. Code is delivered and change requests are marked as completed
    1. Code gets picked up by the next build
  4. The test steps from the test plan are run on the new build
    1. If any test fails, start over from step 4
    2. If all tests pass, continue


  • The requirements are satisfied (all change requests completed, all test cases passing). The resulting build meets the requirements placed upon the product.
Edit | Attach | Print version | History: r6 | r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r2 - 11 Jun 2009 - 21:02:43 - IanGreen
Main.RequirementCompleted moved from Main.ARequirementIsValidatedAndImplemented on 14 Apr 2009 - 15:52 by PratikShah
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback