The two other features that are available in the Requirements Module are Connections Graph and Status.
The connections graph shows the parent and child relationships of all the requirements within the module. Moreover, the connections also show if the requirement is being verified or not. The user can easily differentiate this by looking at the colour code in the connections graph. To access the connections graph, click on the requirements module (1) and select the connections graph (2).
The user can download the connections graphs as an image file by clicking on the download button (3). Note that the requirements are arranged within a box. This box represents the specification title (4). As mentioned earlier, the colour code represents the verification status of the requirement.
Fully green with green box - requirement and its parent requirement are verified (5)
Fully red with a red box - both the requirement and its parent requirement are not verified (6)
The identifier is green but the box is red - the child requirement is verified but the parent requirement is not verified (7)
Yellow box - either the child requirement or parent requirement is not verified
In the connections graph settings (next to the download option), you can enable/disable the compact view (only identifiers are visible in the connections graph) or group by specifications.
The other features that are available in the required module are the status. The status (1) either shows the matrix/tree view of how many requirements/specifications/components are verified or the overall progress of your requirement verification process. The green in the matrix/tree view implies the completion/near completion of your verification process.
In the matrix view (2), the status and the number of verified verification methods over the total count of verification methods of each requirement and component are shown. The user can change the comparison to Specifications/Components (3) as shown in the image below:
The tree within the status shows the verification status for the components in a hierarchical way. Similar to the matrix, more green in the tree means the project has matured well. Also, this gives the system engineer an overall view of which requirements need to be verified. The red ones are not verified and the grey ones are without any verification methods. The example for the tree is shown below.