Changes

Updating solution architecture portion.
Line 56: Line 56:  
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.
 
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 ====
+
=== 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.
   −
===== Reference Architecture Catalog =====
+
==== Requirements Diagram ====
 
  −
Key Stakeholders:  Enterprise architects, service architects, solution architects, engineers/implementers.
  −
 
  −
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 =====
  −
ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946170 Layered Viewpoint]
  −
 
  −
Scope/Constraints:  None.   
  −
 
  −
Key Stakeholders:  Enterprise architects, service architects, solution architects, engineers/implementers.
  −
 
  −
Purpose/Value:  Diagrams of reference architecture patterns/options, to illustrate patterns and considerations for preparing new architectures under particular defined conditions/circumstances.  Used to ensure alignment/compliance and consistency of implementations.
  −
 
  −
===== IT Standard Catalog =====
  −
Key Stakeholders:  Enterprise architects, service architects, solution architects, engineers/implementers.
  −
 
  −
Purpose/Value:  Provides a list of IT Standards to be applied to architectures, designs and implementations at SSC.  Used to ensure alignment/compliance and consistency of implementations.
  −
 
  −
===== Content Metamodel Diagram =====
  −
ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946170 Layered Viewpoint]
  −
 
  −
Scope/Constraints:  None.   
  −
 
  −
Key Stakeholders:  Enterprise architects, service architects, solution architects, engineers/implementers.
  −
 
  −
Purpose/Value:  Illustrates the valid relationships amongst all types of architecture objects, and the rules to be applied for their use in architecture models.  The model of the model for architecture.
  −
 
  −
===== Lexicon Catalog =====
  −
Key Stakeholders:  All users and practitioners of architecture.
  −
 
  −
Purpose/Value:  Provides definitions of terms/nomenclature used for architecture.
  −
 
  −
===== SSC Project Catalog =====
  −
Key Stakeholders:  Executives, project managers/leads, project teams, enterprise architects, service architects, solution architects, governance bodies, engineers.
  −
 
  −
Purpose/Value:  Used to associate objects, artifacts, deliverables to particular projects/initiatives.
  −
 
  −
==== Service/Solution Architecture ====
  −
These diagrams are for service or solution architectures for initiatives to be reviewed/aligned by EA.
  −
 
  −
==== Project Definition ====
  −
===== Requirements Catalog =====
   
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.
   Line 176: Line 134:     
Purpose/Value:  Identifies/defines the required technology components, positioning/placement/location, relationships, network, network zoning required for the initiative.
 
Purpose/Value:  Identifies/defines the required technology components, positioning/placement/location, relationships, network, network zoning required for the initiative.
 +
 +
=== Reference Library ===
 +
 +
==== Reference Architecture Catalog ====
 +
 +
Key Stakeholders:  Enterprise architects, service architects, solution architects, engineers/implementers.
 +
 +
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 ====
 +
ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946170 Layered Viewpoint]
 +
 +
Scope/Constraints:  None.   
 +
 +
Key Stakeholders:  Enterprise architects, service architects, solution architects, engineers/implementers.
 +
 +
Purpose/Value:  Diagrams of reference architecture patterns/options, to illustrate patterns and considerations for preparing new architectures under particular defined conditions/circumstances.  Used to ensure alignment/compliance and consistency of implementations.
 +
 +
==== IT Standard Catalog ====
 +
Key Stakeholders:  Enterprise architects, service architects, solution architects, engineers/implementers.
 +
 +
Purpose/Value:  Provides a list of IT Standards to be applied to architectures, designs and implementations at SSC.  Used to ensure alignment/compliance and consistency of implementations.
 +
 +
==== Content Metamodel Diagram ====
 +
ArchiMate Viewpoint:  [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946170 Layered Viewpoint]
 +
 +
Scope/Constraints:  None.   
 +
 +
Key Stakeholders:  Enterprise architects, service architects, solution architects, engineers/implementers.
 +
 +
Purpose/Value:  Illustrates the valid relationships amongst all types of architecture objects, and the rules to be applied for their use in architecture models.  The model of the model for architecture.
 +
 +
==== Lexicon Catalog ====
 +
Key Stakeholders:  All users and practitioners of architecture.
 +
 +
Purpose/Value:  Provides definitions of terms/nomenclature used for architecture.
 +
 +
==== Initiative (Project) Catalog ====
 +
Key Stakeholders:  Executives, project managers/leads, project teams, enterprise architects, service architects, solution architects, governance bodies, engineers.
 +
 +
Purpose/Value:  Used to associate objects, artifacts, deliverables to particular projects/initiatives.
    
[[Category:Architecture]]
 
[[Category:Architecture]]
 
[[Category:Enterprise Architecture]]
 
[[Category:Enterprise Architecture]]
 
[[Category:Modeling]]
 
[[Category:Modeling]]