## 5.8.4 Conduct an Initial Evaluation of Compliance with RTCA DO-330 Tool Qualification Requirements 

The RTCA DO-330 supplement is applicable when the system developer / subcontractor has used or plans to use tools for qualified activities. Repeat the prior activities of Section 5.8 to evaluate all Tool Qualification (TQ) objectives for RTCA DO-330 compliance. 8 Provide a discussion for each tool as to its use and TQ need and status. 

## 5.8.5 Conduct an Initial Evaluation of Compliance with RTCA DO-331 Model-Based Development Requirements 

The RTCA DO-331 supplement is applicable when the system developer / subcontractor has used or plans to use Model-Based (MB) development. Repeat the prior activities of Section 5.8 to evaluate all MB development objectives for RTCA DO-331 compliance. If this supplement is not applicable, provide a rationale as to why it is not. 

## 5.8.6 Conduct an Initial Evaluation of Compliance with RTCA DO-332 Object-Oriented Techniques 

The RTCA DO-332 supplement is applicable when the system developer / subcontractor has used or plans to use Object-Oriented Techniques (OOT). Repeat the prior activities of Section 5.8 to evaluate all OOT objectives for RTCA DO-332 compliance. If this supplement is not applicable, provide a rationale as to why it is not. 

## 5.8.7 Conduct an Initial Evaluation of Compliance with RTCA DO-333 Formal Methods 

The RTCA DO-333 supplement is applicable when the system developer / subcontractor has used or plans to use Formal Methods (FM). Repeat the prior activities of Section 5.8 to evaluate all FM objectives for RTCA DO-333 compliance. If this supplement is not applicable, provide a rationale as to why it is not. 

## 5.8.8 Conduct On-Site Visits 

After desk reviews have been completed, the evaluation team should schedule visits to the system developer’s / subcontractor’s facilities to review additional documents/processes, interview key personnel, and complete any remaining fields of the worksheet. During this time, the RTCA DO-278A, RTCA DO-330, RTCA DO-331, RTCA DO-332, and RTCA DO-333 evaluations may be updated and re-evaluated based on the additional documents and interviews. 

## 5.8.9 Identify Corrective Actions 

For all findings of noncompliance, the system developer must identify corrective actions for bringing the development into compliance. If a finding of noncompliance is discovered after the lifecycle data has been documented (e.g., in a gap analysis of a legacy product or late in a development), the developer must analyze the non-compliance and take remedial actions to correct any identified problems. 

## 5.9 Produce a Final Software Assurance Compliance Analysis or Compliance Gap Analysis Report 

Produce a final report containing the RTCA DO-278A software assurance compliance analysis or the compliance gap analysis and include a description of further actions required to correct any identified noncompliance. 

