Goal‑Objective‑Service Diagram in Enterprise Architecture
The Goal‑Objective‑Service diagram explains how business services link to drivers, goals, objectives and measures, providing a visual and matrix‑based view of service contributions to enterprise strategy and performance, while also describing alternative representations and related UML/BPMN and ArchiMate profiles.
The Goal/Objective/Service diagram defines how services contribute to achieving a business vision or strategy by linking each service to its supporting drivers, high‑level goals, detailed objectives, and measurable outcomes.
These connections enable organizations to understand which services impact specific aspects of business performance, and the diagram also supplies qualitative input about what constitutes high performance for a given service.
The diagram clearly shows the relationship between business services and enterprise goals, serving as a useful view for managing system evolution and impact analysis; when combined with a matrix representation, it becomes especially practical for large systems with many services and links, offering an alternative but equivalent model that users can choose based on preference.
Another approach is to create individual diagrams for each business service, illustrating the links between the service and the goals it tracks.
UML/BPMN EAP Profile
Business Service : Represents a service offered by the business, which may be realized by one or more IS services.
Goal : The enterprise’s strategic objective.
Generic Traceability Link : Ensures that the source of a trace is found on the target goal during the definition of the trace.
ArchiMate
Original source: https://www.togaf-modeling.org/models/business-architecture/goal-objective-service-diagrams.html
Article: http://jiagoushi.pro/togaf-modeling-goalobjectiveservice-diagrams
Discussion: Join the Chief Architect Circle on Knowledge Planet, the small account jiagoushi_pro, or QQ group 11107777 for deeper conversation.
Architects Research Society
A daily treasure trove for architects, expanding your view and depth. We share enterprise, business, application, data, technology, and security architecture, discuss frameworks, planning, governance, standards, and implementation, and explore emerging styles such as microservices, event‑driven, micro‑frontend, big data, data warehousing, IoT, and AI architecture.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.