251
edits
Changes
Jump to navigation
Jump to search
mLine 16:
Line 16: − + − + + + + + + + + − + + + + + + + + +
SSC Artifacts and Diagrams (view source)
Revision as of 15:35, 19 September 2019
, 15:35, 19 September 2019no edit summary
Scope/Constraints: None.
Scope/Constraints: None.
Key Stakeholders:
Key Stakeholders: Enterprise architects, business analysts, strategic planning, benefits realization team.
Purpose/Value: Used to identify and related the key strategic drivers, goals, outcomes of the organization, and the key strategic stakeholders.
Purpose/Value: Used to identify and related the key strategic drivers, goals, outcomes of the organization, and the key strategic stakeholders. Provides links to identify what existing and planned architecture are supporting the enterprise's desired target direction.
===== Business Capability Map =====
===== Business Capability Map =====
ArchiMate Viewpoint: Capability Map
Scope/Constraints: Generally limited to identifying capabilities/sub-capabilities, and their association with enterprise strategic outcomes, goals, drivers.
Key Stakeholders: Senior executives, branches, business managers, enterprise and business architects. Investment prioritization.
Purpose/Value: A primary communication mechanism with SSC executives on the state of the architecture, activities, and progress towards desired target direction. Helps ensure alignment between current/target activities and the strategic direction/capabilities of the organization. Investment prioritization.
===== Strategic Business Architecture =====
===== Strategic Business Architecture =====
Segment/Service Overview Diagram
====== Segment/Service Overview Diagram ======
ArchiMate Viewpoint: Business Process Cooperation Viewpoint
Scope/Constraints: Uses only business functions, and business functions with categories "SSC Segment", "SSC Client-facing Service", and "SSC Supporting Service".
Key Stakeholders: Enterprise architects/Enterprise Architecture management/executives.
Purpose/Value: Enables EA to organize, prioritize and assign architecture work/activities. In particular, it identifies the segments that will be used to organize EA work, and distributes the key services/functions among them. It does not show detailed information about roles, processes, information, technologies, applications involved in each segment. Segment diagrams are produced for each segment that provides a more complete definition of what belongs in each segment.
Segment Diagram
Segment Diagram
