# 3.2.7 Reference architecture, 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 / Glossary Architecting concepts · 3.2.7 # Reference architecture An architecture that gives a standard or shared way of handling a problem, a circumstance or an opening in a field, a domain of activity or an area of concern. A reference architecture description may contain or point to reference models. - definition - Term - ISO/IEC/IEEE DIS 42024 - Last updated: 2026-10-21 ## What this term settles A reference architecture is still an architecture, so it has fundamental ideas and essential qualities. It is not a template and not a product. The definition matters for reuse: a firm that adopts a reference architecture is adopting a set of decisions, and it should know which ones it is adopting and which it is changing. ## What to do in your practice For each reference architecture the firm reuses, record the source, the version, the field it was written for and the decisions it carries. Then record where the firm departed from it and why. A reuse register turns a vague claim of alignment into a set of traceable choices. ## Who it binds The role that owns the practice area the term governs. A definition binds nobody on its own; it binds the reader who adopts the term in a method, a description or a contract. ## Evidence an auditor or regulator asks for - The reference architecture register with source, version and owner. An auditor asks where a reused architecture came from and whether it is current. - A delta record of local departures from the reference. Shows the firm understood the choices it changed rather than copying without reading. - The reference models the reference architecture relies on. Makes the dependency visible when the reference model changes. - A review date and the last review note. Shows the reference is maintained against the field it came from. Ask your teamWhich decisions in this reference architecture has the firm changed, and who accepted the consequence? ## Common gaps this page catches - Reference architectures are copied into projects with no record of source or version. - Local departures are invisible, so the same reference is claimed by teams that built different things. - No one owns the reference and no one reviews it. ## What to prepare before publication Pick the reference architecture used by the largest programme. Reconstruct its source, version and the departures made in the last two years. That reconstruction is the first row of the reuse register. ## Common questions What does Reference architecture mean in ISO 42024? An architecture that gives a standard or shared way of handling a problem, a circumstance or an opening in a field, a domain of activity or an area of concern. A reference architecture description may contain or point to reference models. What evidence should we keep for 3.2.7? The reference architecture register with source, version and owner. A delta record of local departures from the reference. The reference models the reference architecture relies on. ## Related units - 3.2.1 - 3.5.7 - 3.2.6 Source. ISO/IEC/IEEE DIS 42024, Clause 3.2.7, Terms and definitions. 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: definition. The definition is in the public preview. This page states it in our own words and does not reproduce the text. Last updated: 2026-10-21 · Markdown version · Check your practice Source: https://iso-42024-revision-checker.theartofservice.com/glossary/reference-architecture/