ABSTRACT
Validation and derived requirements are intimately related: the purpose of validation is to show that derived requirements are correct and complete, and the purpose of identifying derived requirements is to identify which requirements must be validated. The objective of validation is defined in DO-254 as verifying that derived requirements are correct and complete. In the DO-254 realm, only derived requirements are validated so the point of identifying requirements as being derived is to identify the requirements that should be validated for completeness and correctness, and they should be validated because they contain some kind of information that must be verified for integrity. While validation can be achieved through review, analysis, or even test, the most common method to validate derived requirements for airborne electronic hardware is review. Validation through testing of finished hardware will require that the hardware be designed and built against unvalidated requirements, which can result in rework if the requirements were in error.
