# 4.3 Architecture design and solution design, 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.3 # Architecture design and solution design The subclause addresses the split between architecture design and solution design. It builds on 3.4.2 and 3.4.5: architecture design is the information needed to create, transform or understand an architecture, while solution design is the information needed to implement a solution entity. - concept, not an obligation - Clause area - ISO/IEC/IEEE DIS 42024 - Last updated: 2026-10-21 ## What this unit settles The introduction treats the split as basic: two kinds of design, one strategic and enduring, the other detailed and tactical. It also says the two can run concurrently. That is the clearest public statement of the split in the document. ## What to do in your practice Write the split into the delivery method as two outputs with different readers. Define what each must contain and which decisions belong to each. Where the two run concurrently, name the interface and the decision rights. ## 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 method with two design outputs and their readers. An auditor asks which output a decision belonged to. - A decision rights table for architecture and solution decisions. Shows the split is operable. - A concurrency note for parallel work. Explains how risk was managed. - A sample of decisions classified by level. Proves the split is used. Ask your teamWhich decision in the last delivery was an architecture decision made by a solution team? ## Common gaps this page catches - One design stage produces both outputs and no one owns the split. - Solution teams make architecture decisions because no decision rights exist. - Concurrent work has no interface record. ## What to prepare before publication Add the two outputs to the method and a decision rights table. Classify the last ten decisions. Where a solution team made an architecture decision, record it as a finding and fix the route. ## Common questions What does Architecture design and solution design mean in ISO 42024? The subclause addresses the split between architecture design and solution design. It builds on 3.4.2 and 3.4.5: architecture design is the information needed to create, transform or understand an architecture, while solution design is the information needed to implement a solution entity. What evidence should we keep for 4.3? The method with two design outputs and their readers. A decision rights table for architecture and solution decisions. A concurrency note for parallel work. ## Related units - 3.4.2 - 3.4.5 - 3.4.4 Source. ISO/IEC/IEEE DIS 42024, Clause 4.3. 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/architecture-design-and-solution-design/