SOI-1 to 4_Preparations
SOI-1 to 4_Preparations
DO-178C DO-178C
DO-254
▪ Primary Standard: Widely adopted for demonstrating the safety of software in aircraft and aerospace systems.
▪ Guiding Design: Provides a framework for the development process to produce aircraft suitable for flight and
international markets.
▪ Historical Evolution: Originated in the 1970s with increasing software integration, evolving from prescriptive to
objective-based.
▪ Development Assurance Levels (DALs): Defines five levels (A-E) based on the criticality of software failure
(Catastrophic to No effect on safety).
▪ Risk-Based Rigor: Higher DALs (higher risk) require more stringent certification processes.
▪ Key Development Stages: Outlines required stages for planning, development, and implementation of safe
software.
▪ Objective-Driven Approach: Offers flexibility in how organizations meet the standard's objectives.
▪ Focus on Safety: Fundamentally aimed at ensuring high-quality and safe aviation software.
▪ International Relevance: Supports the development of aircraft ready for global markets.
ARP4754A
DO-254 DO-178C
DO-254
•Classification System:
•Starts with categorizing electronic hardware as either simple or complex.
•Provides tailored systematic design guidelines for both categories.
•Design Assurance Levels (DALs):
•Similar to DO-178C, it utilizes a DAL framework (Levels A-E).
•Level A represents the most severe impact of hardware failure.
•Compliance efforts scale with the potential damage of a hardware failure.
•Historical Recognition: Formally recognized by the FAA in 2005.
•Initial Discrepancy:
•Initially, EASA (European Aviation Safety Agency) didn't have the same formal recognition.
•This led to confusion, particularly for simple hardware.
•EASA Clarification (2020):
•EASA AMC 20-152A provided formal recognition and clarification on DO-254.
•Established new compliance objectives for different types of hardware.
SOI-1 Planning Review
SOI-1
Purpose:
• Verify that system development planning and initial requirements processes are adequate
for safety objectives in ARP4754A
• Confirm that software planning processes and initial requirements align objectives in DO-
178C
• Ensure hardware planning processes and initial requirements meet objectives in DO-254
ARP4754A
SOI-System Level:
Type Document Name Description
Input Plan for Software Aspects of Certification (PSAC) Overall strategy for DAL B software compliance.
Describes development activities: requirements,
Input Software Development Plan (SDP)
design, coding.
Defines testing and review activities (moderate
Input Software Verification Plan (SVP)
independence for DAL B).
Input Software Configuration Management Plan (SCMP) Config control for software artifacts.
Input Software Quality Assurance Plan (SQAP) Describes QA activities for software.
Input Software Requirements Standards (SRS) Format and structure of high-level requirements.
Input Software Design Standards (SDS) (preliminary) Early design guidance and rules.
Input Software Code Standards (SCS) (preliminary) Initial code development standards.
Input System Requirements Allocated to Software Allocated from ARP4754A SRD.
Input Preliminary Software Requirements Document Captures high-level SW requirements.
Output SOI-1 Audit Report Review summary and corrective actions.
Output Updated PSAC If audit findings require revision.
Output Updated SDP, SVP, SCMP, SQAP If refinements are identified.
System Level (ARP4754A) - SOI-1 Documents
ARP4754A
SOI-Software Level:
Type Document Name Description
Describes system-level processes including
Input System Development Plan (SDP)
requirements, validation, and V&V.
Defines safety assessment process: FHA and
Input Safety Program Plan (SPP)
PSSA.
Input System Requirements Document (SRD) (preliminary) High-level system requirements derived from FHA.
Identifies failure conditions and assigns DAL B
Input Functional Hazard Assessment (FHA) (preliminary)
classification.
Input Certification Plan Compliance approach with FAA/EASA for DAL B.
Input Configuration Management Plan (CMP) Configuration control strategy for DAL B systems.
Input Quality Assurance Plan (QAP) QA methods for process and product quality.
Input
If applicable — defines oversight of supplier-
(optional Supplier Management Plan
provided systems/components.
)
Output SOI-1 Review Report Audit findings, gap analysis, corrective actions.
Output Updated System Development Plan Incorporates findings if any.
Output Updated Safety Program Plan Refined safety processes if required.
Output Refined Preliminary SRD Ensures traceability and completeness for DAL B.
System Level (ARP4754A) - SOI-1 Documents
ARP4754A
SOI-Hardware Level:
Type Document Name Description
Input Plan for Hardware Aspects of Certification (PHAC) Strategy for hardware compliance with DO-254.
Input Hardware Development Plan (HDP) Describes lifecycle activities for DAL B hardware.
Input Hardware Verification Plan (HVP) Describes reviews, analyses, and testing.
Input Hardware Configuration Management Plan (HCMP) Configuration control methods.
Input Hardware Quality Assurance Plan (HQAP) QA process for hardware development.
Input Hardware Requirements Standards (HRS) Format and traceability expectations for requirements.
Input Hardware Design Standards (HDS) (preliminary) Preliminary design guidance for hardware.
Input System Requirements Allocated to Hardware Allocated from ARP4754A SRD.
Input Preliminary Hardware Requirements Document Captures high-level hardware needs.
Output SOI-1 Audit Report Summary of compliance to DO-254, including gaps.
Output Updated PHAC If needed based on findings.
Output Updated HDP, HVP, HCMP, HQAP Revised to close identified gaps.
Output Refined Hardware Requirements Standards Updated per SOI-1 feedback.
SOI-1 Planning Review
ARP4754A
SOI-System Level:
Type Document Name Description
Input Plan for Software Aspects of Certification (PSAC) Overall strategy for DAL B software compliance.
Describes development activities: requirements,
Input Software Development Plan (SDP)
design, coding.
Defines testing and review activities (moderate
Input Software Verification Plan (SVP)
independence for DAL B).
Input Software Configuration Management Plan (SCMP) Config control for software artifacts.
Input Software Quality Assurance Plan (SQAP) Describes QA activities for software.
Input Software Requirements Standards (SRS) Format and structure of high-level requirements.
Input Software Design Standards (SDS) (preliminary) Early design guidance and rules.
Input Software Code Standards (SCS) (preliminary) Initial code development standards.
Input System Requirements Allocated to Software Allocated from ARP4754A SRD.
Input Preliminary Software Requirements Document Captures high-level SW requirements.
Output SOI-1 Audit Report Review summary and corrective actions.
Output Updated PSAC If audit findings require revision.
Output Updated SDP, SVP, SCMP, SQAP If refinements are identified.
System Level (ARP4754A) - SOI-1 Documents
ARP4754A
SOI-Software Level:
Type Document Name Description
Describes system-level processes including
Input System Development Plan (SDP)
requirements, validation, and V&V.
Defines safety assessment process: FHA and
Input Safety Program Plan (SPP)
PSSA.
Input System Requirements Document (SRD) (preliminary) High-level system requirements derived from FHA.
Identifies failure conditions and assigns DAL B
Input Functional Hazard Assessment (FHA) (preliminary)
classification.
Input Certification Plan Compliance approach with FAA/EASA for DAL B.
Input Configuration Management Plan (CMP) Configuration control strategy for DAL B systems.
Input Quality Assurance Plan (QAP) QA methods for process and product quality.
Input
If applicable — defines oversight of supplier-
(optional Supplier Management Plan
provided systems/components.
)
Output SOI-1 Review Report Audit findings, gap analysis, corrective actions.
Output Updated System Development Plan Incorporates findings if any.
Output Updated Safety Program Plan Refined safety processes if required.
Output Refined Preliminary SRD Ensures traceability and completeness for DAL B.
System Level (ARP4754A) - SOI-1 Documents
ARP4754A
SOI-Hardware Level:
Type Document Name Description
Input Plan for Hardware Aspects of Certification (PHAC) Strategy for hardware compliance with DO-254.
Input Hardware Development Plan (HDP) Describes lifecycle activities for DAL B hardware.
Input Hardware Verification Plan (HVP) Describes reviews, analyses, and testing.
Input Hardware Configuration Management Plan (HCMP) Configuration control methods.
Input Hardware Quality Assurance Plan (HQAP) QA process for hardware development.
Input Hardware Requirements Standards (HRS) Format and traceability expectations for requirements.
Input Hardware Design Standards (HDS) (preliminary) Preliminary design guidance for hardware.
Input System Requirements Allocated to Hardware Allocated from ARP4754A SRD.
Input Preliminary Hardware Requirements Document Captures high-level hardware needs.
Output SOI-1 Audit Report Summary of compliance to DO-254, including gaps.
Output Updated PHAC If needed based on findings.
Output Updated HDP, HVP, HCMP, HQAP Revised to close identified gaps.
Output Refined Hardware Requirements Standards Updated per SOI-1 feedback.
TO add slides
https://thecloudstrap.com/do178c-interview-questions/