Changes

[[File:EA Sticker.png|alt=SSC Enterprise Architecture|right|frameless|225x225px]]

 

'''For information about SSC's Enterprise Architecture practice, please see: [[/163gc.sharepoint.com/sites/ACoE-CEA/SitePages/Home.aspx|Architecture Centre of Excellence - Centre d'excellence en architecture - Home]]'''[[File:EA Sticker.png|alt=SSC Enterprise Architecture|right|frameless|225x225px]]

A content metamodel defines a set of entities that allow architectural concepts to be captured, stored, filtered, queried, and represented in a way that supports consistency, completeness, and traceability <small>([https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap30.html#tag_30_02 TOGAF 9: 30.2.2])</small>

A content metamodel defines a set of entities that allow architectural concepts to be captured, stored, filtered, queried, and represented in a way that supports consistency, completeness, and traceability <small>([https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap30.html#tag_30_02 TOGAF 9: 30.2.2])</small>

SSC Services are usually business functions, and should not be represented as ArchiMate business services.

SSC Services are usually business functions, and should not be represented as ArchiMate business services.

* Representation:  Must be represented as a business function, with category of "client-facing service" or "supporting service"

* Representation:  Must be represented as a business function, with category of "client-facing service" or "supporting service"

* Naming:  As defined by SSC Service Management Framework.   

* Naming:  As defined by SSC Service Management Framework.

* SSC Services (or their sub-functions) should always be linked to one or more Capabilities.   

[[Category:Architecture]]

[[Category:Architecture]]

[[Category:Enterprise Architecture]]

[[Category:Enterprise Architecture]]

[[Category:Modeling]]

[[Category:Modeling]]