Requirements Organization and Nomenclature
Requirements Verification
The final step of the systems engineering process is to demonstrate compliance with project requirements through verification activities, ultimately meeting all mission requirements. We demonstrate compliance with mission requirements through Roll-Up, or the philosophy of showing compliance to the parent by demonstrating compliance with all children requirements. To accomplish Roll-Up verification, the Iris team creates verification activities as children of subsystem requirements through one of four verification methods:
Review of Design/Documentation: Determines conformance to requirements by examination of technical drawings, CAD models, or design documentations (such as component specifications or qualification reports).
Analysis: Evaluation of data by generally accepted analytical techniques to determine that the item will meet specified requirements. Techniques include calculations and simulations.
Inspection: Determines conformance to requirements by the visual examination of the design item using standard quality control methods, without the use of special laboratory procedures or equipment. Activities include measurements (dimensions and mass) and visual inspections of features.
Test: A verification method in which technical means, such as the use of special equipment, instrumentation, simulation techniques, or the application of established principles and procedures are used for the evaluation of the system or system components to determine compliance with requirements.
Verification activities are undertaken throughout the project, with review and analysis being the primary verification activities during phases B and C. Phase D, also known as the Assembly, Integration, and Test (AIT), has the majority of the test and inspection activities, to demonstrate a functioning final product before launch.
To create meaningful verification activities that demonstrate compliance with requirements, activities need to outline [1]:
Identification - Verification ID in accordance with requirement naming convention.
Activity Goals - In addition of the requirement that will be verified, the verification activity needs to be clear about the acceptance criteria. There needs to be a measurable and observable metric that can be used as evidence that the CubeSat meets the goal requirement.
Activity Details - Step-by-step instructions that an operator needs to undertake the activity, providing necessary and important guidance for the activity operator. This is especially critical if the activity operator is not the subsystem lead.
Required Support Equipment - A short list of tools, test equipment, software, or facilities needed to complete the test.
Activity Parameters - This is critical information for tests and inspections, and can include, but not limited to, temperature ranges, vibration profiles, test duration, among others.
Activity Log - A place to record results, notes, or a checklist that can be completed.
[1] CCP AIT Webinar Part 1