System Requirement Validation Document
If you work in a high-assurance environment, you may need to generate documents that prove requirements have been implemented, and print or export those documents to document repositories in order to pass audits.
The System Requirements Validation Document App shows how functional and nonfunctional requirements are implemented by generating a printable report.
This app keys off of special tags. To get started, you'll need to let Rally know which user stories represent your System Requirements by tagging them "SRS".
When it is printed, a signature line and printed date are appended to the bottom of the document.
Summary of Product Requirement Data
- Market Requirement: Link and name for parent of the chosen 'SRS' tagged story
- System Requirement: Chosen 'SRS' tagged story link and name
- Acceptance Date: Chosen 'SRS' tagged story acceptance date
Summary of System Requirement Description Data
- Specification: Chosen 'SRS' tagged story link and name
- Description: Chosen 'SRS' tagged story description
- Functional Stories: Links and names for the children stories of the chosen 'SRS' story
Summary of Test Case Data
This section loops through the test cases of the chosen 'SRS' story and its children stories. If no test cases exist, this section will not show.
- Test Case: Link and name of test case
- Story: Story that attaches to this test case
- Test Case Description: Description for this test case
- Last Run: Date that this test case was last ran
- Steps: Table of steps defined for this test case