Assessment Criteria for Third Party DO178B Life Cycle Data
Overview
Occasionally, we will enter into business agreements with third party software vendors to supply DO-178B Life Cycle Data developed using Plans and Procedures external to DDC-I. When this occurs, the oversight activities documented here will apply.
The Approach
Unless explicitly delegated, the ultimate assessment of a supplier's compliance with DO-178B is a privilege held solely by the certification authority and the applicant, that is the entity integrating DDC-I and third-party supplied software within their system. Because of this, DDC-I will not attempt to perform any DO-178B compliance assessments on third-party supplied life cycle data. DDC-I will limit its role to ensuring the categories of data defined in DO-178B exist within the third party's life cycle data, and facilitating communication between the third party supplier and the certification authority or applicant.
The rationale for the approach above is to avoid non-expert compliance opinions from being injected into the third party life cycle data certification process, and to avoid having the third party receive conflicting guidance.
Implementation
If the business arrangement puts DDC-I in the position of delivering third party supplied life cycle data on the third party's behalf, the life cycle data will not be stored at DDC-I except in the form of a backup copy of what is being shipped to the applicant. In essence, third party life cycle data is not DDC-I life cycle data thus the two should not be mingled.
We will limit the assessment of third party life cycle data to a determination of whether it exists, and in some cases as indicated below, to a determination of whether specific sub-categories exist as defined in DO-178B. The activities will not attempt any technical assessments of the data.
Performing the Assessment
- The person assigned to perform the activity should use the criteria specified in the table below.
- Each life cycle data item listed below should be accompanied with appropriate identification that can be used to trace the data back to the third party, as well as indicate the life cycle data has been approved for transfer outside of the third party's configuration management system. While specific identification methods may differ between third party vendors, typical methods include a title page, document revision, publish or configuration management system escape date, and third party signatures where appropriate.
- When performing the assessment, use the following definitions:
- Content exists per DO-178B <section> means we will ensure that the categories of data defined in DO-178B are present within the third party's DO-178B life cycle data.
- <Life cycle data> exists means we will ensure that the specified category of life cycle data has been provided, without any further examination of the data.
- Results from the assessment should be stored within the relevant customer project folder. Note that this location will not be a location containing DDC-I life cycle data.
- A copy of this assessment guide should be included in the report. A PDF generated copy of this entire wiki page is an acceptable format.
- The assessment results and a copy of the criteria used (this wiki page) should also be provided to the third party vendor and customer that requested the activity to be performed.
| No. | DO-178B Life Cycle Data Item | Assessment Criteria |
|---|---|---|
| 1. | Plan for Software Aspects of Certification (PSAC) | Content exists per DO-178B, Section 11.1 |
| 2. | Software Development Plan (SDP) | Content exists per DO-178B, Section 11.2 |
| 3. | Software Verification Plan (SVP) | Content exists per DO-178B, Section 11.3 |
| 4. | Software Configuration Management Plan (SCMP) | Content exists per DO-178B, Section 11.4 |
| 5. | Software Quality Assurance Plan (SQAP) | Content exists per DO-178B, Section 11.5 |
| 6. | Software Requirements and Design | Exists |
| 7. | Source Code | Exists |
| 8. | Executable Object Code | Exists |
| 9. | Test Cases and Procedures | Exists |
| 10. | Requirements and Design Review Evidence | Exists |
| 11. | Source Code Review Evidence | Exists |
| 12. | Test Case and Test Procedure Review Evidence | Exists |
| 13. | Requirements Coverage Requirements trace to code and tests |
Exists |
| 14. | Test Results | Exists |
| 15. | Structural Coverage Analysis | Exists |
| 16. | Software Life Cycle Environment Configuration Index (SLCECI) | Content exists per DO-178B, Section 11.15 |
| 17. | Software Configuration Index (SCI) | Content exists per DO-178B, Section 11.16 |
| 18. | Software Quality Assurance Records | Exists |
| 19. | Software Accomplishment Summary (SAS) | Content exists per DO-178B, Section 11.20 |
| 20. | Tool Qualification Data | Exists (If development or verification tools are being claimed) |
The following categories of life cycle data are not included in the assessment because they would likely require an internal inspection of the configuration management and problem reporting systems used by the third party.
- Problem Reports as described in DO-178B, Section 11.17
- Software Configuration Management (SCM) Records as described in DO-178B, Section 11.18