How the detailed hardware design, such as hardware description language code, constraints, schematics and board layout, and the software low-level requirements and source code are produced to the agreed standards, reviewed and kept traced to requirements. FPGA, board and software engineers, verification engineers and process assurance need it.

1. Purpose and scope

Detailed design produces the data from which hardware and software are built. For programmable devices and ASICs this is the hardware description language code, constraints and any intellectual property configuration; for circuit boards, the schematics, layout and parts list; for software, the low-level requirements and the source code. Each is produced to the standards released in planning and reviewed against them.

The defining rule is traceability in both directions. Every design element traces to a requirement, and every requirement is implemented somewhere. Logic or code that traces to nothing is either justified as derived, and sent to safety, or removed. This keeps unintended function out of the item, which is what the assurance objectives are ultimately about. The stage also writes the verification procedures and cases alongside the design, so verification is ready when the build is.

12 more sections for registered members.

Register or sign in to read on

The full lifecycle detail, with its charts, flows, tables and every section, is for registered members. Registration is free and takes a minute. You come back to this page afterwards.