251
edits
Changes
SSC Artifacts and Diagrams (view source)
Revision as of 10:16, 24 September 2020
, 10:16, 24 September 2020no edit summary
Prepared by: Solution architect, service architect.
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.
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.
Based on ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946175 Motivation Viewpoint]
===== Benefits Dependency Map =====
===== Benefits Dependency Map =====
Prepared by: Benefits management (in cooperation with the project/service team and/or service/solution architect)
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.
Scope/Constraints: Uses motivation elements of outcomes and implementation & migration element of work package and deliverable.
Scope/Constraints: Uses motivation elements of outcomes and implementation & migration element of work package and deliverable.
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.
[https://gcdocs.gc.ca/ssc-spc/llisapi.dll?func=ll&objaction=overview&objid=79336116 Benefits Dependency Map Demonstration Video]
[https://gcdocs.gc.ca/ssc-spc/llisapi.dll?func=ll&objaction=overview&objid=79336116 Benefits Dependency Map Demonstration Video]
Based on ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946175 Motivation Viewpoint]
===== Context Diagram =====
===== Context Diagram =====
Prepared by: Service/Solution architect
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.
Key Stakeholders: Enterprise Architect, Governance Bodies (EART, AC, SARB).
Key Stakeholders: Enterprise Architect, Governance Bodies (EART, AC, SARB).
===== Conceptual Diagram =====
===== Conceptual Diagram =====
Prepared by: Service/Solution architect
Prepared by: Service/Solution architect
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.
Scope/Constraints: Show no sequence/flow, and generally no associations. Limited to actors, roles, business functions (key high-level), business information, key application components, system software, technology services.
Scope/Constraints: Show no sequence/flow, and generally no associations. Limited to actors, roles, business functions (key high-level), business information, key application components, system software, technology services.
Key Stakeholders: Governance bodies (particularly AC and ESSARB), project teams/leads/managers, executives, enterprise architects, service architects, solution architects.
Key Stakeholders: Governance bodies (particularly AC and ESSARB), project teams/leads/managers, executives, enterprise architects, service architects, solution architects.
ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946170 Layered Viewpoint]
==== Logical (and sometimes physical) Architecture ====
==== Logical (and sometimes physical) Architecture ====
Prepared by: Service/Solution architect
Prepared by: Service/Solution architect
Purpose/Value: Identifies/defines the business (functions, processes, roles, actors, etc...) of the project/initiative/SSC service, and links to application/data/information layers.
Scope/Constraints: May only use application components from the application layer. May have 1 diagram, or as many in as much detail as is required for the initiative.
Scope/Constraints: May only use application components from the application layer. May have 1 diagram, or as many in as much detail as is required for the initiative.
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.
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.
ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946160 Business Process Cooperation Viewpoint]
===== Logical Application Diagram (optional) =====
===== Logical Application Diagram =====
Prepared by: Service/Solution architect
Prepared by: Service/Solution architect
Purpose/Value: Optional. Used if more details on application or inter/intra-application are required. Focus on application development/components specifically.
Scope/Constraints: Must link applications to business processes/functions as defined in the logical business diagram. Diagram is optional, and is only needed if required to define the application and/or data architecture for the initiative. Can have as many as are required.
Scope/Constraints: Must link applications to business processes/functions as defined in the logical business diagram. Diagram is optional, and is only needed if required to define the application and/or data architecture for the initiative. Can have as many as are required.
Key Stakeholders: Application managers, application architects, service architects, solution architects, CIO office, project team, application developers.
Key Stakeholders: Application managers, application architects, service architects, solution architects, CIO office, project team, application developers.
ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946162 Application Cooperation Viewpoint]
===== Logical Technology (Usage) Diagram =====
===== Logical Technology (Usage) Diagram =====
Prepared by: Service/Solution architect
Prepared by: Service/Solution architect
Purpose/Value: Maps applications/application systems to required (generic/high level) technology implementations.
Scope/Constraints: Must link the diagram (with objects within the diagram) to either a logical application diagram (and/or objects), or a logical business diagram (or functions/processes therein). Optional. Many have as many as is required to define the technology architecture to the level of detail desired.
Scope/Constraints: Must link the diagram (with objects within the diagram) to either a logical application diagram (and/or objects), or a logical business diagram (or functions/processes therein). Optional. Many have as many as is required to define the technology architecture to the level of detail desired.
Key Stakeholders: Service architects, solution architects, engineers, designers, implementers, operations staff, application support staff and management.
Key Stakeholders: Service architects, solution architects, engineers, designers, implementers, operations staff, application support staff and management.
ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946166 Technology Usage Viewpoint]
===== Logical Technology Diagram =====
===== Logical Technology Diagram =====
Prepared by: Service/Solution architect
Prepared by: Service/Solution architect
Purpose/Value: Identifies/defines the required technology components, positioning/placement/location, relationships, network, network zoning required for the initiative.
Scope/Constraints: None.
Scope/Constraints: None.
Key Stakeholders: Service architects, solution architects, engineers, designers, implementers, operations staff.
Key Stakeholders: Service architects, solution architects, engineers, designers, implementers, operations staff.
ArchiMate Viewpoint: [https://pubs.opengroup.org/architecture/archimate3-doc/apdxc.html#_Toc489946165 Technology Viewpoint]
=== Reference Library ===
=== Reference Library ===