# A.2 Architecture expressed as a set of 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 / Annex A Annex A, Notes on terms and concepts · A.2 # Architecture expressed as a set of models The subclause is the second note in Annex A, on an architecture expressed as a set of models. It builds on model (3.5.5), metamodel (3.5.6) and architecture description (3.5.1). - annex section, status not stated in the public preview - Annex section - ISO/IEC/IEEE DIS 42024 - Last updated: 2026-10-21 ## What this unit settles The note addresses the common situation in which the architecture is available only as a collection of models. That is not the same as an architecture description, and the note is the place where the document connects the two. A firm that treats a model set as the description should expect an audit finding about readability and purpose. ## What to do in your practice For each model set, ask what description it supports and who reads it. If the answer is a tool team only, the set is an engineering asset, not an architecture description. Build the description layer explicitly. Ask the modelling team to produce a one page description for a stakeholder who will never open the tool. The exercise exposes the difference between a model that is correct and a description that is usable, and it usually takes less time than the team expects. ## Who it binds The architecture practice, as a note. The public preview does not state the annex status, so this page does not claim one. ## Evidence an auditor or regulator asks for - A model set inventory with the description each supports. An auditor asks what the models are for. - The reader and purpose per description. Shows the description is designed for use. - The metamodel and notation record. Shows the models are interpretable. - A sample description produced from the models. Proves the layer exists. Ask your teamCan a stakeholder read this architecture without opening the modelling tool? ## Common gaps this page catches - The model repository is presented as the architecture description. - No description layer exists. - The metamodel is undocumented. ## What to prepare before publication Choose one model set and produce a description layer for it. Name the reader. The work is usually a day and it changes the audit answer completely. ## Common questions What does Architecture expressed as a set of models mean in ISO 42024? The subclause is the second note in Annex A, on an architecture expressed as a set of models. It builds on model (3.5.5), metamodel (3.5.6) and architecture description (3.5.1). What evidence should we keep for A.2? A model set inventory with the description each supports. The reader and purpose per description. The metamodel and notation record. ## Related units - 3.5.1 - 3.5.5 - 3.5.6 Source. ISO/IEC/IEEE DIS 42024, Annex A.2, published contents. 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: annex section, status not stated in the public preview. The annex title and subclause title are 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/annex-a/architecture-expressed-as-a-set-of-models/