mega & the zachman framework - e-dnrs · pdf filemega & zachman page 3 what is the...

MEGA & the Zachman Framework

Positioning MEGA Suite™ against the very famous Zachman Framework

MEGA & Zachman page 2

MEGA & the Zachman Framework

MEGA & the Zachman Framework 1

Positioning MEGA Suite™ against the very famous Zachman Framework 1

Introduction 2 What is the Zachman Framework? 3

What does the Zachman Framework look like? 4

Zachman Framework benefits 6 Project scope definition 7 Checking project completeness 7 A learning tool 8

Zachman Framework & MEGA 9 MEGA Zachman Portal 11 MEGA Concepts mapping 12

Annexes 22 Annex A -Customization samples 22

Annex B - Usual definition of the Zachman Framework cells 24

Introduction

This document positions MEGA Suite™ against the very famous Zachman Framework™.

It provides a summary of what the Zachman Framework™ is and how the MEGA Suite is

related to this framework.

This document includes information from Internet sources, including John Zachman

website.


What is the Zachman Framework?

The Enterprise Architecture Framework (EA) frequently called the Zachman Framework,

introduced in 1987 by John Zachman and extended by Sowa in 1992 (Sowa and Zachman

1992), as it applies to enterprises is a logical structure for classifying and organizing the

descriptive representations of an enterprise that are significant to the management of the

enterprise as well as to the development of the enterprise’s systems. It was derived from

analogous structures that are found in the older disciplines of Architecture/Construction

and Engineering/Manufacturing that classify and organize the design artifacts created over

the process of designing and producing complex physical products (e.g., buildings or

airplanes.)

The units of the Framework can also be understood as organization scheme for all kinds of

metadata involved in building and using an information system and have therefore become

widely recognized during the last years.

This Framework is intended being neutral in the sense that it’s defined totally independents

from tools or methodologies and therefore any tool or any methodology can be mapped

against it to understand what they are doing, and what they are NOT doing.

The Zachman Framework cannot be considered as either a modeling language, or a

methodology, or a modeling notation.


What does the Zachman Framework look like?

The Zachman Framework appears as a matrix containing 30 cells, each of them focusing on

one dimension or perspective of the enterprise.

Rows are often presented as levels of abstraction involved in the systems development

process, while columns represent different perspectives also involved in the cycle. However,

these rows, really, are different dimensions, each one being candidate to some

decomposition and realization layers, handling various levels of abstraction.

Zachman and his followers established a set of rules for interpreting and using the original

framework (see Bruce, 1992). These may be summarized as follows.

• Rule 1: The columns have no ordering. No one is more important than another but

focusing on one may have significant practical implications.

• Rule 2: Each column represents a unique model.


• Rule 3: Each column is unique although they are interconnected.

• Rule 4: Each row represents a unique perspective.

• Rule 5: Therefore, each cell is unique (no item should show up in more than one

cell).

• Rule 6: Each row is a complete model from the row's perspective.

• Rule 7: The logic is recursive and generic.


Zachman Framework benefits

“There are four reasons why you do Architecture: "Alignment," "Integration," "Change," and "Reduced Time-to-Market."

• Do you care that the systems I/S is producing actually are aligned with Management's requirements and warrant the expenditure of funds allocated to I/S?

• Do you care whether the data in the Enterprise means the same thing to anyone who uses it, that messages can be cost-effectively transmitted and received whatever time of day or night or day of the year, and that business rules can be uniformly enforced throughout the Enterprise?

• Do you care whether changes to the Enterprise can be made with minimum time, disruption, and cost?

• Do you care whether I/S can produce "custom" implementations on demand, reducing their time-to-market to virtually zero?

If you care about any or all of these things, YOU ARE GOING TO DO ARCHITECTURE, because without Architecture, you cannot do ANY of these things.”

Architecture is an asset. You can save orders of magnitude more money and time, but you have to invest in Architecture to enable you to do something you otherwise are unable to do, namely: "Alignment," "Integration," "Change," and "Mass Customization."

John Zachman

Modeling techniques are the best way to efficiently manage enterprise assets. Powerful

modeling approaches require a large range of modeling artifacts to be able to cover the

entire scope of enterprise architecture. But, it is not always easy to know which modeling

technique to use. The most common question asked by Business and IT architects when

using modeling is: “where should I start from?”. And the usual answer is that there is no one

starting point; it has to be defined on a project basis. This statement usually adds more

confusion than it really brings any helps to modelers.

The Zachman Framework is a powerful answer to these questions: by providing a global

view of the multiple aspects of enterprise architecture, it offers a navigation tool that acts

both as starter and a compass for enterprise modelers. It provides a context in which

Business and IT architects can build a flexible, consistent information system, according to

the strategy of their enterprise.


The Zachman framework can successfully be used as a tool for defining project scope, for

checking project completeness, and as a learning tool for enterprise architecture.

Project scope definition

Most projects do not need to cover all enterprise analysis dimensions. The Zachman

framework helps business analysts and system architects organize their thoughts about

architecture and guides them to narrow the scope of the modeling artifacts required to carry

out their projects. It is then easier to tackle the “where to start” question and to define a

methodology path tailored to the project needs.

For instance, rows in the framework identify types of stakeholders and the associated detail

of information they require. Detailed SQL data types are not the right modeling artifact if

the objectives is to build a map of core business objects.

Checking project completeness

Another difficult question to answer is whether any significant element was left out of the

project scope. The Zachman Framework ensures all appropriate aspects are addressed or

used as a discussion support tool.

For instance, geographical location issues might be crucial for the project and must be

analyzed at all levels of the abstraction stack: business process, IT systems, distributed

objects.


A learning tool

As enterprise architects get more familiar with enterprise modeling, they discover the

benefits of having multiple dimensions for enterprise projects and how methodology steps

can used to move from one cell to another. Model driven approach can be better enforced

within project and increase their success factors.


Zachman Framework & MEGA

MEGA Suite™ is a comprehensive suite of modeling products covering the entire scope of

enterprise architecture. All products are natively integrated and operate with MEGA

Repository. MEGA Repository is the heart of MEGA software providing share, storage,

administration, reporting and security functions. MEGA Process provides capability to

capture, optimize and document business processes. Mega Architecture enables users to

produce functional views of their IT architecture in alignment with business process

definitions. MEGA Integration, .Mega Development and Mega Database are used to

produce IT system specifications for systems, workflows, components and databases in

order to efficiently drive project development. Thanks to MEGA Repository all products

automate accurate documentation and web site publishing to share information inside and

outside project teams and provide the backbone for enterprise architecture frameworks.


MEGA Suite™ provides, out of the box, a complete answer for 24 cells out of 30 listed in

the Zachman Framework. According to Zachman, supporting the framework is not about

providing the same kind of model with different level of detail for each cell:

“The Rows are different, that is, different models occur in every Row within any one Column. It is just like in classic building architecture...

“The models are RELATED to one another, but they are not the SAME model just in increasing levels of detail. ”

John Zachman

Each product of MEGA Suite MEGA Suite provides the appropriate set of models and the

relationships between each model for the different cells. This powerful interconnection

between key concepts increases the added value brought by the enterprise model.

A detail specification for each cell and model mapping is given at the end of this document:

MEGA Concepts mapping


MEGA Zachman Portal

MEGA Suite™ comes with an HTML service that acts as a Zachman Portal onto the

repository. For each Zachman cell, a mapping window is provided that describes the

concept used in MEGA, along with a query that selects the corresponding model objects in

the current repository.

Thereby, users can easily discover best modeling practices in MEGA with the standard

guidelines provided by the Zachman Framework.


The Zachman portal is implemented as simple HTML pages with very straightforward

scripting API invoking queries onto the repository. It can be used as a basis to create new

portals or to adapt the Zachman framework to enterprise specific requirements.

MEGA Concepts mapping

The following paragraphs provide a detailed mapping between Zachman cells and concept s

as utilized in MEGA.

ZZaacchhmmaann cceell ll

RRooww 11 –– CCoo lluumm nn 11

CCoonntt eexxtt uuaall // DDaattaa:: TT hhiinnggss IImmpp oorr ttaanntt ffoorr tthh ee bb uussiinn eess ss

CCoonncceepptt

mmaappppiinn gg

CCoonntt eennttss rr eess uulltt ii nngg ffrroomm ccoorr ee BBuussii nn eessss PPrroocceess ssee ss aa nndd ddeellii vveerr eedd ttoo EExxtteerr nnaall

EEnnttiitt iiee ss ((CCuusstt oommeerr ss))..

BBuussii nnee ssss CC llaass ss aa ssss oocciiaattee dd ttoo CC oo nnttee nnttss ddeellii vveerreedd bbyy BBuu ssii nnee ssss PPrroocceess ssee ss

PPrroodduucctt MMEEGGAA PPrr ooccee ssss

RRaattiioonnaa llee CCaappttuurr ee ee nntteerrpprr iiss ee mmaaii nn ddeell iivv eerraabbllee ss aa nndd tt hh eeiirr aa ssssoo cciiaatt eedd bbuu ssii nnee ssss oobbjj eecctt ss..


RRooww 11 –– CCoo lluummnn 22

LLiisstt ooff pprroocceesssseess tthhee bbuussiinneessss pp eerrffoorrmmss

CCoonncceepptt

mmaappppiinn gg

BBuussii nnee ssss PPrroocc eess ss::


RRaattiioonnaa llee IIddee nnttiiffyy tt hhee ee nntteerrpprr iissee mm aaiinn vv aall uuee cchh aaii nnss..

TThh eerree aarree uuss uuaallllyy aatt mmoosstt 33 oorr 55 ccoorree bbuussii nnee ssss pprroocc eessss eess ii nn aa nn ee nntteerrpprr iissee


ZZaacc hhmmaa nn cceellll RRooww 11 –– CCoo lluummnn 33

LLiisstt ooff lloo ccaatt ii oonn wwhheerree tthh ee bb uussii nn eess ss ooppeerraatteess

CCoonn ccee pptt

mmaappppiinngg

SSiitt ee:: AA ssiittee iiss tthhee ggee ooggrraapp hhiiccaall lloo ccaatt ii oonn ooff aa nn oorrggaann iizzaatt iioo nn


RRaattii oonn aallee IIddee nnttiiffyy tt hhee iimmpp aacctt ooff ggee ooggrraapp hhii ccaall ddii ssttrriibb uuttiioonn ii nn pprroocc eess ss aa nnaallyy ssiiss



LLiisstt ooff oorrggaanniizzaatt iioonnaa ll uunnii ttss

CCoonncceepptt

mmaappppiinn gg

EExxtteerrnn aall EE nnttiitt iiee ss:: OOrrgg--UUnn iitt ooff ttyyppee EExxtteerrnn aall

OOrrgg--UUnniitt wwiitt hh sstteerree oottyypp ee SSttrruuccttuurr ee,, MMaann aagg eerr


RRaattiioonnaa llee AAnnaallyyzz ee cc uusstt oommeerr sseeggmm ee nnttaatt ii oonn aacccc oorrddiinngg tt oo pprr oodduu cctt dd eell iivveerryy

IIddee nnttiiffyy mmaa iinn oorrggaa nniizzaatt ii oonn uu nniittss



LLiisstt ooff EEvveenn ttss ssii ggnniiff iiccaanntt ttoo tt hhee bbuuss iinneessss

CCoonncceepptt

mmaappppiinn gg

MMee ssssaa ggee ttrr iigg ggeerr ii nngg CCoorree BBuu ssii nnee ssss PPrroocceess ssee ss


RRaattiioonnaa llee UUnndd eerr ssttaa nndd hhooww aa nndd ww hhee nn tt hhee ee nnvv iirroonnmmee nntt iinntteerr aa cctt wwiitt hh tthhee ee nntteerr pprr iissee




LLiisstt ooff bbuuss iinneessss ggooaa llss//sstt rraatteeggiiee ss

CCoonncceepptt

mmaappppiinn gg

OObbjjeecctt iivvee aa ssss ooccii aattee dd ttoo gglloobbaall rr eeqquuiirr eemmeenntt ddii aaggrraammss

PPrroodduucctt AAllll PPrroo dduu ccttss

RRaattiioonnaa llee IIddee nnttiiffyy cc oorrppoorraatt ee oobbjj eecctt ii vveess aarr ee ddrr ii vveerr ss ff oorr bboott hh bbuu ssii nnee ssss aann dd IITT pprroojj eecctt ss

ZZaacchhmmaann cceell ll RRooww 22 –– CCoo lluummnn 11

SSeemmaanntt iicc MMooddeell

CCoonncceepptt

mmaappppiinn gg

PPaacckk aaggee DDaatt aa MMooddee llss aassssoo cciiaatteedd wwiitt hh BBuussii nn eessss PPrroocc eess ssee ss oorr BBuussii nneessss

FFuunn cctt ii oonnss

PPrroodduucctt MMEEGGAA DDaatt aabbaassee

RRaattiioonnaa llee DDeeff iinn ee tt hhee ddaattaa sscc oopp ee rr eeqquuiirr eedd ii nn tt hhee ccoo nntteexxtt ooff aa BBuussii nnee ssss PPrroocc eess ss oorr aa

BBuussii nnee ssss FFuu nnccttii oonn ..

BBuussii nnee ssss ddaattaa mmoodd eell ss ee nnaa bbllee dd aattaa rr ee sspp oonnssiibb iilliittyy mm aannaaggeemm eenntt ..

BBuussii nnee ssss oobbjj eecctt ss ccaa nn bbee rr ee uuss eedd aammoo nngg mmuulltt ii ppllee dd aattaa mmoo ddee llss



BBuussiinn eessss PPrroocceessss MMooddeell

CCoonncceepptt

mmaappppiinn gg

BBuussii nnee ssss PPrroocc eess ss DDeeffii nniitt iioo nn DDii aaggrraamm


RRaattiioonnaa llee DDeessccrr ii bbee bb uussiinn eess ss pprroocc eessss vvaa lluuee cchh aaii nnss ii nn tteerrmm ooff aacctt ii vviitt iieess aa nndd tt hheeiirr

sseeqq uuee nncciinn gg.. AAcctt iivv iitt iieess aarr ee sstt eepp ss iinn aa bbuussii nnee ssss pprroocc eessss aa nndd dd eeff iinn ee ww hhaatt iiss ttoo bbee

ddoonnee iinn tt hh ee pprrooccee ssss iinn ddee ppeenndd ee nnttllyy ooff aa nnyy oorrgg aann iizzaatt iioonnaall ccoonncc eerrnn..

TThhii ss ccoommmm oo nn dd eeff iinniitt iioo nn ii ss uu ssee dd aass aa rr eeffeerree nncc ee ffoorr aallll ssppeecc iiff iicc pprroo cceessss

iimmppll eemmeennttaatt iioonnss



BBuussiinn eessss LLoo ggii ssttiiccss SSyyssttee mm

CCoonncceepptt

mmaappppiinn gg

BBuussii nnee ssss PPrroocc eess ss // SSiitt ee


RRaattiioonnaa llee PPrroovv iidd ee aa mmaapp ooff ggeeooggrraapphhii ccaall ssiittee aanndd dd eessccrr ii bbee ggeeoo ggrraapphhiicc aall ddeepp llooyymm eenntt

ffoorr bbuuss iinneess ss pprroo ccee ssss eess..




OOrrggaann iizzaattiioonn cchhaarrtt::

rroollee,, sskk iill ll ss eettss,, sseeccuurr iittyy iissssuueess

CCoonncceepptt

mmaappppiinn gg

OOrrggaannii zzaatt ii oonn aall cc hhaarr tt

PPrroocc eedduurr ee


RRaattiioonnaa llee PPrroovv iidd ee aann oovveerrvv iiee ww ooff tthhee ee nntteerrpprr iiss ee ssttrruucctt uurree.. OOrrgg--cchhaarr ttss iinn ddiiccaattee tt hhee

hhiieerr aarr cchhyy ooff OOrrgg--UUnniitt ss iinn tt hhee ee nntt eerrpprr iissee,, sspp eecciiff iiee ss tthh ee PPeerr ssoo nnss tthhaatt ppll aayy tthhee

rroollee ooff tthh eess ee OOrrgg--UUnniitt ss,, aa nndd ss hhoo wwss aatt wwhhiicc hh SSiitt ee tt hhee OOrrgg--UUnn iitt ii ss ll ooccaatt eedd

DDeessccrr ii bbee tt hhee iimmppll eemmee nnttaatt iioo nn ooff aa llll oorr ppaarr tt ooff aa BBuussii nnee ssss PPrroocceess ss ff rroomm aann

oorrggaann iizzaatt iioo nn vviiee wwpp ooiinntt ..



MMaasstteerr SScchheedduu llee

CCoonncceepptt

mmaappppiinn gg

CCoollll aabboorraatt iioo nn dd eeff ii nniittii oo nn

PPrroodduucctt MMEEGGAA PPrr ooccee ssss,, MMEEGGAA AArrcc hhiitt eecctt uurree oorr MMEEGGAA IInntteeggrraatt iioonn

RRaattiioonnaa llee RReell aattee bbuu ssii nneessss eevv eennttss tt oo tthh eeiirr bbuuss iinn eess ss rree ssuu llttss ii nncc lluuddii nngg ttiimm iinn gg aa nndd

sseeqq uuee nncciinn gg rruulleess




BBuussiinn eessss PPllaann

CCoonncceepptt

mmaappppiinn gg

OObbjjeecctt iivveess aann dd cc oonnttrrii bbuutt iinngg PPrroojj eecctt ss

PPrroodduucctt AAllll MM EEGGAA pprroodduucctt ss

RRaattiioonnaa llee DDeeff iinn ee tthhee ppllaann,, iinn tt eerrmm ooff pprroojjee cctt ,, ffoorr rreeaa lliizz aattii oonn ooff cc oorrppoorraatt ee oobbjjee cctt ii vvee ss


LLooggiiccaa ll DDaattaa MMooddee ll

CCoonncceepptt

mmaappppiinn gg

DDaattaa MMoodd eell ss aass ssoo cciiaatteedd tt oo DDaatt aabbaassee ss

PPrroodduucctt MMEEGGAA DDaatt aabbaassee

RRaattiioonnaa llee DDeeff iinn ee tthhee rruu lleess ffoorr ddaattaa mmaa nnaa ggeemmee nntt aanndd ddaattaa ssttoorraaggee..


AApppplliiccaatt iioonn AArrcchhii tteeccttuurr ee

CCoonncceepptt

mmaappppiinn gg

AAppppll iiccaatt iioo nn AArrcchh iittee ccttuurree DDiiaaggrraamm

PPrroodduucctt MMEEGGAA AArrcc hhiittee ccttuurree

RRaattiioonnaa llee DDeessccrr ii bbee tthh ee ssooff ttwwaarree ee nn vviirroo nnmmeenntt ff oorr aann aappppll iiccaatt iioo nn,, aa ssiitt ee,, aann OOrrgg--UU nniitt ,,

oorr ffoorr tthhee ee nnttiirree ccoommppaa nnyy ..




DDiissttrr iibbuutt eedd SSyysstt eemm AArrcchh iitteecctt uurree

CCoonncceepptt

mmaappppiinn gg

TTeecc hh nniiccaall AArrcchhiitt eeccttuurr ee DDiiaaggrraamm

PPrroodduucctt MMEEGGAA AArrcc hhiittee ccttuurree

RRaattiioonnaa llee DDeessccrr ii bbee EE nntteerrpprr ii ssee AArrcc hhiitt eeccttuurree ddeeppllooyymm eenntt ee xxpprree ssss eedd ii nn tteerrmm ooff ssiittee,,

sseerrvv eerr ss,, nneett wwoorrkk,, nnoo ddee ss,, .. .. ..



HHuummaann IInntteerrffaaccee AArrcchh iitteeccttuurree

CCoonncceepptt

mmaappppiinn gg

CCrroossss rr eeff eerree nnccee bb eettwweeee nn bb uuss iinn eess ss ttaa sskkss aann dd ssyysstteemm rreessoo uurrccee ss

PPrroodduucctt MMEEGGAA PPrr ooccee ssss aann dd MMEEGGAA AArrcc hhiitt eeccttuurree

RRaattiioonnaa llee IIddee nnttiiffyy ii nntt eerr aacctt ii oonn ppoo iinntt ss bbeett wwee eenn OOrrgg--UU nniittss aa nndd ssyysstteemm rr eess oouurrcc eess



PPrroocceessssiinngg SSttrruucc ttuurree

CCoonncceepptt

mmaappppiinn gg

BBuussii nnee ssss OO bbjjeecctt SStt aattee MMaa cchhiinn ee

PPrroodduucctt MMEEGGAA PPrr ooccee ssss aann dd MMEEGGAA DDee vv eelloo ppmmeenntt

RRaattiioonnaa llee DDeeff iinn ee tthh ee ttrr aann ssiitt ii oonn ccyycc llee ffoorr bbuussii nnee ssss oo bbjjee ccttss ii nn rr eellaatt iioo nnsshhii pp wwiitt hh bbuussii nnee ssss

eevveenntt ss




BBuussiinn eessss RRuu llee MMooddee ll

CCoonncceepptt

mmaappppiinn gg

RReeqq uuiirr eemmee nnttss aann dd tthheeiirr cc oonnssttrr aaii nneedd oobbjjeecctt ss

PPrroodduucctt AAllll MM EEGGAA PPrroodduu ccttss

RRaattiioonnaa llee MMoodd eell eenntt eerrpprr iiss ee bb uussiinn eess ss rruullee ss ii nn tteerrmm ooff tthh eeiirr ii nnttee nnttss

((oobbjjee cctt ii vvee ss//rree qquuiirr eemmee nnttss)) aann dd tthh ee mmee aannss ooff hhaa vvii nngg tthhee rr ee ssuu lltt ii nngg cc oonn ssttrraaii nnttss

(( ccoonn ssttrr aaii nnee dd bbuussii nn eessss pprroo cceessss // rr eeaa lliizz iinn gg pprroo cceedduurree)) ..



PPhhyyssiiccaa ll DDaa ttaa MMooddeell

CCoonncceepptt

mmaappppiinn gg

RReell aatt iioo nnaa ll MM oodd eell ss aa nndd XX MMLL mmoo ddee llss

PPrroodduucctt MMEEGGAA DDaatt aabbaassee oorr MMEEGGAA II nntteeggrraatt iioo nn

RRaattiioonnaa llee MMoodd eell tthh ee pp hhyyssii ccaall rreepprree sseennttaatt iioo nn ooff ee nntteerrpprr ii ssee bbuu ssiinnee ssss ddaattaa



SSyysstteemm DDeess iiggnn

CCoonncceepptt

mmaappppiinn gg

SSyysstteemm AArrcchh iitteecctt uurree DD iiaaggrraamm

WWoorrkkff llooww ddiiaa ggrraammss

CCoommppoo nneenntt ddiiaaggrraammss

PPrroodduucctt MMEEGGAA II nntt eeggrraatt ii oonn oorr MMEEGGAA DDeevvee llooppmmee nntt

RRaattiioonnaa llee DDeessii ggnn eenntteerrpprrii ssee ssyysstt eemmss aann dd ccoommppoo nn eenntt ss




TTeecchhnnoollooggyy SSyyssttee mm AArrcchhii tteeccttuurree

CCoonncceepptt

mmaappppiinn gg

DDeettaaii llee dd TT eecc hhnn iiccaa ll AArrcchh iitteeccttuurree DDiiaaggrraamm ss

CCoommppoo nneenntt DDeepp llooyymmeenntt DDiiaaggrraammss

PPrroodduucctt MMEEGGAA AArrcc hhiittee ccttuurree oorr MM EEGGAA DDee vvee llooppmmee nntt

RRaattiioonnaa llee DDeessccrr ii bbee tt hh ee eenntt eerrpprriiss ee pp hhyyss iiccaa ll ttee cchh nnoollooggyy eennvviirr oonnmmee nntt sshhoo wwii nngg tt hhee aacctt uuaall

hhaarrdd wwaarree aann dd ssyysstt eemm ssooff ttwwaarree aatt tthh ee nn ooddeess aanndd ll iinn eess ooff tthh eeiirr ssyysstteemm ss..



PPrreesseennttaattiioonn AArrcchhii tteeccttuurr ee

CCoonncceepptt

mmaappppiinn gg

UUsseerr II nntteerr ffaa cceess aa nndd UUsseerr II nntt eerr ffaaccee DD iiaaggrraamm ss

PPrroodduucctt MMEEGGAA II nntt eeggrraatt ii oonn

RRaattiioonnaa llee SSppeecciiffyy eerrggoo nnoommii cc rr eeqq uuiirr eemmee nntt aanndd pprreessee nnttaattiioo nn ffoorrmmaatt



DDaattaa DDeeff iinnii ttiioonn

CCoonncceepptt

mmaappppiinn gg

GGeenn eerraattee dd SSQQLL ssccrr iipptt oorr XXMMLL sscchheemm aa

PPrroodduucctt MMEEGGAA DDaatt aabbaassee aann dd MMEEGGAA II nntteeggrraatt ii oonn

RRaattiioonnaa llee PPrroovv iidd ee aauuttoommaattiicc aallllyy ddaattaa ddeeff iinniitt iioo nn iimmmmeeddii aatteellyy aa vvaaii llaabb llee ffoorr ddaattaa bbaa ssee

mmaannaa ggeerrss aann dd dd eevv eell oopp eerr ss..




PPrrooggrraammss

CCoonncceepptt

mmaappppiinn gg

GGeenn eerraattee dd ss oouurrcc ee cc oodd ee oorr WWMMLL ww oorrkkfflloo ww dd eeff ii nniitt ii oonn

PPrroodduucctt MMEEGGAA II nntt eeggrraatt ii oonn aann dd MM EEGGAA DDee vv eellooppmmee nntt

RRaattiioonnaa llee PPrroovv iidd ee aauutt oommaattii ccaallllyy ssoouurrcc ee ccoo ddee aann dd wwoorrkkff ll ooww ee xxeeccuuttaa bbll ee ssccrr ii ppttss ttoo

ddeevveell ooppmmee nntt ttee aammss


Annexes

Annex A -Customization samples

Treasury Enterprise Architecture


Healthcare Informatics Framework


Annex B - Usual definition of the Zachman Framework cells

The rows represent various abstraction levels typically involved in the systems development

process, while columns represent different perspectives also involved in the cycle.

1. Scope (Ballpark view): Definition of the enterprise's direction and business purpose. This is necessary to establish the context for any system development effort.

2. Model of the business (Owner's view): This defines — in business terms — the nature of the business, including its structure, functions, organization, and so forth.

3. Model of the information system (Architect's view): This defines the business described in step 2, but in more rigorous information terms. Where row two described business functions, for example, as perceived by the people performing them, row three describes them specifically as transformations of data. Where row two described all the things of interest to the enterprise, row three describes those things about which the organization wishes to collect and maintain information, and begins to describe that information.

4. Technology model (Designer's view): This describes how technology may be used to address the information processing needs identified in the previous rows. Here relational databases are chosen over network ones (or vice versa), kinds of languages are selected and program structures are defined, user interfaces are described, and so forth.

5. Detailed representations (Builder's view): Here a particular language is chosen, and the program listings, database specifications, networks, and so forth are all produced.

6. Functioning system: Finally, a system is implemented and made part of an organization.

The columns in the Zachman framework represent different areas of interest for each perspective. The columns describe the dimensions of the systems development effort. As shown in Figure 2, these are:

1. Data: Each of the rows in this column address understanding of and dealing with an enterprise's data. This begins in row one with a list of the things that concern the company and affect its direction and purpose. Row two, is a contiguous model of the things seen by the participants in the business. Many-to-many and n-ary relationships may be present; reflecting the way the business views them. Also, relationships may be shown which themselves


have attributes. Row three provides more of an information-based perspective, resolving many -to-many and n-ary relationships, along with relationships containing their own attributes. Indeed, attributes are more exhaustively defined, and unique identifiers are specified. Entities are generalized to more closely reflect the underlying structure of the business and its relationships. In row four, entities are converted to table definitions, object classes, hi erarchy segments, or whatever is appropriate for the kind of data base management system to be used. This is tantamount to creating the data definition language statements. In row five, the tables are actually implemented on physical disk drives, using the underlying organization of the database management system. This is where table spaces are defined, disk packs are allocated, and so forth. The actual database itself is created and initial data are converted and loaded for row six.

2. Function: The rows in the function column describe the process of translating the mission of the enterprise into successively more detailed definitions of its operations. Where row one is a list of the kinds of activities the enterprise conducts, row two describes these activities in a contiguous model. Row three portrays them in terms of data transforming processes, described exclusively in terms of the conversion of input data into output data. The technology model in row four then converts these data conversion processes into the definition of program modules and how they interact with each other. Pseudo-code is produced here. Row five then converts these into source and object code. Row six is where the code is linked and converted to executable programs. Note that in the object-oriented approach, functions and data tend to be addressed together.

3. Network: This column is concerned with the geographical distribution of the enterprise's activities. At the strategic level (row one), this is simply a listing of the places where the enterprise does business. At row two, this becomes a more detailed communications chart, describing how the various locations interact with each other. Row three produces the architecture for data distribution, itemizing what information is created where and where it is to be used. In row four, this distribution is translated into the kinds of computer facilities that are required in each location, and in row five, these facilities requirements are translated into specification of particular computers, protocols, communications facilities, and the like. Row six describes the implemented communications facilities.

4. People: The fourth column describes who is involved in the business and in the introduction of new technology. The row one model of people is a simple list of the organizational units and each unit's mission. In row two, this list is fleshed out into a full organization chart, linked to the function column. Here also, requirements for security are described in general terms. In row


three, the potential interaction between people and technology begins to be specified, specifically in terms of who needs what information to do his job. What roles do each play and what data are necessary for those roles? Along with this are specific definitions of security requirements, in terms of who (which role) is permitted access to what. In row four, the actual interface between each person and the technology is designed. In this row, issues of interface graphics, navigation paths, security rules and presentation style are addressed. In row five, this design is converted into the outward appearance of each program, as well as the definitions of access permissions in terms of specific tables and/or columns each user can have access to. In row six, you have trained people, using the new system.

5. Time: The fifth column describes the effects of time on the enterprise. It is difficult to describe or address this column in isolation from the others, especially column two. At the strategic (row one) level, this is a description of the business cycle and overall business events. In the detailed model of the business (row two), the time column defines when functions are to happen and under what circumstances. Row three defines the business events, which cause specific data transformations and entity state changes to take place. In the technology model (row four), the events become program triggers and messages, and the information processing responses are designed in detail. In row five, these designs become specific programs. In row six business events are correctly responded to by the system.

6. Motivation: As Mr. Zachman describes it; this is concerned with the translation of business goals and strategies into specific ends and means. This can be expanded to include the entire set of constraints that apply to an enterprise's efforts. In row one, the enterprise identifies its goals and strategies in general, common language terms. In row two, these are translated into the specific rules and constraints that apply to an enterprise's operation. In row three, business rules may be expressed in terms of information that is and is not permitted to exist. This includes constraints on the creation of rows in a database as well as on the updating of specific values. In row four, these business rules will be converted to program design elements, and in row five they will become specific programs. In row six, business rules are enforced.

mega & the zachman framework - e-dnrs · pdf filemega & zachman page 3 what is the...

Documents