Difference between revisions of "SSC Artifacts and Diagrams"
m |
m |
||
| Line 34: | Line 34: | ||
ArchiMate Viewpoint: Business Process Cooperation Viewpoint | 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". | + | 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. | 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 | + | 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 | + | ====== Segment Diagram ====== |
| + | ArchiMate Viewpoint: Business Process Cooperation Viewpoint | ||
| − | SSC Service Catalog | + | 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. | ||
| + | |||
| + | ====== 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 Library ===== | ||
Revision as of 14:42, 19 September 2019
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.
SSC Key EA Artifacts Diagram
EA Artifacts definitions
The following are the required and recommended artifacts for architecture at SSC.
Strategic Architecture
Strategic Motivation Analysis
Motivation Diagram
ArchiMate Viewpoint: Motivation Viewpoint (standard)
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 Business 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.
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
Reference Architecture Diagram
IT Standard Catalog
Content Metamodel Diagram
Lexicon Catalog
Service/Solution Architecture
SSC Project Catalog
Project Definition
Requirements Catalog
Motivation (Benefits Realization) Diagram
Conceptual Architecture
Solution Context Diagram
Solution Conceptual Diagram
Logical/Physical Architecture
Business Process Cooperation Diagram
Implementation and Deployment Diagram
Application Cooperation Diagram
Technology Usage Diagram
Technology Diagram
