Changes

This portion of enterprise architecture contains artifacts that define the scope of the enterprise, break it down into useful portions (segments), describe the strategic current/target states, drivers and motivations.

This portion of enterprise architecture contains artifacts that define the scope of the enterprise, break it down into useful portions (segments), describe the strategic current/target states, drivers and motivations.

===== Strategic Motivation Diagram =====

==== Strategic Motivation Diagram ====

ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946175 Motivation Viewpoint]

Based on ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946175 Motivation Viewpoint]

Scope/Constraints:  None.

Scope/Constraints:  None.

Key Stakeholders: Enterprise architects, business analysts, strategic planning, benefits realization team.

Key Stakeholders: Enterprise architects, business analysts, strategic planning, benefits realization, SSC executives.

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.

Purpose/Value:  Used to identify and related the 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.  All solution architectures should link (directly or indirectly) to a strategic goal or outcome.

===== Business Capability Map =====

==== Business Capability Map ====

ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946178 Capability Map]

Based on ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946178 Capability Map]

Scope/Constraints:  Generally limited to identifying capabilities/sub-capabilities, and their association with enterprise strategic outcomes, goals, drivers.

Scope/Constraints:  Generally limited to identifying capabilities/sub-capabilities, and their association with enterprise strategic outcomes, goals, drivers.

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.

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 Architecture ====

==== Segment Diagram ====

Scope/Constraints:  Uses only business roles, business actors, and business functions with categories "SSC Segment", "SSC Client-facing Service", and "SSC Supporting Service".  It may begin to associate key high-level roles, information, applications - but generally, it leaves details of architecture to dedicated lower-level diagrams.  One diagram per defined segment.   

 

Scope/Constraints:  Uses only business functions, and business functions with categories "SSC Segment", "SSC Client-facing Service", and "SSC Supporting Service".  It does not show detailed information about roles, processes, information, technologies, applications involved in each segment.  One diagram shows all segments, and key high-level associated functions. 

 

 

 

 

Scope/Constraints:  Uses only business functions, and business functions with categories "SSC Segment", "SSC Client-facing Service", and "SSC Supporting Service".  It may begin to associate key high-level roles, information, applications - but generally, it leaves details of architecture to dedicated lower-level diagrams.  One diagram per defined segment.   

Key Stakeholders:  Enterprise architects/Enterprise Architecture management/executives.

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.   

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.  Every identified SSC service should belong to a segment.   

===== Strategic Service Diagram (formerly Conceptual Service Diagram) =====

==== Strategic Service Diagram ====

[[File:Service Conceptual Diagram - Example Wi-Fi.png|thumb|

[[File:Service Conceptual Diagram - Example Wi-Fi.png|thumb|

Strategic Service Diagram:  GC Wi-Fi Service

Strategic Service Diagram:  GC Wi-Fi Service

]]

]]

ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946170 Layered Viewpoint]

Based on ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946170 Layered Viewpoint]

 

 

 

Scope/Constraints:  This diagram defines, at a high level, an SSC service. It links the SSC Service to Business Capabilities (1 or more), and to other key business functions/services, and to the key foundational/supporting technologies. The diagram may expose some of the key sub-functions/processes that are performed in that SSC service (down 1 level of conception). Detailed business, application, information and technology diagrams for a particular service are to be detailed in other (solution-level) diagrams.

ArchiMate Viewpoint:  Capability Planning View  (Custom:  Base on Capability Planning view at: https://www.hosiaisluoma.fi/blog/archimate-examples)  

Scope/Constraints: Link any Business Function or Business Process to a capability.  

Key Stakeholders:  Enterprise architects/Enterprise Architecture management/executives, Service architects.

Key Stakeholders:  Enterprise architects, segment architects, strategic planning.  

Purpose/Value:  Provides a conceptual view of SSC Services, key inter-service linkages, strategic linkages, and links to enabling technologies. Answers the questions:  1) What services/functions need which services to operate?, 2) What technologies are required by a particular SSC Service?

Purpose/Value:  To link between strategy and enterprise architecture (core elements). Used for mapping key core elements of architecture to realized capabilities.  In particular, those supporting functions/services and related applications/technology in support of particular capabilities.  

Based on ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946170 Layered Viewpoint]

Key Stakeholders:  SSC executives, service mangement, service inventory, enterprise architects, service leads, service teams, service architects, solution architects.

Key Stakeholders:  Enterprise Architects, Service Architects, Solution Architects, Service leads/teams.

Purpose/Value:  Provides a list of the SSC functions designated as "SSC Services" including with key attributes used for service management and service inventory management.

Purpose/Value:  Defines/describes the different architectures for a particular service in defined states (n-2, n-1, n, n+1, n+2) and plateaus (current, target, target+), and what work packages (projects) will satisfy which identified architecture gaps.

==== Reference Library ====

==== Reference Library ====