wiki

Changes

SSC Artifacts and Diagrams (view source)

Revision as of 16:11, 30 October 2020

2,332 bytes added ,  16:11, 30 October 2020
→‎Conceptual Diagram
Line 5: Line 5:  
[[File:EA_Models_Structure.png|frameless|944x944px]]
 
[[File:EA_Models_Structure.png|frameless|944x944px]]
   −
=== Strategic Architecture ===
+
== Enterprise Architecture ==
 +
Enterprise Architecture (EA) includes and is broken down into Strategic and Solution Architecture. 
 +
 
 +
[https://gcdocs.gc.ca/ssc-spc/llisapi.dll/Open/83409305 Video overview of EA, Strategic and Solution architecture artifacts] 
 +
 
 +
== Strategic Architecture ==
 
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 ===
 
Prepared by:  Benefits Management.
 
Prepared by:  Benefits Management.
   Line 16: Line 21:     
Key Stakeholders: Enterprise architects, business analysts, strategic planning, benefits realization, SSC executives.
 
Key Stakeholders: Enterprise architects, business analysts, strategic planning, benefits realization, SSC executives.
 +
 +
[http://qualfrm-0006075.dev.global.gc.ca/SSC_Governed_Architecture/?oid=9fa6c389-96ed-4f4e-82fd-f1750a22f0d6 Strategic Motivation Diagram Example] (QW login required)
    
Based on 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]
   −
==== 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.
 
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.
   Line 27: Line 34:     
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.
 +
 +
[http://qualfrm-0006075.dev.global.gc.ca/SSC_Governed_Architecture/?oid=6d26f35d-1e3b-46b0-ba59-849f065d4dbf Business Capability Map Example] (QW login required)
    
Based on 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]
   −
==== Segment Diagram ====
+
=== Segment Diagram ===
 
Prepared by: Enterprise Architect - Segment Architect/Lead
 
Prepared by: Enterprise Architect - Segment Architect/Lead
   Line 38: Line 47:     
Key Stakeholders:  Enterprise architects/Enterprise Architecture management/executives.
 
Key Stakeholders:  Enterprise architects/Enterprise Architecture management/executives.
 +
 +
[http://qualfrm-0006075.dev.global.gc.ca/SSC_Governed_Architecture/?oid=c8410fdd-62de-45b6-9959-2361c9f1aada Segment Diagram Guidance] (QW login required)
 +
 +
[http://qualfrm-0006075.dev.global.gc.ca/SSC_Governed_Architecture/?oid=78d3b7af-8667-41c4-89e2-d58ffe1595cc Segment Diagram Example] (QW login required)
    
Based on ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946160 Business Process Cooperation Viewpoint]   
 
Based on ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946160 Business Process Cooperation Viewpoint]   
   −
==== Strategic 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
Line 52: Line 65:     
Key Stakeholders:  Enterprise architects/Enterprise Architecture management/executives, Service architects.
 
Key Stakeholders:  Enterprise architects/Enterprise Architecture management/executives, Service architects.
 +
 +
[http://qualfrm-0006075.dev.global.gc.ca/SSC_Governed_Architecture/?oid=7969bebb-476a-4bc8-b649-cb6869e658e3 Strategic Service Diagram Guidance] (QW login required)
 +
 +
[http://qualfrm-0006075.dev.global.gc.ca/SSC_Governed_Architecture/?oid=1864994b-09bd-42e7-a17a-67fd15cf3e55 Strategic Service Diagram Example] (QW login required)
    
Based on 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]
   −
==== 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)
   Line 68: Line 85:  
Based on 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]
   −
=== Solution (including Service) Architecture ===
+
== Solution (including Service) Architecture ==
 
These diagrams are for service or solution architectures for initiatives.  The solution architecture artifacts are usually captured in a Service and Solution Architecture Description deliverable (package).  These solution architectures are reviewed with enterprise architecture through a governance processes (architecture assurance) to help ensure alignment with the enterprise architecture.
 
These diagrams are for service or solution architectures for initiatives.  The solution architecture artifacts are usually captured in a Service and Solution Architecture Description deliverable (package).  These solution architectures are reviewed with enterprise architecture through a governance processes (architecture assurance) to help ensure alignment with the enterprise architecture.
   −
==== Conceptual Solution Architecture ====
+
=== Conceptual Solution Architecture ===
 +
The conceptual solution architecture is a subset of a complete solution architecture.  It identifies the requirements, benefits and measures of success for a project, strategic goals/outcomes and business capabilities to be realized in the solution/initiative.  Further, it identifies the key business functions (SSC services) that will be used, created, impacted by the effort, and begins to outline the scope of the initiative. 
   −
===== Requirements Diagram =====
+
==== Requirements Diagram ====
 
Prepared by:  Solution architect, service architect.
 
Prepared by:  Solution architect, service architect.
   Line 82: Line 100:  
Based on 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]
   −
===== Benefits Dependency Map =====
+
==== Benefits Dependency Map ====
 
Prepared by: Benefits management (in cooperation with the project/service team and/or service/solution architect)
 
Prepared by: Benefits management (in cooperation with the project/service team and/or service/solution architect)
   Line 94: Line 112:     
Based on 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]   
−
===== Context Diagram =====
+
==== Context Diagram ====
    
Prepared by: Service/Solution architect
 
Prepared by: Service/Solution architect
Line 102: Line 120:  
Key Stakeholders:  Enterprise Architect, Governance Bodies (EART, AC, SARB).
 
Key Stakeholders:  Enterprise Architect, Governance Bodies (EART, AC, SARB).
   −
===== Conceptual Diagram =====
+
[https://gcdocs.gc.ca/ssc-spc/llisapi.dll?func=ll&objaction=overview&objid=83412263 Context Diagram guidance and example video]
 +
 
 +
==== Conceptual Diagram ====
 
Prepared by:  Service/Solution architect
 
Prepared by:  Service/Solution architect
   Line 110: Line 130:     
Key Stakeholders:  Governance bodies (particularly AC and ESSARB), project teams/leads/managers, executives, enterprise architects, service architects, solution architects.   
 
Key Stakeholders:  Governance bodies (particularly AC and ESSARB), project teams/leads/managers, executives, enterprise architects, service architects, solution architects.   
 +
 +
[https://gcdocs.gc.ca/ssc-spc/llisapi.dll?func=ll&objaction=overview&objid=83414397 Conceptual Diagram guidance and example video]
    
ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946170 Layered Viewpoint]       
 
ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946170 Layered Viewpoint]       
   −
==== Logical (and sometimes physical) Architecture ====
+
=== Logical (and sometimes physical) Architecture ===
 +
The logical solution architecture provides the details of the business, information/data, application and technology architecture (including security and privacy) for the solution - in as much detail as is required to move to design, implementation and operations.
   −
===== Logical Business Diagram  (mandatory) =====
+
==== Logical Business Diagram  (mandatory) ====
 
Prepared by:  Service/Solution architect
 
Prepared by:  Service/Solution architect
   Line 126: Line 149:  
ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946160 Business Process Cooperation Viewpoint]   
 
ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946160 Business Process Cooperation Viewpoint]   
   −
===== Logical Application Diagram =====
+
==== Logical Application Diagram ====
 
Prepared by:  Service/Solution architect
 
Prepared by:  Service/Solution architect
   Line 137: Line 160:  
ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946162 Application Cooperation Viewpoint]
 
ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946162 Application Cooperation Viewpoint]
   −
===== Logical Technology (Usage) Diagram =====
+
==== Logical Technology (Usage) Diagram ====
 
Prepared by:  Service/Solution architect
 
Prepared by:  Service/Solution architect
   Line 148: Line 171:  
ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946166 Technology Usage Viewpoint]   
 
ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946166 Technology Usage Viewpoint]   
   −
===== Logical Technology Diagram =====
+
==== Logical Technology Diagram ====
 
Prepared by:  Service/Solution architect
 
Prepared by:  Service/Solution architect
   Line 159: Line 182:  
ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946165 Technology Viewpoint]
 
ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946165 Technology Viewpoint]
   −
-----
+
== Reference Library ==
 +
The reference library contains a number of catalogues managing objects to be used across all levels of architecture.  It particularly houses links to objects representing IT Standards and reference architectures (patterns).
   −
=== Reference Library ===
+
A full list of the catalogues can be found in Qualiware, under the CatalogueDiagram:SSC template, and a summary of other key catalogues can be found [[SSC Architecture Catalogs|here]].
−
The reference library contains a number of catalogues managing objects to be used across all levels of architecture.  It particularly houses links to objects representing IT Standards and reference architectures (patterns). r
      
==== Reference Architecture Catalog ====
 
==== Reference Architecture Catalog ====
Retrieved from "https://wiki.gccollab.ca/Special:MobileDiff/32334...33896"