Difference between revisions of "SSC Architecture Content Metamodel"
Jump to navigation
Jump to search
(Initiated page with definition of content metamodels, and our specific usage/standard at SSC.) |
m |
||
| Line 2: | Line 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 3.0.1 is permitted. | 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 3.0.1 is permitted. | ||
| + | |||
| + | === Content Metamodel Diagram === | ||
| + | To be added... | ||
| + | |||
| + | === Object Definitions === | ||
| + | To be added... | ||
| + | |||
| + | Name | ||
| + | |||
| + | Relationships: | ||
Revision as of 19:35, 19 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 3.0.1 is permitted.
Content Metamodel Diagram
To be added...
Object Definitions
To be added...
Name
Relationships:
