251
edits
Changes
SSC Artifacts and Diagrams (view source)
Revision as of 15:37, 23 January 2020
, 15:37, 23 January 2020Changed title sizes.
[[File:EA Sticker.png|alt=SSC Enterprise Architecture|right|frameless|225x225px]]
[[File:EA Sticker.png|alt=SSC Enterprise Architecture|right|frameless|225x225px]]
In addition to a content metamodel, SSC has established a set of specific artifacts (catalogs, matrices, diagrams) that are required. In general, these artifacts follow the recommended viewpoints established in the [https://pubs.opengroup.org/architecture/archimate3-doc/ ArchiMate 3.0.1 Specification]. However, in some instances we have chosen diagrams that better suit our particular needs, particularly in respect to project and service governance.
In addition to a content metamodel, SSC has established a set of specific artifacts (catalogs, matrices, diagrams) that are required. In general, these artifacts follow the recommended viewpoints established in the [https://pubs.opengroup.org/architecture/archimate3-doc/ ArchiMate 3.0.1 Specification]. However, in some instances we have chosen diagrams that better suit our particular needs, particularly in respect to project and service governance. The following are the required and recommended artifacts for architecture at SSC.
=== SSC Key EA Artifacts Diagram ===
=== SSC Key EA Artifacts Diagram ===
[[File:EA_Models_Structure.png|frameless|944x944px]]
[[File:EA_Models_Structure.png|frameless|944x944px]]
=== EA Artifacts definitions ===
=== Enterprise Architecture ===
==== Strategic Motivation Analysis ====
This set of catalogs and diagrams are used to, at the enterprise/strategic level, identify the motivators for SSC. These include strategic plans and directions, legislation, policy, GC Initiatives, and more. The items managed here are intended to be leveraged organization-wide.
This set of catalogs and diagrams are used to, at the enterprise/strategic level, identify the motivators for SSC. These include strategic plans and directions, legislation, policy, GC Initiatives, and more. The items managed here are intended to be leveraged organization-wide.
===== Motivation Diagram =====
ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946175 Motivation Viewpoint]
ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946175 Motivation Viewpoint]
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/Service Overview Diagram =====
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]
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. Segment diagrams are produced for each segment that provides a more complete definition of what belongs in each segment.
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. Segment diagrams are produced for each segment that provides a more complete definition of what belongs in each segment.
===== Segment Diagram =====
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]
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.
===== Conceptual Service Diagram =====
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]
Purpose/Value: Provides a conceptual view of SSC Services, key inter-service linkages, strategic linkages, and links to enabling technologies.
Purpose/Value: Provides a conceptual view of SSC Services, key inter-service linkages, strategic linkages, and links to enabling technologies.
===== Conceptual Foundation Technology Diagram =====
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]
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.
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.
===== SSC Service Catalog =====
Key Stakeholders: SSC executives, service mangement, service inventory, enterprise architects, service leads, service teams, service architects, solution architects.
Key Stakeholders: SSC executives, service mangement, service inventory, enterprise architects, service leads, service teams, service architects, solution architects.
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: Provides a list of the SSC functions designated as "SSC Services" including with key attributes used for service management and service inventory management.
==== Reference Library ====
===== Reference Architecture Catalog =====
Key Stakeholders: Enterprise architects, service architects, solution architects, engineers/implementers.
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.
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]
ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946170 Layered Viewpoint]
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.
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.
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.
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]
ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946170 Layered Viewpoint]
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.
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.
Key Stakeholders: All users and practitioners of architecture.
Purpose/Value: Provides definitions of terms/nomenclature used for 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.
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.
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.
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.
Purpose/Value: List and definitions of the requirements for a project/initiative. .
Purpose/Value: List and definitions of the requirements for a project/initiative. .
===== Motivation (Benefits Realization) Diagram =====
ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946175 Motivation Viewpoint]
ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946175 Motivation Viewpoint]
==== Conceptual Architecture ====
==== Conceptual Architecture ====
===== Solution Context Diagram =====
moved - and integrated with the Solution Conceptual Diagram.
moved - and integrated with the Solution Conceptual Diagram.
===== Solution Conceptual Diagram =====
ArchiMate Viewpoint: Non-Standard (SSC specific)
ArchiMate Viewpoint: Non-Standard (SSC specific)
Purpose/Value: Identifies what, at a high/conceptual level, this project/initiative intends to do (key/main functions), for which clients (roles/actors), and what key information will be required/managed, and what key performance indicators/benefits will be provided by doing the effort.
Purpose/Value: Identifies what, at a high/conceptual level, this project/initiative intends to do (key/main functions), for which clients (roles/actors), and what key information will be required/managed, and what key performance indicators/benefits will be provided by doing the effort.
==== Logical/Physical Architecture ====
===== Business Process Cooperation Diagram =====
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]
Purpose/Value: Identifies/defines the business (functions, processes, roles, actors, etc...) of the project/initiative/SSC service, and links to application/data/information layers.
Purpose/Value: Identifies/defines the business (functions, processes, roles, actors, etc...) of the project/initiative/SSC service, and links to application/data/information layers.
===== Implementation and Deployment Diagram (optional) =====
ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946164 Implementation and Deployment Viewpoint]
ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946164 Implementation and Deployment Viewpoint]
Purpose/Value: Optional. Used if more details on application or inter/intra-application and technology interactions are required than is provided in the Technology Usage Diagram (below).
Purpose/Value: Optional. Used if more details on application or inter/intra-application and technology interactions are required than is provided in the Technology Usage Diagram (below).
===== Application Cooperation Diagram (optional) =====
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]
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.
===== Technology Usage Diagram =====
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]
Purpose/Value: Maps applications/application systems to required (generic/high level) technology implementations.
Purpose/Value: Maps applications/application systems to required (generic/high level) technology implementations.
===== Technology Diagram =====
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]