What does the verification and validation step look like for the software?
Yeah. From a software prospective, one of the things that’s really helpful is having what we call test beds or test platforms where you can run the software in a flight-like or deployment like environment, and you can verify that the requirements are met. So the first step is to actually run the verification testing. This is after the developers developed it and unit tested it. And said, Okay, I think my module’s ready for integration. Once it’s all integrated, then we run the verification tests on it to verify the functionality that it meets the requirements. Is this a manual stage or automated or some combination? It is automated to a large extent. The capability at Lockheed permits automation and scripting of the tests. And they can be rerun. It typically — the whole battery of tests was — I think there were about 85 total tests that were run on the software at an integration level. Per each payload or for — No, total. Total for the — well, okay. Total for the flight system. And the
Related Questions
- Are documents related to validation and verification of software used in support of the Total System Performance Assessment required to be included in the LSN?
- What is the purpose of becoming a Greenhouse Gas (GHG) Validation/Verification Body (V/VB)?
- What is Independent Software Verification & Validation?
