| 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.  It does not show detailed information about roles, processes, information, technologies, applications involved in each segment.  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  | + | ====== 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 =====  |