Edition 3 at DIS ballot, stage 40.20/ Planning date 12 September 2027, an estimate/ ISO/IEC/IEEE 29148:2018 applies today
ISO 29148 Revision CheckerThe requirements record, clause by clause, and the edition that follows it
4.5
ISO/IEC/IEEE 29148:2018
Conformance

Clause 4.5: Tailored conformance

Current editionISO/IEC/IEEE 29148:2018, Clause 4.5Edition 3 at DIS ballotNo public change recorded

Tailored conformance is available for information items, not for the life cycle processes.

What clause 4.5 asks

Tailored conformance is available for information items, not for the life cycle processes. When a project needs a set of information items that does not qualify for full conformance, it selects or modifies the clauses of this document using the tailoring process in Annex C. The tailored text is declared. Conformance is then judged against the declared text, with the tailoring outcomes as evidence.

Why it matters

Tailoring is a documented reduction with a reason, not an excuse for a thin specification. The standard keeps the process provisions out of scope for tailoring because the processes come from 15288 or 12207 and are tailored there. A project that tailors an information item must still be able to show why the removed content was not needed.

In the public record

No clause level change is public for this unit; the DIS keeps the title and scope, and the requirement text is not released.

What good looks like

Record the clause, the change, the reason and the approver in one table. Keep the unmodified clause beside the tailored one. Re-check the declaration when the project changes framework or when the edition changes.

Evidence an assessor asks for

The assessor will compare the declared tailored text with the clause it replaced. A change with no reason is an unexplained exclusion.

  • Tailoring table Each selected or modified clause, the exact change, the reason and the approver
  • Declared text The tailored information item text, versioned and referenced from the conformance statement
  • Tailoring record The Annex C tailoring outcomes that justify the change
  • Review note A dated review confirming the tailored set still meets the project need

Where it commonly fails

  • Clauses removed to match an existing template, with no tailoring record
  • Tailoring used to avoid the Annex A OpsCon content while a full claim is still implied
  • A tailored set that was never re-reviewed after the scope changed

What to do before the revision

List the clauses the project actually needs, then record every removal. If the list is close to the full set, full conformance is cheaper to defend than a long tailoring table.

Read across

← 4.2 Full conformance 5.2.1 General: the requirements engineering function →

Full register / Revision record

Source for clause 4.5: ISO/IEC/IEEE 29148:2018, Clause 4.5, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.