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 | The activities of the software life cycle processes are defined | 0 |
A-1.2 | The software life cycle, including the inter-relationships between the processes, their sequencing, feedback mechanisms and transition criteria, is defined | 0 |
A-1.3 | The software life cycle environment is selected and defined | 0 |
A-1.4 | Additional considerations are addressed | 0 |
A-1.5 | Software development standards are defined | 0 |
A-1.6 | Software plans comply with this document | 0 |
A-1.7 | Development and revision of software plans are coordinated | 0 |
A-10.1 | Communication and understanding between the applicant and the certification authority is established | 0 |
A-10.2 | The means of compliance is proposed and agreement with the Plan for Software Aspects of Certification is obtained | 0 |
A-10.3 | Compliance substantiation is provided | 0 |
A-2.1 | High-level requirements are developed | 0 |
A-2.2 | Derived high-level requirements are defined and provided to the system processes, including the system safety assessment process | 0 |
A-2.3 | Software architecture is developed | 0 |
A-2.4 | Low-level requirements are developed | 0 |
A-2.5 | Derived low-level requirements are defined and provided to the system processes, including the system safety assessment process | 0 |
A-2.6 | Source Code is developed | 0 |
A-2.7 | Executable Object Code and Parameter Data Item Files, if any, are produced and loaded in the target computer | 0 |
A-3.1 | High-level requirements comply with system requirements | 0 |
A-3.2 | High-level requirements are accurate and consistent | 0 |
A-3.3 | High-level requirements are compatible with target computer | 0 |
A-3.4 | High-level requirements are verifiable | 0 |
A-3.5 | High-level requirements conform to standards | 0 |
A-3.6 | High-level requirements are traceable to system requirements | 0 |
A-3.7 | Algorithms are accurate | 0 |
A-4.1 | Low-level requirements comply with high-level requirements | 0 |
A-4.10 | Software architecture is compatible with target computer | 0 |
A-4.11 | Software architecture is verifiable | 0 |
A-4.12 | Software architecture conforms to standards | 0 |
A-4.13 | Software partitioning integrity is confirmed | 0 |
A-4.2 | Low-level requirements are accurate and consistent | 0 |
A-4.3 | Low-level requirements are compatible with target computer | 0 |
A-4.4 | Low-level requirements are verifiable | 0 |
A-4.5 | Low-level requirements conform to standards | 0 |
A-4.6 | Low-level requirements are traceable to high-level requirements | 0 |
A-4.7 | Algorithms are accurate | 0 |
A-4.8 | Software architecture is compatible with high-level requirements | 0 |
A-4.9 | Software architecture is consistent | 0 |
A-5.1 | Source Code complies with low-level requirements | 0 |
A-5.2 | Source Code complies with software architecture | 0 |
A-5.3 | Source Code is verifiable | 0 |
A-5.4 | Source Code conforms to standards | 0 |
A-5.5 | Source Code is traceable to low-level requirements | 0 |
A-5.6 | Source Code is accurate and consistent | 0 |
A-5.7 | Output of software integration process is complete and correct | 0 |
A-5.8 | Parameter Data Item File is correct and complete | 0 |
A-5.9 | Verification of Parameter Data Item File is achieved | 0 |
A-6.1 | Executable Object Code complies with high-level requirements | 0 |
A-6.2 | Executable Object Code is robust with high-level requirements | 0 |
A-6.3 | Executable Object Code complies with low-level requirements | 0 |
A-6.4 | Executable Object Code is robust with low-level requirements | 0 |
A-6.5 | Executable Object Code is compatible with target computer | 0 |
A-7.1 | Test procedures are correct | 0 |
A-7.2 | Test results are correct and discrepancies explained | 0 |
A-7.3 | Test coverage of high-level requirements is achieved | 0 |
A-7.4 | Test coverage of low-level requirements is achieved | 0 |
A-7.5 | Test coverage of software structure (modified condition/decision coverage) is achieved | 0 |
A-7.6 | Test coverage of software structure (decision coverage) is achieved | 0 |
A-7.7 | Test coverage of software structure (statement coverage) is achieved | 0 |
A-7.8 | Test coverage of software structure (data coupling and control coupling) is achieved | 0 |
A-7.9 | Verification of additional code, that cannot be traced to Source Code, is achieved | 0 |
A-8.1 | Configuration items are identified | 0 |
A-8.2 | Baselines and traceability are established | 0 |
A-8.3 | Problem reporting, change control, change review and configuration status accounting are established | 0 |
A-8.4 | Archive, retrieval and release are established | 0 |
A-8.5 | Software load control is established | 0 |
A-8.6 | Software life cycle environment control is established | 0 |
A-9.1 | Assurance is obtained that software plans and standards are developed and reviewed for compliance with this document and for consistency | 0 |
A-9.2 | Assurance is obtained that software life cycle processes comply with approved software plans | 0 |
A-9.3 | Assurance is obtained that software life cycle processes comply with approved software standards | 0 |
A-9.4 | Assurance is obtained that transition criteria for the software life cycle processes are satisfied | 0 |
A-9.5 | Assurance is obtained that software conformity review is conducted | 0 |