# 3.4.9 Concern, 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 Architecture design concepts · 3.4.9 # Concern A matter of interest, relevance or importance to a stakeholder, or one that has an impact on a stakeholder. Concerns can be technical, organisational, socio political, legal, ethical or regulatory, and new ones can surface while architecture decisions are being taken. - definition - Term - ISO/IEC/IEEE DIS 42024 - Last updated: 2026-10-21 ## What this term settles A concern belongs to a stakeholder, not to a document. The definition also says concerns can emerge during the work, which is a warning against treating the concern register as fixed at kick off. It legitimises reopening the register when a decision creates a new concern. ## What to do in your practice Keep a concern register with the concern, the stakeholder, the type, the decision it affects and the status. Add a column for concerns that emerged after a decision. Review the register at each gate, not only at the start. ## 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 - A concern register with stakeholder, type and status. An auditor asks which concerns were known and how each was addressed. - A record of concerns that emerged during the work. Shows the practice responded to new information rather than defending the plan. - The decision to concern trace. Lets a reviewer test whether the architecture addresses what mattered. - The closure note for each concern. Distinguishes addressed from accepted and from open. Ask your teamWhich concern was raised after a decision and changed the architecture, and where is it recorded? ## Common gaps this page catches - Concerns are collected once at kick off and never updated. - Concerns are recorded without the stakeholder, so ownership is unclear. - Regulatory and ethical concerns are held by compliance outside the architecture record. ## What to prepare before publication Add the emerged after decision column to the register. At the next gate, ask each stakeholder what concern has appeared since the last review. Record the answers and any architecture change they trigger. ## Common questions What does Concern mean in ISO 42024? A matter of interest, relevance or importance to a stakeholder, or one that has an impact on a stakeholder. Concerns can be technical, organisational, socio political, legal, ethical or regulatory, and new ones can surface while architecture decisions are being taken. What evidence should we keep for 3.4.9? A concern register with stakeholder, type and status. A record of concerns that emerged during the work. The decision to concern trace. ## Related units - 3.4.7 - 3.4.8 - 3.3.7 Source. ISO/IEC/IEEE DIS 42024, Clause 3.4.9, 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/concern/