- ConsuNova DO-178C whitepapers cover wide range of topics; from understanding DO-178B to efficient planning and optimized strategies in DO-178C development, verification and certification success.
- Select your area of interest, fill in the short form below, and we will send our proprietary and up-to-date whitepaper.
This whitepaper explains the seven principles of development that can be applied to the development of Avionics Systems and Equipment. These principles can, and should, be applied to engineering activities of any discipline – including Systems (ARP 4754A), Software (DO-178C) and Hardware (DO-254). In thinking about the Principles of Development we should consider three dimensions of development and how each of the principles affects that dimension:
1. The Process - The process dimension consists of the definition of the process, the execution of the process, and evidence, or data, left behind by the execution of the process.
2. The Product - The product dimension consists of all the elements of the product; requirements, design, implementation, verification, etc.
3. The Management - The management dimension consists of planning (or scheduling), organization, communication, and risks.
This DO-178C white paper, is based on ConsuNova’s recurrent Avionics Gap Analyses performed worldwide over the years. Some experts say that plans should detail every aspect of software process. However, based on ConsuNova involvements in many projects, there is a fine line between “detailed planning” and “good planning”. The discussions in this 16-page white paper focuses on important Challenges, Recommendations and “takeaways” related to the Planning aspects. DO-178C Optimization Tactics shows the reader the specific examples on how to improve DO-178C planning with adequate content and strategy to achieve successful compliance in optimized manner while governing a practical process for the DO-178C life-cycle during the project.
This whitepaper discusses why ARP 4754A, DO-178C and DO-254 place emphasis on writing correct, complete and testable requirements. ConsuNova provides this paper to introduce a framework of rules for capturing functional requirements which should minimize program risk and maintain schedules.
For the construction and safety certification of airborne systems software, the software tools used to build this software generally needs to be qualified. This qualification provides evidence that the software too is suitable for use, when building such safety-related airborne software. This paper identifies the major activities outlined in DO-330, along with a description of the impact it has on the industry at large. It also examines the relationship between DO-178C and DO-330.
The purpose of this ConsuNova white paper is to educate the reader in how ConsuNova implements DO-178B on a regular basis. Note that DO-178B was also applied to the development of avionics hardware until the FAA officially recognized the DO-254 standard for developing hardware. Please refer to the ConsuNova’s DO-254 white papers for more information.
For decades, Military organizations have developed hardware and software using a variety of specialized, defense-oriented standards including 2167A, 498, and 882. As Military organizations, they were highly motivated to use hardware and software standards which differed from the commercial sector since it was perceived that military applications were “different”. Militaries utmost concern was primarily “Mission”. Today, however, there is an accelerating momentum toward Military/Commercial avionics convergence: adopting DO-178B and DO-254 worldwide. Today, fighter jets (Joint Strike Fighter, T-50, etc.), Cargo planes (C-130, C-17, A400M, etc.) and UAV/UAS’s are requiring compliance to DO-178 and increasingly, DO-254.
Tool qualification is required whenever the design assurance process(es) described in RTCA/DO-178B or RTCA/DO-254 are eliminated, reduced, or automated by the use of the tool unless the output of the tool is verified. Verification of the tool’s output must be accomplished through the verification process as defined by RTCA/DO-178B section 6.
Safety-critical systems including DO-178C and DO-254 require traceability. But what is DO-178 and DO-254 Traceability? This whitepaper describes all aspects of DO178 and DO254 traceability including top-to-bottom and bottom-to-top closed loop traceability for DO-178C and DO-254. Popular traceability tools for DO-178C & DO-254 are discussed as well as traceability trade-offs for D0-178B and D0-254. Requirements traceability, design traceability, and test traceability within DO-254 and DO-178 are all described along with means to maximize effectiveness for DO-178C & DO254 traceability.
What are the most common mistakes via DO-178? As the largest, and fastest-growing, avionics-related services companies in North America, we’ve captured both ours, and our clients, most common mistakes; and we’ve learned from them. Through this learning process, we hope that the skies are safer and our clients are more successful.
The DO-178B guidelines describe objectives for software life-cycle processes, activities and design considerations for achieving those objectives, and proving that the objectives have been satisfied. The majority of DO-178B is dedicated to describing a sequential waterfall development methodology for new, custom-built avionics software. This approach is a requirements-based development and verification methodology that includes a number of alternative methods for satisfying the objectives.
DO-178B is the benefactor, or bane, of avionics projects the world over. But is DO-178B really expensive? Does it add value? Will it improve safety and reliability? Does it have benefits? What are the true costs versus benefits? These important questions are answered in this ConsuNova White Paper.