Goal/Objective/Service Diagram in Enterprise Architecture Modeling
The Goal/Objective/Service diagram defines how business services contribute to strategic goals, links services with drivers, objectives, and measures, and can be visualized alone or with a matrix to aid impact analysis and system evolution in enterprise architecture.
UML/BPMN EAP Profile
Goal (Goal) / Objective (Objective) / Service diagram defines how services contribute to achieving business visions or strategies.
The diagram links services with their drivers, goals, objectives, and measures, allowing enterprises to understand which services impact specific performance aspects and provides qualitative input on high performance of a service.
It clearly shows the relationship between business services and corporate goals, useful for managing system evolution and impact analysis; combining it with a matrix improves readability for large systems, and users may choose either representation.
Another approach is to draw separate diagrams for each business service, showing its connections to tracked goals.
Archimate
Business Service : Represents a service offered by the business, which can be realized by one or more IS services.
Goal : The enterprise’s objectives.
General Traceability Link : Ensures that the source of a trace is found on the target goal during definition.
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.