Difference between revisions of "SSC Architecture Content Metamodel"
Jump to navigation
Jump to search
m (Added reference links/citations.) |
m |
||
| Line 1: | Line 1: | ||
| + | [[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> | ||
Revision as of 09:24, 20 September 2019
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 (TOGAF 9: 30.2.2)
Our content metamodel is based largely on the TOGAF 9.2 and (primarily) on the ArchiMate 3.0.1 specification, with some specific adaptations and alignment for SSC. In general, unless specified, any relationship permitted in ArchiMate is permitted.
Content Metamodel Diagrams
High Level/Overview
5-5-5 Model
Network and Zoning Metamodel
Object Definitions
To be added...
Name
Relationships:
