- ConsuNova brings together valuable experience to deliver free technical whitepapers in various safety-critical standards and industry domains.
- The intent of ConsuNova avionics whitepapers is to educate our community for the challenges ahead, while providing the most effective path to avionics certificaiton 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 whitepaper discusses interactions of ARP 4761 and ARP 4754A in an IMA system and how DO-178B/C processes and objectives, the software failure rate objectives dedicated to the partition software are identified, verified and fed back to the item level FMEA. This 10-page paper includes main topics such as:
- Optimized Safety Assessemnt Process for IMA Systems
- Allocation of the Software Failure Rate
- Interactions between Partition and IMA Platform
- Failure Mode of Partition Software
- Verification of the the Software Failure Rate
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.
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).
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.
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.
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.
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.
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.