DO-254 Requirements Traceability
Louie De Luna, Aldec
EDN (June 4, 2013)
DO-254 enforces a strict requirements-driven process for the development of commercial airborne electronic hardware. For DO-254, requirements must drive the design and verification activities, and requirements traceability helps to ensure this.
Introduction
Complex custom micro-coded devices such as PLDs, FPGAs and ASICs used in commercial airborne hardware are subject to the stringent development process outlined in the DO-254 guidance. This means that the design and verification activities for these types of devices must follow the requirements-based development process described in DO-254. The primary purpose of DO-254 is to provide assurance that the device under test meets its intended functions under all foreseeable operating conditions. Requirements express the functions of the device under test; therefore must drive the design and verification activities.
This paper describes requirements traceability according to DO-254 guidance in the context of FPGAs, and provides explanations as to what it means for the applicants. This paper also enumerates the underlying purpose of requirements traceability and the benefits that can be achieved when done correctly.
To read the full article, click here
Related Semiconductor IP
- ARINC 664 (AFDX) End System DO-254 IP Core
- ARINC 429 IP-Core with DO-254 Package
- DO-254 compliant MIL-STD-1553B IP core
- CAN FD Controller DO-254 IP Core
- UART DO-254 IP Core
Related Articles
- Consumer IC Advances -> Meeting MPEG-4 advanced audio coding requirements
- SoC test requirements debated
- Network performance requirements push up microcontroller ante
- Rapid IO fits interconnect requirements for embedded systems
Latest Articles
- Design and Development of a Neuromorphic Silicon Suite: PVT Sensing, Stochastic LIF Inference, On-Chip STDP Learning, and Crossbar Programming
- LLM4RTL: Tool-Assisted LLM for RTL Generation
- Towards Delta Aware Training: Efficient DNN Weight Storage for Resource-Constrained FPGAs
- CHERI-D: Secure and efficient inline object ID for CHERI temporal memory safety
- AIA: A 16nm Multicore SoC for Approximate Inference Acceleration Exploiting Non-normalized Knuth-Yao Sampling and Inter-Core Register Sharing