A Viewpoint specifies the stakeholder concerns that a View is intended to address and the conventions governing how that View is constructed, interpreted, evaluated, and used.
A Viewpoint may identify:
A Viewpoint does not contain the representation of a particular System. It establishes what a conforming View must address and how it selects and presents the relevant information. A View applies the Viewpoint to a particular System, Model, Domain, or subject of interest.
A single System may have multiple Viewpoints because different stakeholders have different concerns. An operational Viewpoint may address missions, Actors, activities, and information exchanges. A security Viewpoint may address threats, trust boundaries, controls, and authorization. A deployment Viewpoint may address Nodes, execution environments, dependencies, and allocations.
In Systems Modeling Language Version 2 (SysML v2), a Viewpoint Definition is a kind of Requirement Definition that specifies one or more stakeholder concerns to be satisfied by creating a View of a Model. A View Definition specifies how the View artifact is constructed, what Model content it presents, and how it renders that content.
specification of stakeholder concerns and the conventions governing the construction, interpretation, evaluation, and use of Views intended to address those concerns
Aligned with ISO/IEC/IEEE 42010 architecture-description concepts and the OMG Systems Modeling Language Version 2.0 Language Specification treatment of Viewpoint Definitions, stakeholder concerns, View Definitions, and View artifacts.
A Viewpoint is distinct from a View. A Viewpoint establishes the concerns, rules, and conventions. A View is the resulting representation of a particular subject according to that Viewpoint.
A Viewpoint is also distinct from the personal opinion or physical location of an observer. In architecture and Systems modeling, a Viewpoint is a governed specification for addressing identified stakeholder concerns.
A security-assurance Viewpoint identifies security officers, system owners, and authorization authorities as stakeholders. It requires a conforming View to present trust boundaries, information flows, security controls, threats, residual risks, and supporting Evidence using specified Model elements and rendering conventions.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.