DO-178C has defined airborne software assurance for more than a decade. Its objectives-based structure, emphasis on verification, and alignment with safety analysis have made it the cornerstone of avionics software certification. However, aircraft systems continue to evolve rapidly. Increased autonomy, connectivity, model-based development, artificial intelligence, and continuous software updates are challenging traditional certification paradigms. Therefore, understanding the future of DO-178C requires analyzing how regulatory expectations, technology trends, and engineering practices are converging. This article explores the future of DO-178C by examining expected evolutions, emerging pressures, and likely directions for airborne software assurance.
Why the Future of DO-178C Matters
DO-178C influences how avionics software is designed, verified, and certified. Therefore, changes to this standard have far-reaching consequences.
Future evolution matters because:
Software complexity continues to increase
Development cycles accelerate
New technologies challenge traditional assumptions
Certification timelines must remain predictable
As a result, industry stakeholders must anticipate change rather than react to it.
Section summary:
The future of DO-178C affects engineering practices, certification cost, and aircraft safety.
Stability as a Core Principle
One defining characteristic of DO-178C is stability. Unlike rapidly changing software standards, DO-178C evolves cautiously.
This stability exists because:
Certification relies on predictable requirements
Aircraft lifecycles span decades
Regulatory confidence depends on proven processes
Therefore, the future of DO-178C will likely favor evolution rather than replacement.
Section summary:
DO-178C prioritizes stability to preserve certification predictability.
Lessons Learned from DO-178B to DO-178C
The transition from DO-178B to DO-178C provides insight into future evolution. DO-178C did not redefine core objectives. Instead, it introduced supplements.
Key lessons include:
Core principles remain unchanged
Supplements address new technologies
Backward compatibility is preserved
This pattern strongly suggests how future updates may occur.
Section summary:
DO-178C evolution favors extensions over radical change.
Role of Supplements in the Future of DO-178C
Supplements represent the primary mechanism for adapting DO-178C to new technologies. Therefore, future change will likely occur through additional guidance rather than a new base standard.
Existing supplements already address:
Model-Based Development (DO-331)
Tool Qualification (DO-330)
Formal Methods (DO-333)
Future supplements may address emerging development paradigms.
Section summary:
Supplements allow DO-178C to adapt without destabilizing the core standard.
Model-Based Development as a Long-Term Driver
Model-Based Development continues to mature. Therefore, its influence on DO-178C will increase.
Future expectations may include:
Deeper integration of model verification
Improved traceability automation
Better alignment between model and code coverage
However, fundamental verification objectives will remain unchanged.
Section summary:
MBD will shape future guidance without weakening assurance rigor.
Artificial Intelligence and Machine Learning Challenges
Artificial intelligence introduces behaviors that are difficult to specify deterministically. Therefore, AI challenges traditional DO-178C assumptions.
Key challenges include:
Non-deterministic behavior
Training-based development
Difficulty in defining complete requirements
Consequently, AI will likely require separate guidance rather than direct inclusion in DO-178C.
Section summary:
AI challenges may lead to parallel guidance rather than DO-178C replacement.
Increasing Automation and Tool Dependence
Automation continues to expand across avionics development. Therefore, tool qualification importance will increase.
Future trends include:
Greater reliance on code generation
Automated verification and analysis
Continuous integration pipelines
As a result, DO-330 and tool assurance will gain greater prominence.
Section summary:
Tool qualification will become more central in future certification.
Continuous Airworthiness and Software Updates
Aircraft software increasingly receives post-certification updates. Therefore, traditional certification assumptions face pressure.
Future considerations include:
Incremental certification approaches
Impact-based change assessment
Reuse of verification evidence
DO-178C already supports change management, but expectations may evolve.
Section summary:
Continuous updates will drive refinement of change management practices.
Integration with Cybersecurity Standards
Cybersecurity concerns continue to grow. Therefore, integration between DO-178C and DO-326A will deepen.
Future integration may include:
Shared assurance artifacts
Coordinated safety and security analyses
Unified architectural assumptions
This integration will remain evolutionary rather than disruptive.
Section summary:
Safety and security assurance will become more tightly coupled.
Certification Authority Perspective on Future Change
Authorities value clarity and predictability. Therefore, any evolution of DO-178C will proceed conservatively.
Authority priorities include:
Maintaining safety levels
Avoiding unnecessary disruption
Supporting innovation responsibly
Industry collaboration will shape future guidance.
Section summary:
Authorities favor gradual, consensus-driven evolution.
Industry Expectations and Pressure Points
Industry stakeholders seek efficiency improvements. However, they also recognize the need for rigorous assurance.
Common expectations include:
Reduced rework through better guidance
Improved clarity on emerging technologies
More consistent interpretation across authorities
These pressures influence future updates indirectly.
Section summary:
Industry seeks clarity and efficiency without reducing assurance rigor.
Potential Areas of Future Guidance
Based on current trends, likely future focus areas include:
Advanced modeling and abstraction
Improved reuse of certification credit
Clarification of data-driven verification
Enhanced guidance for mixed-criticality systems
However, these areas will likely appear as guidance material rather than new objectives.
Section summary:
Future guidance will address complexity while preserving core principles.
Why DO-178C Will Not Be Replaced Soon
Despite criticism, DO-178C remains effective. Therefore, replacement remains unlikely.
Key reasons include:
Proven safety record
Global regulatory acceptance
Flexibility through supplements
Evolution will remain incremental.
Section summary:
DO-178C’s strength lies in adaptability rather than obsolescence.
Preparing for the Future of DO-178C
Organizations can prepare proactively for future evolution.
Preparation strategies include:
Strong fundamentals in requirements and verification
Early adoption of supplements
Robust tool qualification discipline
Continuous engagement with regulatory guidance
Strong fundamentals outlast standard updates.
Section summary:
Organizations prepared for change focus on fundamentals.
Long-Term Vision for Airborne Software Assurance
The long-term vision emphasizes confidence rather than compliance. Therefore, future assurance will focus on demonstrating trustworthiness.
Key elements include:
Clear safety arguments
Objective evidence
Transparent assumptions
DO-178C will continue to support this vision.
Section summary:
Future assurance emphasizes trust and evidence, not checkbox compliance.
Conclusion
The future of DO-178C will not involve abrupt replacement or radical transformation. Instead, it will follow a deliberate path of evolution driven by supplements, guidance material, and industry consensus. Emerging technologies such as model-based development, increased automation, cybersecurity integration, and artificial intelligence will shape how DO-178C is applied, but not its fundamental objectives. Organizations that master DO-178C fundamentals today will remain well positioned for tomorrow. Ultimately, DO-178C’s future lies in its ability to adapt while preserving the uncompromising safety assurance that aviation demands.
WRITTEN BYMusa ToktaşMusa Toktas is the Managing Director at Heraklet, a software engineering and R&D consultancy focused on aviation software and secure systems. His work centers on building and scaling certification-minded engineering practices for safety and compliance driven programs, including DO-178C software assurance, DO-254 hardware assurance, and the systems engineering and safety framework of ARP-4754A and ARP-4761. He also works on security governance and implementation for networked systems, covering secure architecture, risk management, and operational controls aligned with ISO 27001. Musa writes about reliable software delivery in regulated environments, verification and traceability, secure development practices, and designing resilient networked platforms.
More Stories from
Musa Toktas is the Managing Director at Heraklet, a software engineering and R&D consultancy focused on aviation software and secure systems. His work centers on building and scaling certification-minded engineering practices for safety and compliance driven programs, including DO-178C software assurance, DO-254 hardware assurance, and the systems engineering and safety framework of ARP-4754A and ARP-4761. He also works on security governance and implementation for networked systems, covering secure architecture, risk management, and operational controls aligned with ISO 27001. Musa writes about reliable software delivery in regulated environments, verification and traceability, secure development practices, and designing resilient networked platforms.



