|
Objective
|
Description
|
Satisfied with Independence
|
|
Objective A.1.1
|
Software development and integral processes are defined
|
|
|
Objective A.1.4
|
Additional considerations are addressed
|
|
|
|
|
|
|
Objective A.2.1
|
High-level requirements are developed
|
|
|
Objective A.2.2
|
Derived high-level requirements are defined
|
|
|
Objective A.2.3
|
Software architecture is developed
|
|
|
Objective A.2.4
|
Low-level requirements are developed
|
|
|
Objective A.2.5
|
Derived low-level requirements are defined
|
|
|
Objective A.2.6
|
Source code is developed
|
|
|
Objective A.2.7
|
Executable Object Code and Parameter Data Item files, if any, are produced and loaded in the target
computer [DO-178C]
|
|
|
Objective A.2.8 MB
|
Specification Model elements that do not contribute to implementation or realization of any high-level
requirement are identified [DO-331]
|
|
|
Objective A.2.9 MB
|
Design Model elements that do not contribute to implementation or realization of any software architecture
are identified [DO-331]
|
|
|
Objective A.2.10 MB
|
Design Model elements that do not contribute to implementation or realization of any low-level requirement
are identified [DO-331]
|
|
|
|
|
|
|
Objective A.3.1
|
Software high level requirements comply with system requirements
|
|
|
Objective A.3.2
|
High-level requirements are accurate and consistent
|
|
|
Objective A.3.6
|
High-level requirements are traceable to system requirements
|
|
|
Objective A.3.7
|
Algorithms are accurate
|
|
|
|
|
|
|
Objective A.4.13
|
Software partitioning integrity is confirmed
|
|
|
|
|
|
|
Objective A.5.8
|
Parameter Data Item File is correct and completed [DO-178C]
|
|
|
|
|
|
|
Objective A.6.1
|
Executable Object Code complies with high-level requirements
|
|
|
Objective A.6.2
|
Executable Object Code is robust with high-level requirements
|
|
|
Objective A.6.5
|
Executable Object Code is compatible with target computer
|
|
|
|
|
|
|
Objective A.7.3
|
Test coverage of high-level requirements is achieved
|
|
|
|
|
|
|
Objective A.8.1
|
Configuration items are identified
|
|
|
Objective A.8.2
|
Baselines and traceability are established
|
|
|
Objective A.8.3
|
Problem reporting, change control, change review, and configuration status accounting are established
|
|
|
Objective A.8.4
|
Archive, retrieval, and release are established
|
|
|
Objective A.8.5
|
Software load control is established
|
|
|
Objective A.8.6
|
Software life cycle environment control is established
|
|
|
|
|
|
|
Objective A.9.2
|
Assurance is obtained that software life cycle processes comply with approved software plans [DO-178C]
|
Y
|
|
Objective A.9.5
|
Assurance is obtained that software conformity review is conducted [DO-178C]
|
Y
|
|
|
|
|
|
Objective A.10.1
|
Communication and understanding between the applicant and the certification authority is established
|
|
|
Objective A.10.2
|
The means of compliance is proposed and agreement with the Plan for Software Aspects of Certification is
Obtained
|
|
|
Objective A.10.3
|
Compliance substantiation is provided
|
|