SW Level A
Main Description
Level A - Catastrophic: Safety concerns at this level may often resulting in total loss of the aircraft and passengers. Failure conditions of this category would prevent safe flight and/or landing. This may be due to direct cause fault or may result from overburdening the workload on the pilot and/or crew.

Objective Description Satisfies with Independence
Objective A.1.1 Software development and integral processes are defined  
Objective A.1.2 Transition criteria, inter-relationships and sequencing among processes are defined  
Objective A.1.3 Software lifecycle environment is defined  
Objective A.1.4 Additional considerations are addressed  
Objective A.1.5 Software development standards are defined  
Objective A.1.6 Software plans comply with DO-178  
Objective A.1.7 Development and revision of software plans are coordinated [DO-178C]  
      
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 Y
Objective A.3.2  High-level requirements are accurate and consistent Y
Objective A.3.3 High-level requirements are compatible with target computer  
Objective A.3.4 High-level requirements are verifiable  
Objective A.3.5 High-level requirements conform to standards  
Objective A.3.6 High-level requirements are traceable to system requirements  
Objective A.3.7  Algorithms are accurate Y
Objective A.3.8 MB Simulation cases are correct [DO-331] Y
Objective A.3.9 MB Simulation procedures are correct [DO-331] Y
Objective A.3.10 MB Simulation results are correct and discrepancies explained [DO-331] Y
     
Objective A.4.1 Low-level requirements comply with high-level requirements Y
Objective A.4.2 Low-level requirements are consistent and accurate Y
Objective A.4.3 Low-level requirements are compatible with target computer  
Objective A.4.4 Low-level requirements are verifiable  
Objective A.4.5 Low-level requirements conform to standards  
Objective A.4.6 Low-level requirements are traceable to high-level requirements  
Objective A.4.7 Algorithms are accurate Y  
Objective A.4.8 Software architecture is compatible with high-level requirements Y
Objective A.4.9 Software architecture is consistent Y  
Objective A.4.10 Software architecture is compatible with target computer  
Objective A.4.11 Software architecture is verifiable  
Objective A.4.12 Software architecture conforms to standards  
Objective A.4.13 Software partitioning integrity is confirmed Y
Objective A.4.14 MB Simulation cases are correct [DO-331] Y 
Objective A.4.15 MB  Simulation procedures are correct [DO-331] Y 
Objective A.4.16 MB Simulation results are correct and discrepancies explained [DO-331] Y 
     
Objective A.5.1 Source code complies with low-level requirements Y
Objective A.5.2 Source code complies with software architecture Y
Objective A.5.3 Source code is verifiable   
Objective A.5.4 Source code conforms to standards  
Objective A.5.5 Source code is traceable to low-level requirements  
Objective A.5.6 Source code is accurate and consistent Y  
Objective A.5.7 Output of software integration process is complete and correct  
Objective A.5.8 Parameter Data Item File is correct and completed [DO-178C] Y
Objective A.5.9 Verification of Parameter Data File is achieved [DO-178C] Y
      
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.3 Executable Object Code complies with low-level requirements Y
Objective A.6.4 Executable Object Code is robust with low-level requirements Y
Objective A.6.5 Executable Object Code is compatible with target computer  
      
Objective A.7.1 Test procedures are correct Y
Objective A.7.2 Test results are correct and discrepancies explained Y
Objective A.7.3 Test coverage of high-level requirements is achieved Y
Objective A.7.4 Test coverage of low-level requirements is achieved Y
Objective A.7.5 Test coverage of software structure (modified condition/decision) is achieved Y
Objective A.7.6 Test coverage of software structure (decision coverage is achieved) Y
Objective A.7.7 Test coverage of software structure (statement coverage is achieved) Y
Objective A.7.8 Test coverage of software structure (data coupling and control coupling) is achieved Y
Objective A.7.9 Verification of additional code, that cannot be traced back to source code, is achieved [DO-178C] Y
Objective A.7.10 MB Simulation cases are correct [DO-331] Y
Objective A.7.11 MB Simulation procedures are correct [DO-331] Y
Objective A.7.12 MB Simulation results are correct and discrepancies explained [DO-331] Y
Objective A.7.10 OO Verify local type consistency [DO-332] Y
Objective A.7.11 OO Verify the use of dynamic memory management is robust [DO-332] Y
   
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.1 Assurance is obtained that software plans and standards are developed and reviewed for compliance with this document and for consistency [DO-178C] Y
Objective A.9.2 Assurance is obtained that software life cycle processes comply with approved software plans [DO-178C] Y
Objective A.9.3 Assurance is obtained that software life cycle processes comply with approved software standards [DO-178C] Y
Objective A.9.4 Assurance is obtained that transition criteria for the software life cycle processes are satisfied [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