The rules this is built from, and the regimes around the buyer
The product reads the ISO/IEC/IEEE 29148:2018 requirement set in full. The four markets below are the jurisdictions a requirements lead usually meets beside it. The relevant sector framework is named for each market where one is held; where it is not held, the page says so and does not state its text.
The record that applies today
The record has 50 clause and information item pages plus 10 Annex pages. The clause pages state the requirement, the evidence and the common gaps, each cited to ISO/IEC/IEEE 29148:2018. The full register is the index.
Four markets, chosen by scan
FDA QMSR and 21 CFR Part 11
A medical device software project that uses 29148 for its requirements may also be subject to the FDA quality management system regulation and, where records are electronic, 21 CFR Part 11. Both are held and named here. They govern the product and the records, not the requirements method itself. Using 29148 does not by itself establish compliance with either.
FDA QMSR / 21 CFR Part 11MDR 2017/745 and EN 50716
Medical device software sits under the Medical Devices Regulation, which sets its own software lifecycle and risk file expectations; a 29148 requirement set can feed them. Railway software has its own requirements standard in EN 50716. Both are held and named here.
EU MDR / EN 50716DO-326A and ISO 19650
Airworthiness security under DO-326A applies to airborne systems and their requirements. ISO 19650 governs information requirements in construction and asset management. Both are held and named here. There is no held UK statute specific to requirements engineering as a discipline.
DO-326A / ISO 19650No held requirements engineering regime
The scan found no held Australian instrument that governs requirements engineering as a discipline. The Therapeutic Goods Administration regulates medical devices, but its essential principles are not held here, so this page names the regulator and does not state the requirement. The project's own contract and sector scheme fill the gap.
Named, not held. See the sources page.The rules this is built from
Every line names its source. The 60 records are written from the published ISO/IEC/IEEE 29148:2018, in our words, with the clause cited. The revision layer is read from the public ISO stage record and its scope abstract. Where the public record is silent, the page says so.
Clause by clause, and the information items
Each page states the requirement in our words, the evidence an assessor asks for, the common gaps and what to do before the edition changes.
Open the registerThe OpsCon content, labelled
Annex A content is part of a full conformance claim. Annex B is informative. Annex C is the tailoring process.
Open Annex ANo invented date
The DIS is at 40.20. The planning date is an estimate and is labelled wherever it appears.
Read the revision recordThe ISO/IEC/IEEE 29148:2018 text is not reproduced. The DIS requirement text is not public and is not reproduced. The record this site reads is linked on the standards page.