# 4.6 Architecture viewpoints and architecture views, ISO 4202 ## 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.6 # Architecture viewpoints and architecture views The subclause addresses the relationship between viewpoints and views. It builds on viewpoint (3.5.4) and view (3.5.3): the viewpoint is the convention, the view is the expression that addresses concerns and reflects aspects. - concept, not an obligation - Clause area - ISO/IEC/IEEE DIS 42024 - Last updated: 2026-10-21 ## What this unit settles The pair is the mechanism by which concerns reach the description. The document treats a viewpoint as associated with stakeholder perspectives, framing their concerns and providing the conventions for creating views. That makes the viewpoint register the link between the stakeholder work and the modelling work. ## What to do in your practice Write the viewpoint register with the perspective, the concerns, the aspects and the produced views. Audit the views against it and retire any view with no viewpoint. Test a viewpoint by asking a new architect to produce a view from the written convention alone. When a new stakeholder appears, add the perspective and the concerns first, then decide whether an existing viewpoint can frame them. Creating a new view before the concern is written is how view libraries grow without becoming more useful. The register should be read before the modelling tool is opened. ## 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 viewpoint register and the view library. An auditor asks whether views follow stated conventions. - The trace from perspective to concern to viewpoint to view. Shows the chain is complete. - The retired views record. Shows the library is curated. - The reproducibility test result. Proves the convention is written well enough to use. Ask your teamWhich view in the library has no viewpoint, and who would notice if it were deleted? ## Common gaps this page catches - Views exist without viewpoints, so the conventions live in individual heads. - The view library is a tool dump with no curation. - No trace connects a stakeholder perspective to a view. ## What to prepare before publication Write three viewpoints and test them. Retire the views without a viewpoint. Record the trace for the top five views. The register is the artefact that makes the practice repeatable. ## Common questions What does Architecture viewpoints and architecture views mean in ISO 42024? The subclause addresses the relationship between viewpoints and views. It builds on viewpoint (3.5.4) and view (3.5.3): the viewpoint is the convention, the view is the expression that addresses concerns and reflects aspects. What evidence should we keep for 4.6? The viewpoint register and the view library. The trace from perspective to concern to viewpoint to view. The retired views record. ## Related units - 3.5.3 - 3.5.4 - 3.4.8 - 4.5 Source. ISO/IEC/IEEE DIS 42024, Clause 4.6. 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-viewpoints-and-views/