TOGAF V91 M7 Metamodel
TOGAF V91 M7 Metamodel
Slide 1 of 45
TOGAF is a registered trademark of The Open Group in the United States and other countries
Slide 2 of 45
Roadmap
Part I - Introduction
Preface, Executive Overview, Core Concepts, Definitions and Release Notes
Slide 3 of 45
Module Objectives
The objectives of this module are to describe: What a metamodel is and why it is needed Key concepts of the Core Metamodel The division of the metamodel into Core and Extensions Key concepts of the Core Metamodel Entities The components of the TOGAF Content Metamodel
Slide 4 of 45
What is a metamodel?
A metamodel is a precise definition of the constructs and rules needed for creating models
Source www.metamodel.com
A model that describes how and with what the architecture will be described in a structured way.
TOGAF 9 definitions
Slide 5 of 45
Why a metamodel?
Slide 6 of 45
Slide 7 of 45
Slide 8 of 45
Slide 9 of 45
Slide 10 of 45
Slide 11 of 45
Slide 12 of 45
Slide 14 of 45
Stakeholder Needs
Executive CxO Programme Management Office Line Management
Executive
HR
Line Management
Application Management
Infrastructure Management
Procurement
Stakeholder Types QA/ Standards Groups Product Specialists Enterprise Security Technical Specialists
Corporate
System
End - User
Project
Slide 15 of 45
Slide 17 of 45
Slide 18 of 45
Slide 19 of 45
TOGAF 9 Artifacts
Requirements catalog Phase C, Data Architecture Data Entity/Data Component catalog Data Entity/Business Function matrix Application/Data matrix Logical Data diagram Data Dissemination diagram
Phase C, Application Architecture Application Portfolio catalog Interface catalog Application/Organization matrix Role/Application matrix Application/Function matrix Application Interaction matrix Application Communication diagram Application and User Location diagram Application Use-Case diagram
Phase D, Technology Architecture Technology Standards catalog Technology Portfolio catalog System/Technology matrix Environments and Locations diagram Platform Decomposition diagram
Slide 20 of 45
10
Slide 21 of 45
Slide 22 of 45
11
Slide 23 of 45
Metamodel Extensions
Slide 24 of 45
12
Governance Extension
Slide 25 of 45
Governance Extension
Scope:
The ability to apply measures to objectives and then link those measures to services The ability to apply contracts to service communication or service interactions with external users and systems The ability to define re-usable service qualities defining a servicelevel profile that can be used in contracts Creation of additional diagrams to show ownership and management of systems
Slide 26 of 45
13
Governance Extension
This extension should be used in the following situations:
When an organization is considering IT change that will result in a significant impact to existing operational governance models When an organization has granular requirements for service levels that differ from service to service When an organization is looking to transform its operational governance practice
Slide 27 of 45
Services Extension
Slide 28 of 45
14
Services Extension
Scope:
Creation of IS services as an extension of business service
Slide 29 of 45
Services Extension
This extension should be used in the following situations:
When the business has a preset definition of its services that does not align well to technical and architectural needs When business and IT use different language to describe similar capabilities Where IT service is misaligned with business need, particularly around the areas of quality of service, visibility of performance, and management granularity Where IT is taking initial steps to engage business in discussions about IT architecture
Slide 30 of 45
15
Slide 31 of 45
Slide 32 of 45
16
Slide 33 of 45
Data Extension
Slide 34 of 45
17
Data Extension
Scope:
Creation of logical data components that group data entities into encapsulated modules for governance, security, and deployment purposes Creation of physical data components that implement logical data components; analogous to databases, registries, repositories, schemas, and other techniques of segmenting data Creation of data lifecycle, data security, and data migration diagrams to show data concerns in more detail
Slide 35 of 45
Data Extension
This extension should be used in the following situations:
Where the architecture features significant complexity and risk around the location, encapsulation, and management of or access to data
Slide 36 of 45
18
Slide 37 of 45
Additional diagrams to be created: Process/System Realization diagram Software Engineering diagram Application Migration diagram Software Distribution diagram Processing diagram Networked Computing/Hardware diagram Communications Engineering diagram
Slide 38 of 45
19
Motivation Extension
Slide 40 of 45
20
Motivation Extension
The scope of this extension is as follows:
Creation of a new metamodel entity for Driver that shows factors generally motivating or constraining an organization Creation of a new metamodel entity for Goal that shows the strategic purpose and mission of an organization Creation of a new metamodel entity for Objective that shows near to midterm achievements that an organization would like to attain Creation of a Goal/Objective/Service diagram showing the traceability from drivers, goals, and objectives through to services
Slide 41 of 45
Motivation Extension
This extension should be used in the following situations:
When the architecture needs to understand the motivation of organizations in more detail than the standard business or engagement principles and objectives that are informally modeled within the core content metamodel When organizations have conflicting drivers and objectives and that conflict needs to be understood and addressed in a structured form When service levels are unknown or unclear
Slide 42 of 45
21
Summary
TOGAF provides a rich metamodel This provides a number of benefits: It supports both formal and informal modeling It formalizes the definition of an Enterprise Architecture It formalizes the relationship between objects It enables an EA tool mapping
Slide 43 of 45
Exercise
Determine which of the Metamodel extensions is most appropriate for the following situations:
1. 2. 3. 4. 5. Where organizations have conflicting objectives Where service levels are unknown Where many applications are in use with overlapping functionality Where management of information is complex Where business process has to support regulatory compliance
Slide 44 of 45
22
TOGAF is a registered trademark of The Open Group in the United States and other countries
Slide 45 of 45
23