The Fundamental Importance of an Integrated Meta Model to ...archive.opengroup.org/johannesburg2008/presentations...inspired! IT z Consulting zTraining zResearch zTools The Fundamental

inspired!IT Consulting Training Research Tools

The Fundamental Importance of an Integrated Meta Model

to EA Success

Graham McLeodJune 2008


Copyright 2007

Abstract

This talk covers the fundamental importance and role of comprehensive meta models in supporting frameworks for EA, including Zachman, DODAF, TOGAF and IAF. Graham discusses this against the background of implementing multiple concurrent frameworks and architecture notations sharing a single repository and meta model. He relates the experience of Inspired in extending its meta models to support multiple frameworks (especially TOGAF) as well as notations (including TOGAF viewpoints and Archimate). He shows how the meta model is the unifying force to unite the perspectives of business and IT as well as to manage architecture at the conceptual, logical and physical levels. Finally, he shows how user extensibility can allow the support of advanced uses such as integration of risk management, quality management and governance elements (such as controls, cost and responsibility).


Copyright 2007

We Will Look AtMeta Model

ConceptCoverageUsefulnessRole in Supporting Collaboration and Achieving Integration

How Meta Model can support multiple frameworks and perspectives simultaneouslyA Case Study / ExamplesSome meta model extensions that enhance the relevance and profile of EA in the business


Copyright 2007

Meta ModelWhat is a meta model?

Identifies concepts, relationships and properties of the things that we want to modelMay include the way in which we want the concept to be represented (notation, symbol, style etc. )Technically: A class model

Example

FrameworkProvides

User Defined

ApplicationFunction

ApplicationType

Application Scenario

categorises provided by

part of

Status

Transactional

BankMaster

RetailBanking

2006 Optimistic

Upgrade to Rel 3

categorises provided by

part of

Meta Model

Logical

Physical

Content Model


Copyright 2007

Coverage of Meta Model for EADomains

BusinessProcessApplicationInformationTechnology

Cross Cutting ConcernsRiskCostQuality

HousekeepingSecurity and PermissionsTimeframe and Status

Model Types / ViewpointsAudienceContentNotation

Channel Customer Type

Market Competitor

BusinessEvent

Stakeholder Business Goal

Business Communication

BusinessObject

Activity/Business Service Key Indicator

Application

Platform Network Element

Technical Service

Data Collection

DatabaseUser I-Face


Copyright 2007

Usefulness of Meta ModelScope our effortsGenerate QuestionsProvide NavigationProvide the Pigeon holes or Frame for our puzzleShared Vocabulary and Glossary to aid collaborqtionConfigure ToolingProvide Semantics Under the Framework

Regardless of notation or medium of capture or display

Improve the Quality of Modelsconnect rather than naming

Unifies Perspectives


Copyright 2007

VITAL Role of Meta Model

Architect = ConductorMeta Modeler = Arranger


Copyright 2007

Frameworks, Notations and Meta Model

Meta Model supports multiple representations, frameworksFrameworks can co-exist. Content can be captured or viewed via various "lenses"

Technical ArchitectureTechnical Architecture

User Access Application Enablers Data Storage and Management

User Interfaces Connectivity Platforms Services

Business ArchitectureBusiness Architecture Markets Products Services Channels Suppliers Resources Technology Processes Culture Competitors

ApplicationsApplications

Types/Classes InventoryTypes/Classes Inventory

InformationInformation


Driv

ers

Content Models Rep

osito

ryModelTypes ModelTypes

Meta Model


Copyright 2007

Case StudyAdapting the Inspired Frameworks to support TOGAFDone in Q2/3 last yearProcess

Thoroughly study TOGAF to define a meta modelCross map concepts to existing Inspired Meta Model onesIdentify gaps and differences

Extend some types (new properties or relationships)Add new types (few) [e.g. Building Block; Requirement Type; Categories]Add new relationships

Populate types with content [consistent with cateogrisation scheme]Define spatial maps [e.g. Crop Circle; IIIRM; TRM; Ent. Continuum]Define mappings between Meta Model and Viewpoints

Define Model Types

ResultDeep support for TOGAFCoexistence of Inspired, Zachman, IAF, TOGAF and other frameworksAbility to share content across these perspectives and communitiesCertification!


Copyright 2007

Advanced UsesGovernance, Risk and Improvement have become major topics for organizationsMeta Models can be extended to cater for these

Additional types for things like:Risk Categories; Risk Zones to which architecture elements can be relatedControlsGuidelines

Additional properties for things like:Risk score (current; desired)Cost (now, future)Quality (now, future)

Additional relationships for things like:Business Unit / Stakeholder responsible

Having these aspects can really make business executives notice and get involved in EA

Technical ArchitectureTechnical ArchitectureUser Access Application Enablers Data Storage and Management

User Interfaces Connectivity Platforms Services

Business ArchitectureBusiness Architecture Goals Markets Products Services Channels Suppliers Processes Resources Technology Culture Competitors

ApplicationsApplications


InformationInformation

Types/Classes Inventory

Risk

QualityCost


Copyright 2007

Application

Technology

ChannelChannel

Platform

Resource

Project DBMS

President

VP

Minion Minion

VP VP

Minion Minion Minion

Business UnitBusiness Unit

DealsDeals

Cost CentreCost Centre

President

VP

Minion Minion

VP VP


President

VP

Minion Minion

VP VP


Business UnitBusiness UnitTurns out that most of the cost elements are

already in the architecture models!

We need to add attributes to individual

items to record the various relevant costs;

then implement a mechanism to

accumulate them. This adds a model element for Cost Centre. Costs accumulated there can, in turn, be apportioned across business units.

This is a flexible approach that allows

various cost categories to be monitored - various

models can be simultaneously implemented

Cost in Meta Model


Copyright 2007

Drill into same content

Multiple Frameworks


Copyright 2007

Contact & BioGraham [email protected]@pro-mis.com+27 82 578 1834

Inspiredwww.inspired.org+27 21 531 5404

PROMIS Solutions AGwww.pro-mis.com+41 (41) 7 60 73 88

Graham McLeod is widely recognized as a thought leader in the Enterprise Architecture space. He has been delivering EA benefits in organizations via consulting, training, models, methods and frameworks since 1990.

He has taught strategy, enterprise architecture, process modeling, system delivery techniques and project management to hundreds of practitioners while at Comcon, Q Data, University of Cape Town and Inspired.

He is the author of the extremely comprehensive Inspired Enterprise Architecture frameworks (1994 to present) and the architect of the Archi/EA Webmodeler tool recognised by the Association of Enterprise Architects, Gartner and Forrester as one of the leading tools worldwide.

He was recently appointed CTO and chief architect of Promis Solutions AG group in Switzerland. Promis Solutions is a leading European provider of EA and Process tools and services. Graham has spoken at previous Open Group Conferences in Ireland and Cape Town, as well as at IRM Conferences in the UK. He is a certified TOGAF Architect and trainer. He has personally been involved in the strategy and EA efforts of over 20 major organizations worldwide including assurance, retail, banking, telecommunications, information technology, energy, healthcare, education, government and hospitality. He has authored several books and consults at board level via Inspired, Promis and Gartner.

Documents

The Fundamental Importance of an Integrated Meta Model to ...archive.opengroup.org/johannesburg2008/presentations...inspired! IT z Consulting zTraining zResearch zTools The Fundamental