According to the TOGAF® Standard, a "concern" is explicitly defined as an interest in a system relevant to one or more of its stakeholders. Concerns are the key drivers for the creation of an architecture, as they represent the interests that need to be addressed. These interests can relate to any aspect of the system, such as performance, security, cost, or usability. The entire process of creating architecture views and viewpoints is centered around identifying and addressing these stakeholder concerns.

A. Requirements: Requirements are specific, quantifiable statements of need that are derived from broader stakeholder concerns, not the interests themselves.

B. Principles: Principles are high-level, guiding rules and constraints for the architecture, which are not the same as the fundamental interests of stakeholders.

D. Architecture views: Views are representations of the architecture created specifically to address and communicate about stakeholder concerns; they are not the concerns themselves.

1. The Open Group. (2022). TOGAF® Standard

10th Edition. Van Haren Publishing.

Part I

Chapter 3

Definitions: Defines "Concern" as "An interest in a system relevant to one or more of its stakeholders."

Part I

Chapter 3

Definitions: Defines "Stakeholder" as "An individual

team

organization

or class thereof

having an interest in

or concerns relative to

a system."

Part III

Section 24.3

Steps in the Stakeholder Management Process: Step 2 is "Identify Stakeholders' Concerns

and Key Issues".

2. ISO/IEC/IEEE. (2011). Systems and software engineering — Architecture description (Standard No. 42010:2011).

Section 3.5: Defines "concern" as an "interest in a system relevant to one or more of its stakeholders". This international standard is a normative reference for the TOGAF Standard.