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 repositories in order to pass audits.
The System Requirements
shows how functional and nonfunctional requirements are implemented by generating a printable
This app uses tags. To get started, you need to
stories that represent your System Requirements as SRS.
When printed, a signature line and printed date are appended to the bottom of the document.
Source code is available: System Requirement Validation Document app source code
Product Requirement Section
- Market Requirement: Specified SRS-tagged story's parent link and name
- System Requirement: Specified SRS-tagged story link and name
Date: Specified SRS-tagged story acceptance date
System Requirement Description Section
- Specification: Specified SRS-tagged story link and name
- Description: Specified SRS-tagged story description
- Functional Stories: Specified SRS-tagged story's children links and names
Test Case Section
This section loops through the test cases of the specified SRS story and its child stories. If no test cases exist, this section does not display.
- 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
This app should be considered as a starting point to meet your organization's unique requirements. You may need to modify the app code further to implement specific features that best help your team. For more information on customizing apps, see our developer portal, or open a new support case.