Test whether a requirement has been satisfied

Pre-conditions

• A requirement has been created that needs to be verified. A QM and RM tool have been associated with each other.

Scenario

1. User identifies a requirement using the RM tool
2. User requests a dialog for locating test cases in the RM tool
   • If a suitable test case already exists for the requirement then it is selected
   • Otherwise a new test case is created. Minimal details such as title and description are provided.
3. Selecting the test case from the RM tool creates a bi-directional link between that test case and the requirement
   • Link can be used in the QM tool to examine which requirement is validated by the test case
   • Link can be used in the RM tool to examine which test case validates the requirement
4. (Optional) From the QM tool, user associates test scripts with the test case selected in step 3
   • New test scripts may be created
   • Existing test scripts may also be selected
5. User updates the test case details based on the test scripts to be executed
   • User provides procedural data such as the test case precondition and postcondition
   • The test case may be reviewed and refined as needed
6. Development team implements requirement using a CM tool
   • Development team creates candidate driver
   • Development team delivers candidate driver for test
7. Test case is executed using QM tool
   • Multiple configurations may be tested
   • Defects are created if necessary

Post-conditions

• Requirement has been tested. If new defects have been created then the requirement may not have been fully satisfied.