Verification Activities

Verification activities are used to demonstrate the CubeSat's compliance with project requirements and it's capability to meet mission goals and expectations. Requirements need to be clearly defined in the pass fail criteria, if the test has been undertaken, and if the results demonstrate compliance. Figure 1 shows a verification group with the most common visible columns.

To standardize the columns used by the team and make for an easier review experience, standard view 1 has been created. It can be accessed from the 3 dots on the left-hand side of the verification activities. Load view and then Standard View 1. This can be seen in the figure below.

This shows the status, compliance, verification comment, and phase tag.

Because the Iris team uses the Valispace requirements interface to control verification activities, many of the functions options and columns presented in the requirements page and details sections are still available to users. However, because verification activities differ from requirements, different information is needed to understand and interpret the current state of the project. Common elements used by the Iris team for verification activities are detailed below with corresponding call-out numbers in Figure 1.

1. Verification ID - This column provides the requirement ID's in accordance requirement and verification activity naming convention.

2. Verification Text - This tab provides a visual representation of how all requirements or specification (subsystem requirements) are linked.

3. Parent Requirements - - This column provides the parent requirement for all subsystem and inter-subsystem requirements, and verification activities.

4. Compliance Status - This column provides the current compliance status of the verification activity. Supporting evidence is documented in the "Verification Comment" column (item 6).

5. Compliance Comment - This column is used for additional documentation for the compliance status of the activity.

6. Verification Method - This column provides the verification method used (Review of Design/Documentation, Analysis, Inspection, Test).

7. Components - To enable the verification activities in Valispace, requirement groups need to be linked to components. The Iris team has created general subsystem components in Valispace that can be found in the Components module, with the only purpose to enable verification content.

8. Status - This column demonstrates if the verification activity has been completed (shown as verified). Other options include ongoing, or partially verified.

9. Verification Comment - This is the main column where the Iris team includes links or directions to evidence for the status and compliance of the verification activity. All verification reports are collected in the Verification Reports section in this wiki.

All verified and compliant activities are reflected in their respective subsystem requirements group, and appear as an entry in the number of children verified column, shown in Figure 2. This cascades into the top level requirements, providing evidence of verification through roll-up to mission level requirement.