Viewing requirements
Main View
The basic view of a requirement looks like:
Note the following fields displayed:
- Name
- Description
- Tags
- Security Implication
- Requirement Type
- Requirement State
Linked requirements
Upstream links example
This is an example of links being displayed upstream of the current requirement:
Notice how the red lines indicate a suspect link, which needs attention.
Downstream links example
This is an example of links being displayed downstream of the current requirement:
Notice how the red lines indicate a suspect link, which needs attention.
Incidents
It is worth noting that incidents that are linked to a requirement are displayed separately from other information!
If there is a suspect link with an incident, that is able to be cleared either from the upstream requirement or the incident Requirement Links view.
Requirement dependencies
Dependencies are different than links because dependencies indicate an order of operation, whereas links indicate tightly related information.
Use dependencies to keep track of the order in which a project should be implemented.
Related items
This is where any files that are related to this document are linked.
Files are only uploaded once, and can be linked to as many documents as you would like.
For more information, see the files page.
Related incidents
Incidents that have been linked to the current requirement appear in their own separate tab, because of their importance.
Any time a requirement or incident is modified, the links become suspect and can be cleared either from the upstream document or the incident.
Test runs
Technical documents
For documents that are on the left side of the V (technical documents), the test run view will show the different downstream requirements (which will be verification/validation documents) and their associated historical test run results.
These can also be filtered by individual requirements:
Validation/Verification documents
For documents that are on the right side of the V, the test results view looks more streamlined, as it only shows results for that one validation:
Version history
Any updates to the requirement will result in a new version being created: