content_image/607620.jpg content_image/607619.jpg
to the approval authority and/or SME. However, only the data shown in Table L.2 are of special interest for this review. The supporting software data should undergo the configuration control appropriate for the AL. 

<img src='content_image/607620.jpg'>

Evaluation criteria for this review include all objectives of RTCA DO-278A, Annex A. Additionally, all software-related problem reports, action items, approval issues, etc., should be addressed before approval. 

Note : Although this appendix proposes four types of reviews, the type, number, and extent of those reviews may not suit every project and applicant. Additional considerations and alternative approaches may be appropriate. 

## 6.3 Intervention Points 

The purpose of design assurance is to catch errors as early as possible in the design process and prevent them from being incorporated into the final product. The overall concept is that a review (or intervention) should be conducted: 

• Early enough in the design process that corrective action can be taken to ensure compliance and reduce the repetition of work. 

• Late enough to have enough data for a good sample to be used to represent how well the development is progressing. 

• At a point where progress can be halted, if needed, before the completion of a milestone to resolve issues of non-compliance before they can corrupt the next design stage. 

When to conduct each review depends upon the developer’s plans. Table L.3 provides a rough timeline of when to conduct the different reviews. 

<img src='content_image/607619.jpg'>

