Requirements Nomenclature
The Iris team decomposes the mission level requirements into different subsystem requirements groups, providing guidance in developing the technical design of the CubeSat. Each subsystem lead is responsible for decomposing, updating, and maintaining their respective subsystem's requirement. To ensure a thorough and meaningful requirement verification approach, it is important to maintain a thorough record of the parents and children of each requirement. The final step of decomposition is creating a verification activity child that will demonstrate Iris's compliance with our requirements, in accordance with our V-Model. Figure 1 provides a visual outline of our requirements hierarchy.
Each subsystem groups created children requirements, using their respective subsystem's project acronym, shown in Table 1. The requirement group acronyms are used throughout the project for identification of requirements, verification activities, and design documentation.
If a subsystem requires another subsystem to make accommodations (i.e. structure requires another subsystem to be below a certain mass), an Inter-Subsystem requirement (R-INT) is created. R-INT is a special requirements group that allows subsystem teams to either push or pull requirements from another team, allowing for a useful method to monitor all inter-subsystem needs.
When recording requirements, the requirement ID will be followed by a four-digit number (e.g. R-YYY-0010, R-YYY-0020). Table 2 outlines the requirement definition, and appropriate interpretation. Should a requirement be introduced in between other requirements, the last digit will be used.