Line 6: |
Line 6: |
| === Content Metamodel Diagrams === | | === Content Metamodel Diagrams === |
| ==== High Level/Overview ==== | | ==== High Level/Overview ==== |
− | | + | [[File:SCC MetalModelDraft-V3.5.png|frameless|1173x1173px]] |
− | ==== [[File:SCC MetalModelDraft-V3.5.png|frameless|1173x1173px]] ====
| |
− | | |
| ==== SSC Services and Segments ==== | | ==== SSC Services and Segments ==== |
− | | + | [[File:SCC MetalModelDraft-V3.6 - Service and Segment.png|frameless|691x691px]] |
− | ==== [[File:SCC MetalModelDraft-V3.6 - Service and Segment.png|frameless|691x691px]] ====
| |
− | | |
| ==== Motivation Details ==== | | ==== Motivation Details ==== |
| [[File:SCC MetalModelDraft-V3.6 - Motivation.png|frameless|1198x1198px]] | | [[File:SCC MetalModelDraft-V3.6 - Motivation.png|frameless|1198x1198px]] |
− |
| |
| ==== 5-5-5 Model ==== | | ==== 5-5-5 Model ==== |
| [[File:SCC MetalModelDraft-V3.5 - 555.png|frameless|575x575px]] | | [[File:SCC MetalModelDraft-V3.5 - 555.png|frameless|575x575px]] |
| + | |
| + | ==== Security ==== |
| + | [[File:SCC MetalModelDraft-V3.6 - Security.png|frameless|600x600px]] |
| + | |
| + | ==== Privacy ==== |
| + | [[File:SCC MetalModelDraft-V3.6 - Privacy.png|frameless|599x599px]] |
| | | |
| ==== Network and Zoning Metamodel ==== | | ==== Network and Zoning Metamodel ==== |
Line 74: |
Line 75: |
| * Must link directly (or indirectly through another business service, interface or product) to a client of the related function for the service. | | * Must link directly (or indirectly through another business service, interface or product) to a client of the related function for the service. |
| * Naming: Should use verb ending. May use an "ing" ending. The verb should describe the primary activity of the service, e.g.: "Insurance claim processing". | | * Naming: Should use verb ending. May use an "ing" ending. The verb should describe the primary activity of the service, e.g.: "Insurance claim processing". |
| + | |
| + | ==== Capability ==== |
| + | A capability represents an ability that an organization, person, or system possesses. We primarily use capabilities in capability maps, that allow architecture to present a higher-level more strategic and conceptual view of the state of the enterprise, and to help with decision-making. |
| + | * Linking: Capabilities can link to other capabilities (e.g. parent/child) - indicated with serving relationships. |
| + | * Linking: Business functions should link and be linkable to capabilities (realize). Capabilities should realize outcomes or goals in the motivation layer. |
| + | * Linking: Only business functions from the core elements should link to capabilities.l |
| + | * Tend to be more abstract than most SSC services, functions, processes. |
| | | |
| ==== SSC Services ==== | | ==== SSC Services ==== |
| 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. |
− | Name
| + | * SSC Services (or their sub-functions) should always be linked to one or more Capabilities. |
− | | + | [[Category:Architecture]] |
− | Relationships:
| + | [[Category:Enterprise Architecture]] |
| + | [[Category:Modeling]] |