251
edits
Changes
SSC Artifacts and Diagrams (view source)
Revision as of 16:09, 19 September 2019
, 16:09, 19 September 2019→Implementation and Deployment Diagram
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 ======
====== Implementation and Deployment Diagram (optional) ======
ArchiMate Viewpoint: Implementation and Deployment Viewpoint.
====== Application Cooperation Diagram ======
Scope/Constraints: None.
Optional.
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) ======
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 ======
====== Technology Usage Diagram ======
Scope/Constraints: None.
Scope/Constraints: None.
Key Stakeholders: Service architects, solution architects, engineers, designers, implementors, operations staff, application support staff and management.
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.
Purpose/Value: Maps applications/application systems to required (generic/high level) technology implementations.
Scope/Constraints: None.
Scope/Constraints: None.
Key Stakeholders: Service architects, solution architects, engineers, designers, implementors, operations staff.
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.
Purpose/Value: Identifies/defines the required technology components, positioning/placement/location, relationships, network, network zoning required for the initiative.