Enterprise Architecture using the Zachman Framework A Model-Driven Approach

1
Enterprise Architectureusing the Zachman
FrameworkA Model-Driven Approach

• Ali Fatolahi (Presenter)
• Stéphane S. Somé and Timothoy C. Lethbridge
• School of Information Technology and Engineering
• University of Ottawa
• May 2007, IRMA 2007 Conference, Vancouver

2
Agenda

• Enterprise Architecture (EA)
• The Zachman Framework (ZF)
• Model-Driven Architecture (MDA)
• Problem Statement
• Applying MDA to ZF
• Discussion Conclusion

3
Enterprise Architecture (EA)

• A Set of Models and Documents
• For the entire business all systems
• Alignment of IT with Business
• Strategy, Process, Regulations,
• EA governs Systems Lifecycle
• Planning, Development, Maintenance
• A collection of tools methods

4
Enterprise Architecture (Contd.)

• Motivations
• Reduce maintenance costs
• Ensure systems in accordance business
• Guarantee an integrated IT environment
• consistent, accurate, correct
• Prevent redundancy
• Interoperability, Flexibility, ilities!

5
The Zachman Framework (ZF)

• EA is like a jungle of models
• Maps are required to not get lost!
• ZF is such a map for this jungle
• One of the origins of EA
• The most used framework for EA and related arenas

FOR MORE INFO...
EA Survey Trends 2005 Results www.enterprise-arc
hitecture.info/Images/EA Survey/Enterprise
Architecture Survey 2005 IFEAD v10.pdf
6
The Zachman Framework
Data What
Function How
Network where
People Who
Time When
Motivation Why
Scope (Contextual) Planner
Subject Scope Content (Contextual) Stakeholder
Planner
Business (Conceptual) Owner
Subject Business Content (Conceptual) Stakeholde
r Owner
Subject System Content (Logical) Stakeholder
Designer
System (Logical) Designer
Subject Technology Content (Physical) Stakeholde
r Builder
Technology (Physical) Builder
Components (Detailed) Sub-Contractor
Subject Components Content (Detailed) Stakeholde
r Sub-Contractor
Enterprise
Subject Real Working Enterprise
7
Challenges of using ZF

• Engineering and reengineering perspectives from
  each other
• Different languages and standards coming from
  different sources
• Related Research existing on
• Applying UML to ZF
• Assigning MDA-based models to ZF

8
Our Approach

• MDA as a modeling source for ZF
• Strong in model transformation
• Well-Defined family of modeling tools, standards
  and methods
• Similar approaches to
• Meta-modeling
• Separation of concerns
• Popularity

9
Model-Driven Architecture (MDA)

• Models are assets not cost
• More modeling, less coding
• (Automatic) Model Transformation
• From requirements to code
• Not so fast!
• Model reusability
• Design-time interoperability

10
MDA (Contd.)
Computation-Independent Modeling (CIM)
Platform-Independent Modeling (PIM)
Platform-Specific Modeling (PSM)
11
MDA vs. ZF Separation of Concerns
FOR MORE INFO...
http//www.omg.org/mda/mda_files/09-03-WP_Mapping_
MDA_to_Zachman_Framework1.pdf
12
MDA vs. ZF Modeling Coverage
FOR MORE INFO...
http//www.omg.org/mda/mda_files/09-03-WP_Mapping_
MDA_to_Zachman_Framework1.pdf
13
Meta-Object Facility (MOF)

• Meta-Data Language of MDA
• A means of defining new languages
• Very simple but strong
• Two levels of languages
• MOF-based languages UML, CWM,
• UML Profiles
• UML Notation is usually used

14
Conceptual Graphs (CG)

• A Conceptual Graph is a set of
• Concepts
• Relations
• Example CG A cat is on a mat.

Concept 2
Relation
Concept 1
Mat
Cat
On
FOR MORE INFO...
http//conceptualgraphs.org/
15
Conceptual Graphs vs. MOF

• CG
• Meta-Data language of ZF
• Integrity of the ZF
• Could MDA preserves the integrity?
• Yes, if MOF could define CGs
• Could an MDA be seen as ZF-based EA?
• Yes, if CGs could define MOF

16
MOF Meta-Modelfor CG
17
Synthesis of a CGwith MOF
18
CG Meta-Model for MOF
19
Meta-Modeling in ZF
Repository Framework
Enterprise Engineering Framework
Enterprise Framework
Product Framework
20
Meta-Modeling in MDA

• M3 Meta-Meta-Model
• MOF
• M2 Meta-Model
• UML, CWM, UML Profiles,
• M1 User Model
• Instances of UML,
• M0 Runtime Model
• Runtime Objects

21
MDA vs. ZFMeta-Modeling
Repository Framework
M3
uses
Enterprise Engineering Framework
M2
instantiates
supplies
Enterprise Framework
realizes
Product Framework
engineers
M1
produces
M0
22
Discussion

• Platform or Technology
• ZF
• Technology-Independence
• Equal to Platform-Independence
• MDA
• Platform-independence
• Is not equal to Technology-Independence
• ZF is recursive but not MDA

23
Discussion (Contd.)

• In ZF
• Technology Independent
• DB2 and Struts Independent
• In MDA
• Depends on Platform
• If PlatformDB2
• Platform-Independent
• DB2-Independent
• Not Struts-Independent

Technology Independent Area
DB2
Struts
24
Future Work

• Transformation Functions
• Input High-Level Requirements
• e.g. Use Case
• Output Low-Level Design Models
• e.g. Executable State-Machine
• PIM to PSM Transformation
• ZF Coverage
• Row 2 (and/or 3) to Row 3 (and/or 4)

25
Thank you
?
FOR MORE INFO...
Read my paper in the proceedings of the IRMA 2007
Conference in Vancouver!