Difference between revisions of "SSC Artifacts and Diagrams"
(Changed title sizes.) |
|||
| Line 1: | Line 1: | ||
[[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]] | ||
| − | === | + | === 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] | ||
| Line 31: | 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. | 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] | ||
| Line 42: | Line 39: | ||
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] | ||
| Line 51: | Line 48: | ||
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] | ||
| Line 60: | Line 57: | ||
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] | ||
| Line 78: | Line 75: | ||
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. | ||
| Line 84: | Line 81: | ||
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. | ||
| Line 92: | Line 89: | ||
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] | ||
| Line 101: | Line 98: | ||
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] | ||
| Line 115: | Line 112: | ||
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] | ||
| Line 145: | Line 142: | ||
==== 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) | ||
| Line 158: | Line 155: | ||
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] | ||
| Line 169: | Line 166: | ||
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] | ||
| Line 178: | Line 175: | ||
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] | ||
| Line 187: | Line 184: | ||
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] | ||
| Line 196: | Line 193: | ||
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] | ||
Revision as of 15:37, 23 January 2020
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 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
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.
Motivation Diagram
ArchiMate Viewpoint: Motivation Viewpoint
Scope/Constraints: None.
Key Stakeholders: Enterprise architects, business analysts, strategic planning, benefits realization team.
Purpose/Value: Used to identify and related the key 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.
Business Capability Map
ArchiMate Viewpoint: Capability Map
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.
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: Business Process Cooperation Viewpoint
Scope/Constraints: Uses only business functions, and business functions with categories "SSC Segment", "SSC Client-facing Service", and "SSC Supporting Service". It does not show detailed information about roles, processes, information, technologies, applications involved in each segment. One diagram shows all segments, and key high-level associated functions.
Key Stakeholders: Enterprise architects/Enterprise Architecture management/executives.
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: Business Process Cooperation Viewpoint
Scope/Constraints: Uses only business functions, 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.
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: Layered Viewpoint
Scope/Constraints: A template is provided to complete the diagram. This particular diagram links the SSC Service to Business Capabilities (1 or more), and to other key business functions/services, and to the key foundational/supporting technologies. Similar to the Conceptual Foundation Technology diagrams, except the focus here is on the business function and clients, rather than the technologies. The diagram may expose some of the key sub-functions/processes that are performed in that SSC service.
Key Stakeholders: Enterprise architects/Enterprise Architecture management/executives.
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: Layered Viewpoint
Scope/Constraints: A template is provided to complete the diagram. This particular diagram links the SSC Service to Business Capabilities (1 or more), and to other key business functions/services, and to the key foundational/supporting technologies. Similar to the Conceptual Service Diagram, except the focus is on the enabling technologies, rather than business functions/processes. The diagram may expose some of the key technology sub-functions/services that are used.
Key Stakeholders: Enterprise architects/Enterprise Architecture management/executives.
Purpose/Value: Provides a conceptual view of SSC Services, key inter-service linkages, strategic linkages, and links to enabling technologies.
Capability Planning View
ArchiMate Viewpoint: Capability Planning View (Custom: Base on Capability Planning view at: https://www.hosiaisluoma.fi/blog/archimate-examples)
Scope/Constraints: Link any Business Function or Business Process to a capability.
Key Stakeholders: Enterprise architects, segment architects, strategic planning.
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.
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.
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: 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: 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.
Purpose/Value: List and definitions of the requirements for a project/initiative. .
Motivation (Benefits Realization) Diagram
ArchiMate Viewpoint: Motivation Viewpoint
Scope/Constraints: None.
Key Stakeholders: Project manager/lead, project team, business analyst, benefits realization team, governance bodies, management.
Purpose/Value: Identify the benefits of a projects/initiative, identifying key performance metrics, help ensure alignment with enterprise outcomes, identify and link requirements to tactical and strategic outcomes.
Conceptual Architecture
Solution Context Diagram
moved - and integrated with the Solution Conceptual Diagram.
Solution Conceptual Diagram
ArchiMate Viewpoint: Non-Standard (SSC specific)
Scope/Constraints: Show no sequence/flow, and generally no associations. Limited to actors, roles, business functions (key high-level), business information, KPI's.
Key Stakeholders: Governance bodies (particularly AC and ESSARB), project teams/leads/managers, executives, enterprise architects, service architects, solution architects.
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: Business Process Cooperation Viewpoint
Scope/Constraints: May only use application components from the application layer.
Key Stakeholders: Governance bodies (particularly AC and ESSARB), project teams/leads/managers, enterprise architects, service architects, solution architects, business leads, business architects, business analists, business process practicioners.
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: Implementation and Deployment Viewpoint
Scope/Constraints: None.
Key Stakeholders: Application managers, application architects, service architects, solution architects, CIO office, project team, application developers.
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: Application Cooperation Viewpoint
Scope/Constraints: None.
Key Stakeholders: Application managers, application architects, service architects, solution architects, CIO office, project team, application developers.
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: Technology Usage Viewpoint
Scope/Constraints: None.
Key Stakeholders: Service architects, solution architects, engineers, designers, implementers, operations staff, application support staff and management.
Purpose/Value: Maps applications/application systems to required (generic/high level) technology implementations.
Technology Diagram
ArchiMate Viewpoint: Technology Viewpoint
Scope/Constraints: None.
Key Stakeholders: Service architects, solution architects, engineers, designers, implementers, operations staff.
Purpose/Value: Identifies/defines the required technology components, positioning/placement/location, relationships, network, network zoning required for the initiative.
