## 5.5 Have the System Developer / Subcontractor Conduct a Self-Evaluation 

Have the system developer / subcontractor evaluate their own software development efforts against the RTCA DO-278A criteria and record the findings. This will help Subject Matter Experts (SMEs) and the compliance evaluation team better understand the document structure, system/software architecture, organization, development processes, and verification approach. 

## 5.6 Identify Evidence of Compliance 

Locate the content within the system developer’s documents that demonstrates compliance with the RTCA DO-278A guidance. The labeling of the document’s contents does not have to match the RTCA DO-278A document descriptions as long as the intent of the text clearly satisfies RTCA DO-278A requirements. CM is required for all developer documents. 

## 5.7 Rate the Level of Compliance with RTCA DO-278A Guidance 

Once the system developer / subcontractor has provided the requested documents and process descriptions, review the submissions with the RTCA DO-278A SMEs to determine whether the developer’s/subcontractor’s submissions align with the RTCA DO-278A guidance. Evaluate compliance to applicable RTCA DO-278A guidance and remember that different guidance may apply to different DALs. Use the identified top-level or sub-objectives (mentioned in Section 4.1.3) as the means to map the guidance to the DALs. Identify the compliance rating as Satisfied (S), Partially Satisfied (P), Not Satisfied (N), or Not Applicable (X) using the following evaluation criteria: 

• Satisfied: The RTCA DO-278A guidance has been met through normal means and has been fully satisfied. 

• Partially Satisfied: The RTCA DO-278A guidance has been partially met through normal means and its intent has been partially satisfied. 

• Not Satisfied: The RTCA DO-278A guidance has not been met through normal means and its intent has not been satisfied. 

• Not Applicable: The RTCA DO-330, RTCA DO-331, RTCA DO-332, or RTCA DO-333 guidance is not applicable to this project. 

## 5.8 Evaluate Progress 

## 5.8.1 Justify the Evaluation 

Record how the reviewed documentation demonstrates or does not demonstrate compliance with RTCA DO-278A guidance. List the documents, sections, and paragraphs that support the compliance rating or provide a rationale for why the evaluation may be (P) or (N). 

## 5.8.2 Indicate Whether Additional Documents are Needed 

Identify additional documents and processes needed to fully evaluate compliance to the RTCA DO-278A guidance. 

## 5.8.3 Summarize the RTCA DO-278A Software Assurance Compliance Analysis 

Once compliance to applicable RTCA DO-278A guidance has been evaluated and assigned a compliance rating (see Section 5.7), review the results and summarize the overall findings. 

