Standards
What each standard asks of the trace
Eight standards, each shown when you tick it. With nothing ticked the trace and the findings show, and no clause.
- Requirements traceability in ISO 26262road vehicles functional safety; 11 clauses cited
- Requirements traceability in Automotive SPICEthe Automotive SPICE process assessment model, its system, software and hardware engineering base practices; 11 clauses cited
- Requirements traceability in IATF 16949automotive quality management, the design and development supplementals; 2 clauses cited
- Requirements traceability in IEC 62304medical device software life cycle processes; 11 clauses cited
- Requirements traceability in ISO 13485medical device quality management, design and development controls; 5 clauses cited
- Requirements traceability in FDA QMSRthe US Quality Management System Regulation, which incorporates ISO 13485 by reference and adds FDA-specific provisions; 2 clauses cited
- Requirements traceability in DO-178Csoftware considerations in airborne systems and equipment certification; 10 clauses cited
- Requirements traceability in AS9100Daviation, space and defence quality management, design and development; 4 clauses cited
Named, not quoted
- DO-254 (airborne electronic hardware): the hardware counterpart of DO-178C, with its own requirements capture and traceability objectives. We do not hold its text, so it is named and never quoted.
- IEC 61508 (functional safety of electrical, electronic and programmable electronic systems): the generic functional safety standard ISO 26262 was adapted from. We do not hold its text, so it is named and never quoted.
- ARP4754B (development of civil aircraft and systems): the aircraft and system development process whose requirements DO-178C and DO-254 receive. We do not hold its text, so it is named and never quoted.
- ISO 14971 (application of risk management to medical devices): the risk management standard IEC 62304 and ISO 13485 point to for the hazard analysis a medical device requirement traces to; not in the held clause set, so named and never quoted. We do not hold its text, so it is named and never quoted.
- ISO/IEC/IEEE 29148 (requirements engineering): the requirements engineering standard that sets out the characteristics of a well-formed requirement. We do not hold its text, so it is named and never quoted.