Aldec Design and Verification 
Louie De Luna
Louie is responsible for FPGA level in-target testing technology and requirements lifecycle management for DO-254 and other safety-critical industry standards. He received his B.S. in Computer Engineering from University of Nevada in 2001. His practical engineering experience includes areas in … More » Following the Roadmap to Successful TraceabilitySeptember 23rd, 2013 by Louie De Luna
– Roads connect two or more places on a map; traceability connects two or more elements in a project (such as functions, requirements, concept, design, verification data and test results). – Road names help identify specific places that are linked to it; traceability names help identify specific project elements that are linked to it. – In the absence of roads, reaching your destination is practically impossible; in the absence of traceability achieving compliance is also practically impossible. According to DO-254 guidance, traceability is the correlation between the individual system requirements, hardware requirements, conceptual design, detailed design, implementation and verification results. Traceability entails that all system functions are traceable all the way down to the FPGA requirements, verification test cases and test results. This ensures that the development process for the system and FPGA is requirements-based. For the rest of this article, visit the Aldec Design and Verification Blog. Tags: Aldec, cca, circuit card assembly, conceptual design, detailed design, do-254, FPGA, fpga requirements, hardware design process, hardware requirements, HDL Design, implementation, individual system requirements, requirements capture, spec-tracer, test results, Traceability, verification results, verification test cases Category: Requirements Management |
|
|
|||||
|
|
|||||
|
|||||
