DO-278A Best Practices

DO-278A Best Practices

Certain good aviation software development practices are self-evident. For software, the obvious good practices include utilizing defect prevention, experienced developers, automated testing, and fewer changes. This paper isn’t about the obvious, as it is assumed the reader is educated by virtue of making it to this page. Instead, this AFuzion DO-278A Best Practices identified herein are subtler and considerably “less practiced”, and have been deployed by AFuzion’s CNS/ATM engineers and auditors on many leading worldwide CNS/ATM projects in America, Europe, Australia, Asia, and the Middle East. Why focus on the critical path Best Practices for CNS/ATM and DO-278A deployment? Simple: today’s CNS/ATM projects are growing massively in complexity, with strong tendencies to automate former manual (controller) activities. For business reasons, engineering management is loath to affect the critical path.

The following figure summarizes the Top 10 not-always-obvious DO-278A Best Practices. The detailed table following provides use-case information intended to help the CNS/ATM DO-278A practitioner (and auditor) perform KPI-based analysis to determine the efficacy of deploying the various best practices. (Note: Details of all the above mentioned details are contained within the following pages of this paper (download to read). For additional DO-278A training, guidance, gap analysis, and mentoring, simply contact AFuzion.)

Free: Download Remaining 10+ Page Paper Here