Changes

m
no edit summary
Line 101: Line 101:     
====== Requirements Catalog ======
 
====== Requirements Catalog ======
Key Stakeholders:  Project managers, project teams, business analyists,bu iness architects, sservice 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.  .
Line 110: Line 110:  
Scope/Constraints:  None.     
 
Scope/Constraints:  None.     
   −
Key Stakeholders:   
+
Key Stakeholders: Project manager/lead, project team, business analyst, benefits realization team, governance bodies, management.  
   −
Purpose/Value:   
+
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 ====
 
==== Conceptual Architecture ====
Solution Context Diagram
     −
Solution Conceptual Diagram
+
====== Solution Context Diagram ======
 +
ArchiMate Viewpoint:  Non-Standard (SSC specific)
 +
 
 +
Scope/Constraints:  Limited to business function, work package, capability, gap, plateau, requirement, outcome, goal.   
 +
 
 +
Key Stakeholders:  Governance bodies (particularly AC and ESSARB), project teams/leads/managers, executives, enterprise architects, service architects, solution architects. 
 +
 
 +
Purpose/Value:  Identifies what, if any strategic goals/outcomes and business capabilities a project/initiative is intending to realize/support. 
 +
 
 +
====== 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 =====
 
===== Logical/Physical Architecture =====
Business Process Cooperation Diagram
     −
Implementation and Deployment Diagram
+
====== Business Process Cooperation Diagram ======
 +
ArchiMate Viewpoint:  Business Process Cooperation Viewpoint
   −
Application Cooperation Diagram
+
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.
 +
 
 +
====== Application Cooperation Diagram ======
 +
Optional.
 +
 
 +
====== Technology Usage Diagram ======
 +
ArchiMate Viewpoint:  Technology Usage Viewpoint
 +
 
 +
Scope/Constraints:  None.   
 +
 
 +
Key Stakeholders:  Service architects, solution architects, engineers, designers, implementors, 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.   
   −
Technology Usage Diagram
+
Key Stakeholders:  Service architects, solution architects, engineers, designers, implementors, operations staff. 
   −
Technology Diagram
+
Purpose/Value:  Identifies/defines the required technology components, positioning/placement/location, relationships, network, network zoning required for the initiative.