10 | Overview of certification process | 0 |
11 | Software life cycle data | 0 |
12 | Additional considerations | 0 |
2 | System aspects relating to software development | 0 |
3 | Software life cycle | 0 |
A-1.1 | Activities of every life cycle process set out in the plans | 3 |
A-1.2 | Life cycle model fixed: process interactions, order, feedback and transition criteria | 3 |
A-1.3 | Development and verification environment chosen and documented | 2 |
A-1.4 | Section 12 topics and other special considerations dealt with in planning | 2 |
A-1.5 | Requirements, design and code standards established | 4 |
A-1.6 | Plans shown to conform to DO-178C for the assigned level | 1 |
A-1.7 | Plans produced and changed in a coordinated way | 1 |
A-10.1 | Applicant and certification authority communicate and understand each other | 0 |
A-10.2 | Means of compliance proposed and PSAC agreed with the authority | 2 |
A-10.3 | Evidence of compliance supplied to the authority | 2 |
A-2.1 | High-level software requirements produced from the allocated system requirements | 3 |
A-2.2 | Derived high-level requirements identified and passed to the system and safety processes | 3 |
A-2.3 | Software architecture produced | 2 |
A-2.4 | Low-level requirements produced | 1 |
A-2.5 | Derived low-level requirements identified and passed to the system and safety processes | 1 |
A-2.6 | Source code written from the low-level requirements and architecture | 2 |
A-2.7 | Executable object code and any parameter data item files built and loaded on the target | 2 |
A-3.1 | High-level requirements satisfy the system requirements allocated to software | 2 |
A-3.2 | High-level requirements precise and free of conflict | 2 |
A-3.3 | High-level requirements fit the target hardware | 0 |
A-3.4 | High-level requirements testable or otherwise verifiable | 2 |
A-3.5 | High-level requirements follow the requirements standards | 0 |
A-3.6 | High-level requirements traced to system requirements | 2 |
A-3.7 | Algorithms in the high-level requirements are correct | 0 |
A-4.1 | Low-level requirements satisfy the high-level requirements | 1 |
A-4.10 | Architecture fits the target hardware | 0 |
A-4.11 | Architecture verifiable | 0 |
A-4.12 | Architecture follows the design standards | 0 |
A-4.13 | Partition breaches shown to be prevented | 2 |
A-4.2 | Low-level requirements precise and free of conflict | 0 |
A-4.3 | Low-level requirements fit the target hardware | 0 |
A-4.4 | Low-level requirements verifiable | 0 |
A-4.5 | Low-level requirements follow the design standards | 0 |
A-4.6 | Low-level requirements traced to high-level requirements | 0 |
A-4.7 | Algorithms in the low-level requirements are correct | 0 |
A-4.8 | Architecture does not conflict with the high-level requirements | 1 |
A-4.9 | Architecture internally coherent | 0 |
A-5.1 | Source code implements the low-level requirements | 1 |
A-5.2 | Source code matches the architecture | 0 |
A-5.3 | Source code verifiable | 0 |
A-5.4 | Source code follows the code standards | 1 |
A-5.5 | Source code traced to low-level requirements | 1 |
A-5.6 | Source code free of accuracy and consistency defects | 1 |
A-5.7 | Integration outputs checked as complete and correct | 1 |
A-5.8 | Parameter data item file content correct and complete | 1 |
A-5.9 | Parameter data item file verification demonstrated | 1 |
A-6.1 | Executable object code meets the high-level requirements | 2 |
A-6.2 | Executable object code robust against the high-level requirements | 2 |
A-6.3 | Executable object code meets the low-level requirements | 0 |
A-6.4 | Executable object code robust against the low-level requirements | 0 |
A-6.5 | Executable object code works on the target computer | 1 |
A-7.1 | Test procedures checked as correct | 2 |
A-7.2 | Test results checked and every discrepancy explained | 2 |
A-7.3 | Tests cover every high-level requirement | 3 |
A-7.4 | Tests cover every low-level requirement | 0 |
A-7.5 | Structural coverage by modified condition/decision coverage (level A) | 0 |
A-7.6 | Structural coverage by decision coverage (levels A and B) | 1 |
A-7.7 | Structural coverage by statement coverage (levels A to C) | 2 |
A-7.8 | Data coupling and control coupling exercised by the tests | 0 |
A-7.9 | Compiler-generated code not traceable to source verified (level A) | 0 |
A-8.1 | Configuration items identified | 2 |
A-8.2 | Baselines set and traceability kept | 1 |
A-8.3 | Problem reporting, change control, change review and status accounting in place | 4 |
A-8.4 | Archiving, retrieval and release in place | 2 |
A-8.5 | Software load control in place | 1 |
A-8.6 | Life cycle environment under control | 1 |
A-9.1 | Quality assurance confirms plans and standards were produced and reviewed for conformity and consistency | 1 |
A-9.2 | Quality assurance confirms the processes follow the approved plans | 3 |
A-9.3 | Quality assurance confirms the processes follow the approved standards | 0 |
A-9.4 | Quality assurance confirms transition criteria are met | 0 |
A-9.5 | Quality assurance confirms the software conformity review is held | 1 |
REG | Recognition, supporting documents and regulator material around DO-178C | 0 |