Changes

Jump to navigation Jump to search
m
no edit summary
Line 66: Line 66:  
ArchiMate Viewpoint:  Layered Viewpoint
 
ArchiMate Viewpoint:  Layered Viewpoint
   −
Scope/Constraints:  Uses any/all required objects, in generic/abstract forms, at any level.     
+
Scope/Constraints:  None.     
    
Key Stakeholders:  Enterprise architects, service architects, solution architects, engineers/implementers.
 
Key Stakeholders:  Enterprise architects, service architects, solution architects, engineers/implementers.
Line 78: Line 78:     
====== Content Metamodel Diagram ======
 
====== Content Metamodel Diagram ======
Lexicon Catalog
+
ArchiMate Viewpoint:  Layered Viewpoint
 +
 
 +
Scope/Constraints:  None.   
 +
 
 +
Key Stakeholders:  Enterprise architects, service architects, solution architects, engineers/implementers.
 +
 
 +
Purpose/Value:  Illustrates the valid relationships amongst all types of architecture objects, and the rules to be applied for their use in architecture models.  The model of the model for architecture.
 +
 
 +
====== Lexicon Catalog ======
 +
Key Stakeholders:  All users and practitioners of architecture.
 +
 
 +
Purpose/Value:  Provides definitions of terms/nomenclature used for architecture.
    
==== Service/Solution Architecture ====
 
==== Service/Solution Architecture ====
SSC Project Catalog
+
 
 +
====== SSC Project Catalog ======
 +
Key Stakeholders:  Executives, project managers/leads, project teams, enterprise architects, service architects, solution architects, governance bodies, engineers.
 +
 
 +
Purpose/Value:  Used to associate objects, artifacts, deliverables to particular projects/initiatives.
    
===== Project Definition =====
 
===== Project Definition =====

Navigation menu

GCwiki