What is DO-178C and why is it relevant to Boeing software development?

What is DO-178C and why is it relevant to Boeing software development?

• A. A mechanical design standard.
• B. An airborne software safety standard defining lifecycle processes and objectives based on software level (A-D) to ensure flight-safety-compliant software.
• C. A standard for electrical wiring interconnect systems in aircraft.
• D. A regulation specifying pilot training programs.

Answer: (B)

DO-178C is an airborne software safety standard that defines the lifecycle processes and objectives for software used in aircraft, tailored to how critical the software is. It specifies what activities must be performed—planning, requirements development, design, coding, integration, verification, configuration management, and quality assurance—and the evidence needed to show compliance. The standard uses software levels (A through D in this framing, with higher levels requiring more rigorous verification and documentation) to determine how stringent the objectives and V&V activities must be. This structure ensures that flight-safety-critical software behaves correctly in all expected and fault conditions, which is essential for certification by authorities like the FAA. In Boeing software development, DO-178C is relevant because projects must demonstrate airworthiness through this standard’s processes. By following DO-178C, developers establish traceability from requirements through design and tests, prove thorough verification and validation, and manage changes in a controlled way. It also covers how to qualify development and verification tools, and, as needed, integrates supplements for formal methods or model-based approaches. This framework helps Boeing deliver software that meets safety goals and receives certification for flight use. The other options describe different domains (mechanical design, wiring/interconnect hardware, or pilot training) and do not address airborne software safety standards.

DO-178C is an airborne software safety standard that defines the lifecycle processes and objectives for software used in aircraft, tailored to how critical the software is. It specifies what activities must be performed—planning, requirements development, design, coding, integration, verification, configuration management, and quality assurance—and the evidence needed to show compliance. The standard uses software levels (A through D in this framing, with higher levels requiring more rigorous verification and documentation) to determine how stringent the objectives and V&V activities must be. This structure ensures that flight-safety-critical software behaves correctly in all expected and fault conditions, which is essential for certification by authorities like the FAA.

In Boeing software development, DO-178C is relevant because projects must demonstrate airworthiness through this standard’s processes. By following DO-178C, developers establish traceability from requirements through design and tests, prove thorough verification and validation, and manage changes in a controlled way. It also covers how to qualify development and verification tools, and, as needed, integrates supplements for formal methods or model-based approaches. This framework helps Boeing deliver software that meets safety goals and receives certification for flight use. The other options describe different domains (mechanical design, wiring/interconnect hardware, or pilot training) and do not address airborne software safety standards.