Changes

Jump to navigation Jump to search
Updated diagram "prepared by" statements.
Line 9: Line 9:     
==== Strategic Motivation Diagram ====
 
==== Strategic Motivation Diagram ====
 +
Prepared by:  Benefits Management.
 +
 
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]
   −
Scope/Constraints:  None.
+
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.
Line 18: Line 20:     
==== Business Capability Map ====
 
==== Business Capability Map ====
 +
Prepared by: Enterprise Architecture - Business Capability Lead
 +
 
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]
   Line 27: Line 31:     
==== Segment Diagram ====
 
==== Segment Diagram ====
 +
Prepared by: Enterprise Architect - Segment Architect/Lead
 +
 
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]
   Line 39: Line 45:  
Strategic Service Diagram:  GC Wi-Fi Service
 
Strategic Service Diagram:  GC Wi-Fi Service
 
]]
 
]]
 +
Prepared by:  Enterprise Architect (in collaboration with Service Leads/Architects)
 +
 
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]
   Line 48: Line 56:     
==== Service Roadmap Diagram ====
 
==== Service Roadmap Diagram ====
 +
Prepared by:  Enterprise Architect (in collaboration with Service Leads/Architects)
 +
 
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]
   Line 62: Line 72:     
===== Requirements Diagram =====
 
===== Requirements Diagram =====
 +
Prepared by:  Solution architect, service architect.
 +
 
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]
    
Key Stakeholders:  Project managers, project teams, business analyst, business architects, service architects, solution architects, engineers.
 
Key Stakeholders:  Project managers, project teams, business analyst, business architects, service architects, solution architects, engineers.
  −
Prepared by:  Solution architect, service architect.
      
Purpose/Value:  List and definitions of the requirements for a project/initiative, as well as any related/influencing standards, principles, policies and/or reference architectures.
 
Purpose/Value:  List and definitions of the requirements for a project/initiative, as well as any related/influencing standards, principles, policies and/or reference architectures.
    
===== Benefits Dependency Map =====
 
===== Benefits Dependency Map =====
 +
Prepared by: Benefits management (in cooperation with the project/service team and/or service/solution architect)
 +
 
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]
   Line 76: Line 88:     
Key Stakeholders:  Project manager/lead, project team, business analyst, benefits realization team, governance bodies, management, executives.   
 
Key Stakeholders:  Project manager/lead, project team, business analyst, benefits realization team, governance bodies, management, executives.   
  −
Prepared by: Benefits management in cooperation with the project/service team and/or service/solution architect. 
      
Purpose/Value:  Identify the benefits of a projects/initiative, identifying key performance metrics (KPI's) that will be used to measure success of the effort.  Helps ensure alignment with enterprise outcomes, identify and link requirements to tactical and strategic outcomes.   
 
Purpose/Value:  Identify the benefits of a projects/initiative, identifying key performance metrics (KPI's) that will be used to measure success of the effort.  Helps ensure alignment with enterprise outcomes, identify and link requirements to tactical and strategic outcomes.   
    
===== Context Diagram =====
 
===== Context Diagram =====
 +
 +
Prepared by: Service/Solution architect
    
Based on ArchiMate Viewpoint:
 
Based on ArchiMate Viewpoint:
    
Key Stakeholders:  Enterprise Architect, Governance Bodies (EART, AC, SARB).
 
Key Stakeholders:  Enterprise Architect, Governance Bodies (EART, AC, SARB).
  −
Prepared by:  Service/Solution architect
      
Purpose/Value:  Identifies the services used and/or modified/created by the initiative.  Identifies and links the initiative to a business capability to be fully or partly realized by the initiative.
 
Purpose/Value:  Identifies the services used and/or modified/created by the initiative.  Identifies and links the initiative to a business capability to be fully or partly realized by the initiative.
    
===== Conceptual Diagram =====
 
===== Conceptual Diagram =====
 +
Prepared by:  Service/Solution architect
 +
 
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]  
   Line 103: Line 115:     
===== Logical Business Diagram  (mandatory) =====
 
===== Logical Business Diagram  (mandatory) =====
 +
Prepared by:  Service/Solution architect
 +
 
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]
   Line 112: Line 126:     
===== Logical Application Diagram (optional) =====
 
===== Logical Application Diagram (optional) =====
 +
Prepared by:  Service/Solution architect
 +
 
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]
   Line 120: Line 136:  
Purpose/Value:  Optional.  Used if more details on application or inter/intra-application are required.  Focus on application development/components specifically.
 
Purpose/Value:  Optional.  Used if more details on application or inter/intra-application are required.  Focus on application development/components specifically.
   −
===== Logical Technology Usage Diagram =====
+
===== Logical Technology (Usage) Diagram =====
 +
Prepared by:  Service/Solution architect
 +
 
 
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]
   Line 130: Line 148:     
===== Logical Technology Diagram =====
 
===== Logical Technology Diagram =====
 +
Prepared by:  Service/Solution architect
 +
 
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]
   Line 141: Line 161:     
==== Reference Architecture Catalog ====
 
==== Reference Architecture Catalog ====
 +
 +
Prepared/maintained by: Enterprise Architecture
    
Key Stakeholders:  Enterprise architects, service architects, solution architects, engineers/implementers.
 
Key Stakeholders:  Enterprise architects, service architects, solution architects, engineers/implementers.
Line 146: Line 168:  
Purpose/Value:  Provides a list of the reference architecture documents available, informing architects of the standard patterns and considerations for preparing architecture in particular defined circumstances.
 
Purpose/Value:  Provides a list of the reference architecture documents available, informing architects of the standard patterns and considerations for preparing architecture in particular defined circumstances.
   −
==== Reference Architecture Diagram/Catalog ====
+
==== Reference Architecture Diagram ====
 +
Prepared by:  Enterprise architect, solution/service architect, subject matter experts.
 +
 
 
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]
   Line 156: Line 180:     
==== IT Standard Catalog ====
 
==== IT Standard Catalog ====
 +
Prepared/Maintained by:  Enterprise Architecture
 +
 
Key Stakeholders:  Enterprise architects, service architects, solution architects, engineers/implementers.
 
Key Stakeholders:  Enterprise architects, service architects, solution architects, engineers/implementers.
   Line 161: Line 187:     
==== Content Metamodel Diagram ====
 
==== Content Metamodel Diagram ====
 +
Prepared/maintained by:  Enterprise Architecture
 +
 
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]
   Line 170: Line 198:     
==== Lexicon Catalog ====
 
==== Lexicon Catalog ====
 +
Prepared/maintained by:  Enterprise Architecture
 +
 
Key Stakeholders:  All users and practitioners of architecture.  
 
Key Stakeholders:  All users and practitioners of architecture.  
   Line 175: Line 205:     
==== Initiative (Project) Catalog ====
 
==== Initiative (Project) Catalog ====
 +
Prepared/maintained by:  Enterprise architecture, governance body secretariats, others.
 +
 
Key Stakeholders:  Executives, project managers/leads, project teams, enterprise architects, service architects, solution architects, governance bodies, engineers.
 
Key Stakeholders:  Executives, project managers/leads, project teams, enterprise architects, service architects, solution architects, governance bodies, engineers.
   Line 180: Line 212:     
==== Architecture Gaps Catalog ====
 
==== Architecture Gaps Catalog ====
 +
Prepared/maintained by:  Enterprise Architecture
 +
 +
Key Stakeholders:  Enterprise Architecture, Service/solution architects, SISD, Service Lines
 +
 +
Purpose/Value:  To identify SSC gaps so that they may be accommodated in future architecture and initiatives.
 
[[Category:Architecture]]
 
[[Category:Architecture]]
 
[[Category:Enterprise Architecture]]
 
[[Category:Enterprise Architecture]]
 
[[Category:Modeling]]
 
[[Category:Modeling]]

Navigation menu

GCwiki