Industry Whitepapers

DO-254 Whitepaper Research
  • ConsuNova brings together valuable experience to deliver free technical whitepapers in various safety-critical standards and industry domains.
  • The intent of ConsuNova industry whitepapers is to educate our community for the challenges ahead while providing the most effective path to success.
  • See DO-178 whitepapers and DO-254 whitepapers for specific related standards.

Latest Whitepapers:

Top DO-178C Optimization Tactics for Planning Aspects
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.

8 Steps of Reverse Engineering to show DO-254 Compliance
This DO-254 whitepaper introduces a methodology, which can be used to developing a process which will allow reverse engineering of a Proof of Concept (PoC) prototype FPGA to gain compliance to DO-254. This paper represents an alternate means of complying with DO-254 (as DO-254 does not recognize a Reverse Engineering process).

Practical Rules for ARP 4754A Requirements Capture
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.

Understanding DO-297 Integrated Modular Avionics (IMA)
This paper identifies the major aspects of Integrated Modular Avionics (IMA) and guidance for IMA developers, integrators, applicants, and those involved in the approval and continued airworthiness of IMA systems (DO-297). This paper also provides an overview of the role of participants in IMA development and compliance.

Aircraft System Safety Assessment
This DO-254 whitepaper details the DO-254 certification process, DO254 compliance, commercial and military DO-254, and DO-254 strategies and issues. The DO-254 guideline is applicable to all hierarchical stratifications of hardware developed for airborne systems including Line Replaceable Units (LRUs), Circuit Card/Board Assemblies (CCAs), custom micro-coded components (e.g. ASIC, PLD, FPGA, CPLD), integrated hybrids and multi-chip components, and Commercial-Off-The-Shelf (COTS) devices.

Advanced static analysis techniques for verification
This paper describes how recent developments in static analysis techniques, so called Static Verification, can be efficiently used in conjunction with functional testing techniques in order to substantially reduce debugging, code inspection, and robustness testing efforts. The paper elaborated on the key features static analyzers should have for bringing software engineers actual added value during their software development process (exhaustiveness and in-depth analysis to handle both “false positive” and “false negative” issues).

Global Positioning System (GPS) Mathematics
This white paper describes how a GPS receiver performs the calculation of a user’s latitude, longitude, and altitude. First, a basic discussion of the Least Squares Approximation Theory is provided, as such is the basis for subsequent calculations. For a basic discussion of GPS theory, first read “GPS Theory” white paper. It is presumed the reader of this GPS Mathematics white paper has a basic understanding of GPS theory, algebra, and calculus.

Software tips for successful 510(k) submissions
Once upon a time, there was the FDA’s “GMP”, which detailed the “Good Manufacturing Practices” for medical device software. However, “Good” occasionally meant “Far From Great”, and the revolution began. Today, there is a need to develop medical devices from finer-grained subcomponents, with open interfaces that can be composed in flexible ways, to achieve a broad range of functionalities. In addition, these devices need to be network-centric so they can interoperate following a “plug-and-play” paradigm. And all of this advanced software must comply with the FDA’s new 510(k) submission process.

FDA 510(k): Medical Device Software Approval
The FDA 510(k) process regulates the development of a myriad number of increasingly complex medical devices, all within a realm of rapidly evolving software technology. The related questions we receive at ConsuNova are likewise diverse and challenging. However, medical device software development is science, and science must provide answers. This white paper provides a brief background and summarizes the requirements for developing successful medical device software and ensuring FDA 510(k) compliance.