If you’re developing security or safety-critical software for aerospace or defence applications, you need complete confidence in your software development and test processes to help you meet FAA, EASA, or other regulatory requirements.
In these sectors, requirements for both safety and security continue to rise. The DO-178B standard has evolved into DO-178C, improving safety requirements and accommodating new technologies for development and verification. And increasingly, standards developed for the aerospace sector have been recognised as a best practice and have been adopted in other security and safety-critical markets such as defence, even though there is no certification requirement.
Beyond the needs to meet stringent requirements, aerospace and defence projects become even more challenging due to lengthy development schedules— during which targets and specifications can evolve over several years—as well as large, geographically dispersed teams. At the same time, the stakes keep rising: budgets are tighter, deadlines are shorter, and the risks of non-compliance have never been higher.
Coding standards such as MISRA C and MISRA C++, JSF++ AV, CWE, CERT C, CERT C++, and CERT Java have been developed specifically to improve code quality, safety, and security and are increasingly leveraged by software organisations in aerospace and defence industries. However, manually enforcing these standards comes at the price of time, effort, money, and—ironically—quality, as the manual process is complex and error-prone. To reduce costs and improve productivity, development organisations need to automate support for compliance to coding standards as well as frameworks such as the Future Airborne Capability Environment (FACE).