Scenario A: Requirements are implemented, validated and delivered

Pre-conditions

• 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.

Scenario

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, each of which is linked to its parent.
   3. The change requests are assigned to 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 to validate each requirement are written and linked to 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
5. Links can be used to inspect the content of the build
   1. Links between a requirement and a change request can be used to check that a requirement has been delivered
   2. Links between a requirement and a test case can be used to check that the implementation meets that requirement

Post-conditions

• The requirements are satisfied (all change requests completed, all test cases passing). The resulting build meets the requirements placed upon the product.