# 4.9 Reference architectures and reference models, ISO 42024 ## Published contents Contents1 Scope2 Normative references3 Terms and definitions4 Architecture concepts4.1 Overview4.2 Architecture and architecting4.3 Architecture design and solution design4.4 Architecture definition and communication4.5 Stakeholder concerns and architectural aspects4.6 Architecture viewpoints and architecture views4.7 Architecture frameworks and architecture description languages4.8 Architecture descriptions and architecture models4.9 Reference architectures and reference models4.10 Life cycle and life history4.11 Architecting precepts5 Architecting principles5.1 Introduction to the principles5.2 Principles about the purpose of an architecture5.3 Principles about the focus of an architecture5.4 Principles about architecting outcomesTerms 3.2 Architecting concepts 3.2.1 Architecture3.2.2 Architecture feature3.2.3 Architecting3.2.4 Architecting principle3.2.5 Architecture principle3.2.6 Architecture framework3.2.7 Reference architecture3.3 Entity related concepts 3.3.1 Entity of interest3.3.2 Solution entity3.3.3 Environment3.3.4 Context3.3.5 Enterprise3.3.6 System3.3.7 Aspect3.3.8 Dimension3.4 Architecture design concepts 3.4.1 Design (noun)3.4.2 Architecture design3.4.3 Architecture information package3.4.4 Engineering effort3.4.5 Solution design3.4.6 Solution information package3.4.7 Stakeholder3.4.8 Stakeholder perspective3.4.9 Concern3.5 Architecture description concepts 3.5.1 Architecture description3.5.2 Solution description3.5.3 Architecture view3.5.4 Architecture viewpoint3.5.5 Model3.5.6 Metamodel3.5.7 Reference model3.6 Entity life cycle concepts 3.6.1 Life cycle3.6.2 Life cycle phase3.6.3 Life cycle stage3.6.4 Life historyAnnexes A.1 Architecture design and solution related entitiesA.2 Architecture expressed as a set of modelsA.3 Life cycle and life history conceptsA.4 Enterprise and system conceptsA.5 Duality of architectural decomposition and architectural synthesisB.1 BackgroundB.2 Aligning architecture in designB.3 Duality of architectureB.4 Pursuit of opportunities Home / Concepts Architecture concepts · 4.9 # Reference architectures and reference models The subclause addresses reference architectures and reference models. It builds on reference architecture (3.2.7) and reference model (3.5.7). A reference architecture is an architecture that offers a standard or common approach in a field; a reference model models a recurring problem. - concept, not an obligation - Clause area - ISO/IEC/IEEE DIS 42024 - Last updated: 2026-10-21 ## What this unit settles The pair gives a firm a disciplined way to reuse. A reference architecture carries decisions; a reference model carries a common approach to a recurring problem. Reuse without knowing which one is being adopted is how a firm ends up with the label but not the decisions. ## What to do in your practice Keep a reuse register: the reference, its type, the source, the version, the decisions it carries, the local departures and the owner. Trace each local architecture to the reference it reuses. Review the register when the source publishes a new version. When a source publishes a new version, review the register before any project does. The review asks which local architectures relied on the changed decisions and which departures are now obsolete. Without that step, a firm can be on two versions of the same reference and call both current. ## Who it binds The organisation and the architecture practice. This unit is not a shall requirement; the claim level states what it is. ## Evidence an auditor or regulator asks for - The reuse register with type and decisions. An auditor asks what was reused and what was changed. - The local departure record with approval. Shows the firm understood the decisions it changed. - The trace from local architecture to reference. Proves the reuse claim. - The version review note. Shows the firm tracks the source. Ask your teamWhich reference architecture does this firm claim to follow but has departed from without recording it? ## Common gaps this page catches - Reuse is claimed in slides and not traceable in the architecture. - Reference models and reference architectures are used interchangeably. - No one reviews the source version. ## What to prepare before publication Build the reuse register for the top five references. For each, record the type, source, version, decisions and departures. The untraceable claims are the first to fix. ## Common questions What does Reference architectures and reference models mean in ISO 42024? The subclause addresses reference architectures and reference models. It builds on reference architecture (3.2.7) and reference model (3.5.7). A reference architecture is an architecture that offers a standard or common approach in a field; a reference model models a recurring problem. What evidence should we keep for 4.9? The reuse register with type and decisions. The local departure record with approval. The trace from local architecture to reference. ## Related units - 3.2.7 - 3.5.7 - 3.5.1 Source. ISO/IEC/IEEE DIS 42024, Clause 4.9. Open the official record. Retrieved 21 October 2026. https://www.iso.org/obp/ui/en/#iso:std:iso-iec-ieee:42024:dis:ed-1:v1:en ISO catalogue record 87510, the status, stage and page count. Claim level: concept, not an obligation. The subclause title is in the public preview. The body text is not public. Last updated: 2026-10-21 · Markdown version · Check your practice Source: https://iso-42024-revision-checker.theartofservice.com/clauses/reference-architectures-and-reference-models/