DI-SESS-82337

Software Accomplishment Summary (SAS)

Describes the methodology and evidence used for Government certification of software compliance with civil performance standards under RTCA/DO-178C, summarizing the compliance effort for software.

Approval DateMarch 29, 2021

AMSC NumberN10228

Preparing ActivityAS

Project NumberSESS-2021-007

OPR—

DTIC ApplicableNo

GIDEP ApplicableNo

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The Software Accomplishment Summary (SAS) document describes the methodology used and the evidence created for the Government certification of software compliance within similar civil performance standards for RTCA/DO-178C "Software Considerations in Airborne Systems and Equipment". The SAS is intended to provide the Government with a summary of the compliance effort for software.

This Data Item Description (DID) contains the format, content, and intended use information for the data product resulting from the work task described in the contract statement of work (SOW).

Preparation Instructions

1Reference DocumentsThe applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions shall be as specified in the contract.

2FormatThe SAS shall be in the contractor's format.

3ContentThe SAS shall be compliant with the guidance in RTCA DO-178C 11.20 as documented in 3.1. The SAS shall identify:

3.1Any deviations from the approved plans and processes

3.2Configuration of the approved software

3.3Any open or deferred priority 1, 2, and 3 Problem Trouble Reports (PTR)

3.4SAS

3.5System overviewThis section shall provide an overview of the system, including a description of its functions and their allocation to hardware and software, the architecture, the processor(s) used, the hardware/software interfaces, and safety features. This section shall also describe any differences from the system overview in the Plan for Software Aspects of Certification.

3.6Software overviewThis section shall briefly describe the software functions with emphasis on the safety and partitioning concepts used, and shall explain differences from the software overview proposed in the Plan for Software Aspects of Certification.

3.7Certification considerationsThis section shall restate the certification considerations described in the Plan for Software Aspects of Certification and describe any differences.

3.8Software life cycleThis section shall summarize the actual software life cycle(s) and explain differences from the software life cycle and software life cycle processes proposed in the PSAC.

3.9Software life cycle dataThis section shall describe any differences from the proposals made in the Plan for Software Aspects of Certification for the life cycle data produced, the relationship of the data to each other and to other data defining the system, and the means by which the data was made available to the certification authority. This section shall explicitly reference, by configuration identifiers and version, the applicable Software Configuration Index and Software Life Cycle Configuration Index. Detailed information regarding configuration identifiers and specific version of software life cycle data shall be provided in the Software Configuration Index.

3.10Additional considerationsThis section shall summarize any specific considerations that warrant the attention of the certification authority. It explains any differences from the proposals contained in the Plan for Software Aspects of Certification regarding such considerations. Reference should be made to data items applicable to these matters, such as issue papers or special conditions.

3.11Supplier oversightThis section shall describe how supplier processes and outputs comply with plans and standards.

3.12Software identificationThe section shall identify the software configuration by part number and version.

3.13Software characteristicsThe section shall state the Executable Object Code size, timing margins, including worst-case execution time, memory margins, resource limitations, and the means used for measuring each characteristic.

3.14Change historyIf applicable, this section shall include a summary of software changes with attention to changes made due to failures affecting safety, and identify and changes from and improvements, to the software life cycle processes since the previous certification.

3.15Software statusThis section shall contain a summary of Problem Reports unresolved at the time of certification. The Problem Report summary shall include a description of each problem and any associated errors, functional limitations, operational restrictions, potential adverse effect(s) on safety together with a justification for allowing the Problem Report to remain open, and details of any mitigating action that has been or needs to be carried out.

3.16Compliance statementThis section shall include a statement of compliance with the SAS and a summary of the methods used to demonstrate compliance with criteria specified in the software plans. This section shall also address additional rulings made by the certification authority and any deviations from the software plans, standards, and this document not covered elsewhere.

References

—

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer