content_image/532806.jpg
• Visibility into the methodologies being used to comply with requirements and supporting data; 

• Objective evidence showing that the software project adheres to its approved software plans and procedures; and 

• The opportunity for the approval authority to monitor SME activities. 

## 6.2 Interaction between the Software Review Process and the Software Lifecycle 

The review process should begin early in the software lifecycle, as this will mitigate the risk of the software / planning decisions not satisfying RTCA DO-278A objectives. Beginning the review process early requires timely communication between the applicant and the approval authority about planning decisions that may affect the software processes and product. 

The development of software for a CNS/ATM system may take several months or years. Since RTCA DO-278A is process-oriented guidance, the review process must be integrated throughout the software lifecycle to be meaningful. This means that there should be regular contact between the applicant and the approval authority. Regular contact between the applicant and the approval authority assures both parties that the software development is meeting the required RTCA DO-278A objectives. The four types of recommended reviews are software planning reviews, software development reviews, software verification reviews, and final approval software reviews. 

## 6.2.1 Software Planning Review 

Although the software planning process may continue throughout the software lifecycle and plans and standards may change as the project progresses, the planning process is generally considered complete when the associated initial transition criteria are satisfied. The software planning review should take place at this time. Typical criteria for completion of the software planning process include: 

• Software plans and standards have been internally reviewed based on company-specified criteria, and all deficiencies have been resolved. 

• Software plans and standards have been evaluated by an SQA team, and all deficiencies have been resolved. 

• Software plans and standards have been approved and placed under configuration control. 

• Objectives 1 and 2 of RTCA DO-278A, Annex A, Table A-1 and Table A-10 have been satisfied. 

The applicant or the applicant’s SME must make the software plans and standards (shown in Table L.1) available to the approval authority. The supporting software data should undergo the configuration control appropriate for the software AL. 

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

