[FCR 25] Verification of adherence of the flight hardware to the fracture control requirements in this NASA Technical Standard shall include all of the following:
a. Written documentation that establishes that each requirement has been met. This documentation describes how the requirement was verified, e.g., test, analysis, inspection. The project is responsible for providing this verification, including assurance that fracture control activities were implemented on the flight hardware before flight and reflight, to the appropriate program management.
NASA-STD-5019A w/CHANGE 4
- b. Approval of the FCP and FCSR by the RFCB, documented by a concurrence memorandum from the RFCB to the applicable project/program office.
- c. In the event of conflict between the RFCB and the applicable project office concerning verification of compliance with fracture control requirements, follow the procedures in place at each NASA Center to resolve technical conflict, with the option to appeal to the NASA Chief Engineer for final resolution.
[Rationale: All requirements need to be verified. The verification is the evaluation and documentation that all requirements have been met. There are many methods of verification, e.g., analysis, test, inspection, each of which should be documented.]
The project is responsible to the appropriate program for the line-by-line review of the verification requirements. The RFCB is responsible for a review of the methodology of the compliance to and verification of the requirements. These are documented in the FCP and FCSR, respectively.
Commonly, the project writes project-specific requirements that are traceable to a higher level standard. This requirements set includes a verification section. In this section, there is a verification requirement for every requirement in the project-specific requirements. This requirement documents how the verification will be done.
The RFCB is to receive the FCP and FCSR in accordance with requirements in this NASA Technical Standard, but, as described above, the RFCB is not the entity that performs the requirement-by-requirement review.