251
edits
Changes
Jump to navigation
Jump to search
Line 11:
Line 11: − Based on ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946175 Motivation Viewpoint]+ Line 17:
Line 17: − 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.+ + + − − Based on ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946178 Capability Map] Line 28:
Line 28: − 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.+ − Based on ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946160 Business Process Cooperation Viewpoint]+ − + − 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. + Line 47:
Line 47: − Based on ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946170 Layered Viewpoint]+ Line 53:
Line 53: − 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?+ − Based on ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946170 Layered Viewpoint]+ Line 64:
Line 64: − 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.+ − +
SSC Artifacts and Diagrams (view source)
Revision as of 09:03, 24 September 2020
, 09:03, 24 September 2020no edit summary
Prepared by: Benefits Management.
Prepared by: Benefits Management.
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.
Scope/Constraints: None beyond the constraints of the default ArchiMate 3.0 recommended viewpoint.
Scope/Constraints: None beyond the constraints of the default ArchiMate 3.0 recommended viewpoint.
Key Stakeholders: Enterprise architects, business analysts, strategic planning, benefits realization, SSC executives.
Key Stakeholders: Enterprise architects, business analysts, strategic planning, benefits realization, SSC executives.
Based on ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946175 Motivation Viewpoint]
==== Business Capability Map ====
==== Business Capability Map ====
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.
Prepared by: Enterprise Architecture - Business Capability Lead
Prepared by: Enterprise Architecture - Business Capability Lead
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.
Key Stakeholders: Senior executives, branches, business managers, enterprise and business architects. Investment prioritization.
Key Stakeholders: Senior executives, branches, business managers, enterprise and business architects. Investment prioritization.
Based on ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946178 Capability Map]
==== Segment Diagram ====
==== Segment Diagram ====
Prepared by: Enterprise Architect - Segment Architect/Lead
Prepared by: Enterprise Architect - Segment Architect/Lead
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.
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 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.
Key Stakeholders: Enterprise architects/Enterprise Architecture management/executives.
Key Stakeholders: Enterprise architects/Enterprise Architecture management/executives.
Based on ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946160 Business Process Cooperation Viewpoint]
==== Strategic Service Diagram ====
==== Strategic Service Diagram ====
Prepared by: Enterprise Architect (in collaboration with Service Leads/Architects)
Prepared by: Enterprise Architect (in collaboration with Service Leads/Architects)
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?
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.
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.
Key Stakeholders: Enterprise architects/Enterprise Architecture management/executives, Service architects.
Key Stakeholders: Enterprise architects/Enterprise Architecture management/executives, Service architects.
Based on ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946170 Layered Viewpoint]
==== Architecture Roadmap Diagram ====
==== Architecture Roadmap Diagram ====
Prepared by: Enterprise Architect (in collaboration with Service Leads/Architects)
Prepared by: Enterprise Architect (in collaboration with Service Leads/Architects)
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.
Scope/constraints: Uses Implementation and Migration elements, and Motivation elements (goal/outcome).
Scope/constraints: Uses Implementation and Migration elements, and Motivation elements (goal/outcome).
Key Stakeholders: Enterprise Architects, Service Architects, Solution Architects, Service leads/teams.
Key Stakeholders: Enterprise Architects, Service Architects, Solution Architects, Service leads/teams.
[https://gcdocs.gc.ca/ssc-spc/llisapi.dll?func=ll&objaction=overview&objid=79127247 Architecture Roadmap Demonstration Video]
[https://gcdocs.gc.ca/ssc-spc/llisapi.dll?func=ll&objaction=overview&objid=79127247 Architecture Roadmap Demonstration Video]
Based on ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946170 Layered Viewpoint]
=== Solution (including Service) Architecture ===
=== Solution (including Service) Architecture ===
