Requirements Page
The Valispace requirements module is the core of the Iris project requirements and verification tracking system, providing all the information required of the team to find and review relevant requirements. The team has grouped each requirement in accordance with the systems engineering hierarchy, allowing individual subsystems to create and manage their own requirements and verification activities. Iris system engineering lead manages the mission level and the inter-subsystem requirements to ensure design harmony between subsystems. Figure 1 provides the elements of the requirements group page.
Valispace provides the team with different methods to document and organize information relating to requirements. Below is a description of the most common requirements related columns used by the Iris team, corresponding with the call-out number in Figure 1.
Requirements Tab - This tab provides the view currently provided in Figure 1, providing the user a view of recorded requirements.
Connections Tab - This tab provides a visual representation of how all requirements or specification (subsystem requirements) are linked.
Status Tab - This is a new feature in Valispace as of the 28th of October 2020, but provides a useful outline of the verification status of all children in the project. This will be reviewed and investigated further by the Iris team.
Requirement Identifier - This column provides the requirement ID's in accordance requirement and verification activity naming convention.
Requirement Text - This column provides the requirements text, following "Shall," "Should," and "May" conventions.
Requirement Rationale - This column provides the reasoning or parent external requirements for mission level requirements.
Parent Requirements - This column provides the parent requirement for all subsystem and inter-subsystem requirements, and verification activities.
Child Requirements - This column provides the child requirements for all requirement groups.
Verified Children - This column provides the number of children requirements and verification activities that have been verified.
Tags - This column provides tags that facilitate sorting. It is primarily used to identify when verification activities occur (Phase A, B, etc.)
Page Settings - This drop down menu provides users to be able to edit visible columns, export table into either an CSV or XLSX file. Figure 2 provides the expected view.
Requirements and verification activities are divided into their respective subsystem folders, which organizes entries as either requirements or verification activities, as shown in Figure 3. Note that due to the nature of mission level requirements having no parents, and inter-subsystem requirements being an interim group, they have been allocated into the "Top_Level_Group."
Users can also access more requirement specific information by clickling on the requirement ID, discussed in the next section.