Verification (spaceflight)

Verification in the field of space systems engineering covers two verification processes: Qualification and Acceptance

Overview

In the field of spaceflight verification standards are developed by NASA and the ECSS, and to specify requirements for the verification of a space system product, such as:[1]

Verification is one main reason that costs for space systems are high. All data are to be documented and to stay accessible for potential, later failure analyses. In previous times that approach was executed down to piece-parts level (resistors, switches etc.) whereas nowadays it is tried to reduce cost by usage of "CAM (Commercial, Avionics, Military) equipment" for non-safety relevant units.

Qualification and Acceptance

Qualification is the formal proof that the design meets all requirements of the specification and the parameters agreed in the Interface Control Documents (ICD) including tolerances due to manufacturing imperfections, wear-out within specified life-time, faults etc. The end of the qualification process is the approval signature of the customer on the Certificate of Qualification (COQ) agreeing that all his requirements are met.

Acceptance is the formal proof that the product identified by its serial number meets all requirements of the specification and is free of workmanship and material failures. Acceptance is based on the preceding qualification by reference to the used design / manufacturing documentation. The end of the acceptance process is the approval signature of the customer on the Certificate of Acceptance (COA) agreeing that all his requirements are met by the product to be delivered.

Qualification verification methods are

Each software element will be tested alone and as part of the overall system configuration until considered as qualified.

Acceptance verification methods are

See also

References

  1. Space Engineering Verification, ECSS-E-10-02A, 17 November 1998, p.11.

Further reading

This article is issued from Wikipedia - version of the 9/30/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.