P. 1
Enterprise Architecture Frameworks

Enterprise Architecture Frameworks

|Views: 181|Likes:
Published by Stephen Lahanas
This presentation provides an overview of Enterprise Architecture Frameworks. It is presented by the Semantech Inc. Enterprise Architecture Center of Excellence. The purpose of the briefing is to provide a better understanding of how Frameworks are used in the practice of EA.
This presentation provides an overview of Enterprise Architecture Frameworks. It is presented by the Semantech Inc. Enterprise Architecture Center of Excellence. The purpose of the briefing is to provide a better understanding of how Frameworks are used in the practice of EA.

More info:

Published by: Stephen Lahanas on Jun 24, 2011
Copyright:Traditional Copyright: All rights reserved

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PPT or read online from Scribd
See more
See less

10/25/2014

original

Enterprise Architecture

Center of Excellence

Presented by Stephen Lahanas

The Practice of EA: Understanding Architecture Frameworks
Copyright 2011, Semantech Inc., All Rights Reserved

Introduction
‡ The presentation series, ³EA Practice´ is dedicated to highlighting some of the key aspects of the evolving IT practice of Enterprise Architecture. ‡ This briefing ± ³Understanding Frameworks´ explores what frameworks are and how they are related to the practice of architecture as well as to stakeholder expectations for architecture. ‡ These briefings are presented by the Semantech Web Servers are one Inc. Enterprise dangerousthing, Nuclear Reactors are Architecture Center of Excellence a bit more ± there are systems which absolutely must to FAIL. which is dedicated not making EA actionable«
Copyright 2011, Semantech Inc.

2

IT Complexity is the most Disruptive trend of all ± and it will only get worse«
Web Servers are one thing, Nuclear Reactors are a bit more dangerous ± there are systems which absolutely must not FAIL.

Copyright 2011, Semantech Inc.

3

The Importance of Architecture
‡ Not everyone practices Enterprise Architecture, not everyone agrees what it is and more importantly not everyone fully appreciates its relevance. ‡ Enterprise Architecture is Meta-Architecture; it encompasses all possible architectures present within an enterprise; Application, Infrastructure, Data, SOA, Cloud, Security and many more. ‡ Architecture is both medium and message ± it provides an organizational framework and helps communicate it. ‡ Architecture is the most important tool we have to manage technology related disruption and complexity in today¶s enterprise.
Copyright 2011, Semantech Inc.

4

Enterprise Architecture is more than a Blueprint ± it is the sum total of all elements necessary Web Servers are one thing, Nuclear Reactors a to actualize are a bit more dangerous ± there are systems which absolutely must not FAIL. capability.
Copyright 2011, Semantech Inc.

5

What is Architecture ?
‡ Architecture is Design. ‡ Architecture is Conceptual Visualization. ‡ Architecture is the attempt to quantify existing and future capabilities. ‡ Architecture is a communication medium for bringing together the stakeholders who rely on that capability. ‡ Architecture is complex; there is more than one type of architecture, these are often symbiotic in nature. ‡ A typical enterprise is a system of systems, represented by an architecture of architectures which is generally referred to as Enterprise Architecture. Web Servers are one thing, ‡ Architecture is a Evolutionary,Nuclear Reactors are as we do. it changes just a bit more dangerous ± there are systems which ‡ Architecture is data, itnot FAIL. automated. absolutely must can be
Copyright 2011, Semantech Inc.

6

What is EA ?
‡ Enterprise Architecture represents the top level of enterprise IT capabilities and systems representations. ‡ Enterprise Architecture can be depicted through high level Reference (FEA) or Domain (UML) or Data models or can be illustrated in depth using DoDAF, TOGAF or Zachman Framework artifacts or products. ‡ Not all Enterprise Architecture is depicted using EA Web Servers are one Architecture is often Frameworks. Enterprisething, Nuclear Reactors are viewed a bit more dangerous ± there are systems which as a mandated lifecycle management tool rather than absolutely must not FAIL. a system design approach, but it is in fact both.
Copyright 2011, Semantech Inc.

7

EA - The Big Picture

Web Servers are one thing, Nuclear Reactors are a bit more dangerous ± there are systems which absolutely must not FAIL.

Copyright 2011, Semantech Inc.

8

Talking about Meta-Architecture
‡ The previous diagram illustrates an important point we made at the beginning of the presentation. Enterprise Architecture is Meta-Architecture. ‡ Why is this significant? The main reason is this ± if your architectures aren¶t integrated ± what is the likelihood your systems will be properly integrated ? ‡ Meta-Architecture represents the deliberate attempt to reconcile architecture perspectives and the Web Servers are one thing, Nuclear Reactors are unique requirements of±many systems which must a bit more dangerous there are systems which co-exist absolutely must not FAIL. in a unified enterprise environment.
Copyright 2011, Semantech Inc.

9

Frameworks & Meta-Architecture
DoDAF is an EA Framework example EA & lifecycle support support systems design

EA Frameworks support Lifecycle Management

Web Servers are one thing, Nuclear Reactors are a bit more dangerous ± there are systems which absolutely must not FAIL.

Copyright 2011, Semantech Inc.

10

What is a Framework ?
‡ Enterprise Architecture Frameworks are a deliberate attempt to provide a mechanism for managing MetaArchitecture. ‡ Frameworks allow architects to both describe and illustrate system and environmental characteristics within any given enterprise, parts thereof or even a conglomeration of enterprises. ‡ Frameworks are generally thought of as collections of views or perspectives within a shared µgeneric¶ Web Servers are one thing, Nuclear Reactors are enterprisebit more dangerous ± there are systems whichoften a taxonomy. That core taxonomy is absolutely must not FAIL. segregated by capability or technology type.
Copyright 2011, Semantech Inc.

11

A single house is much like a single system ± it has various types of architecture within it and it exists within ever-larger ecosystems«
Web Servers are one thing, Nuclear Reactors are a bit more dangerous ± there are systems which absolutely must not FAIL.

Copyright 2011, Semantech Inc.

12

Frameworks are Metamodels
‡ Enterprise Architecture Frameworks are the most familiar parts of EA, yet many people do not realize that they are essentially, flexible data models. ‡ EA Frameworks are built upon metamodels; for example DoDAF is built atop CADM. The metamodel allows for variations in expression through customization of the DoDAF ³Views.´ ‡ Metamodel integration makes it possible to map data back and forth across any Framework. There are several products that now automate such mappings. ‡
Web Servers are one thing, Nuclear Reactors are a bit Metamodelsmore dangerous ± there are systemsprovide in general are attempts to which absolutely must not FAIL.

outlines for capabilities and relationships ± they can evolve.
13

Copyright 2011, Semantech Inc.

An Example Metamodel

Part of theWeb Servers are one thing, Nuclear Reactors are CADM a bit more dangerous ± there are systems which Metamodel for DoDAF not FAIL. absolutely must 1.5
Copyright 2011, Semantech Inc.

14

Framework Example: DoDAF
‡ DoDAF is the Department of Defense Architecture Framework. DoDAF evolved from several modeling approaches including C4ISR and IDEF. ‡ DoDAF products are separated into ³Views.´ Systems Operational and Technical views ± this maps to C4ISR and the FEAF. There are numerous products per each view and there are several more views. ‡ The latest version of DoDAF is 2.0, but many organizations still use version 1.5. The main difference between Web Servers are one the shift in focus from the versions is thing, Nuclear Reactors are a µproducts¶ bit more dangerous ±in 2.0, to facilitate automation to datamust not FAIL. are systems which models there absolutely and integration of architectures.
Copyright 2011, Semantech Inc.

15

Meta-Model Flexibility

Even within the DoDAF standard versions, there is a great deal of flexibility on Web Servers are one thing, Nuclear Reactors are how to exploit the products are systems which a bit more dangerous ± there absolutely must not FAIL. or models«
Copyright 2011, Semantech Inc.

16

Framework Example: Zachman
The Zachman Framework, originally developed for IBM, is perhaps the oldest of the commonly used EA frameworks and is more often used in commercial IT. The differences between the major frameworks are not as significant as they seem ± all mirror past and current IT practice well.

Web Servers are one thing, Nuclear Reactors are a bit more dangerous ± there are systems which absolutely must not FAIL.

Copyright 2011, Semantech Inc.

17

Framework Example: ToGAF

ToGAF is requirements focused ± this is an important differentiation from other frameworks and has Web Servers are one thing, Nuclear Reactors are significant automation implications.
a bit more dangerous ± there are systems which absolutely must not FAIL.

Copyright 2011, Semantech Inc.

18

Not all Frameworks are recognized as Enterprise Architecture frameworks in the formal sense. It is important to recognize the Practice of Enterprise Architecture is itself still evolving.
Web Servers are one thing, Nuclear Reactors are a bit more dangerous ± there are systems which absolutely must not FAIL.

Copyright 2011, Semantech Inc.

19

Framework Example: ITIL
ITIL is the Information Technology Infrastructure Library. ITIL is a taxonomy; it is also a collection of IT processes. ITIL is not a metamodel used for further EA development, rather it is a reference point for automation and process management. ITIL processes have become an Web Servers are one for industry standard template thing, Nuclear Reactors are a bit more dangerous ± there are systems which a variety ofabsolutely must not FAIL. IT security solutions.
Copyright 2011, Semantech Inc.

20

Frameworks are Semantics

All Metamodels are also semantic models. The most effective way to integrate EA with the rest of the enterprise is by use of semantic models.

Web Servers are one thing, Nuclear Reactors are a bit more dangerous ± there are systems which absolutely must not FAIL.

Copyright 2011, Semantech Inc.

21

Semantic Integration
‡ Enterprise Architecture is a key element of any Enterprise Integration initiative. If the EA is developed in concert with a Semantic Framework it is easier to align program management as well as follow-on solution / implementation designs. ‡ This approach is referred to as Semantic Integration. This represents the future of much of IT ± primarily because it enables us to automate much more of Web Servers are one thing, Nuclear Reactors are and the Lifecycle (both the development a bit more dangerous of an enterprise. management portions) ± there are systems which
absolutely must not FAIL.
Copyright 2011, Semantech Inc.

22

SOA Architecture

Web Servers are one thing, Nuclear Reactors are a bit more dangerous ± there are systems which absolutely must not FAIL.

Copyright 2011, Semantech Inc.

23

SOA & Cloud Architecture
‡ Services Oriented Architecture and the rise of Cloud Architecture represents an interesting situation for the practice of Enterprise Architecture in that these solution architecture approaches deliberately attempt to build in aspects of enterprise integration or meta-architecture. ‡ Some might argue that this would obviate the need for Enterprise Architecture, but in fact the reverse is true. If one is deliberately architecting a solution for the whole enterprise ± it absolutely critical that all aspects of that architecture Servers are one thing, Nuclear Reactors are are thought through and documented. Very Web a solutions (including are systems Cloud few if any bit more dangerous ± thereall SOA & which absolutely must not solutions) are ready µoutFAIL.the box¶ to deploy. of
Copyright 2011, Semantech Inc.

24

Future EA Presentations
‡ Many of the topics we¶ve introduced here are extremely complex and cannot be properly introduced within the context of this overview presentation. ‡ We will be presenting a number of these topics within their own presentations, including: ‡ ‡ ‡ ‡ ‡ ‡ An Introduction to DoDAF 2.0 An Introduction to ToGAF Understanding ITIL An Introduction to Zachman SOA, The Cloud & thing, Nuclear Reactors are Web Servers are one Enterprise Architecture a bit more dangerous ± there Semantic Integration Enterprise Architecture &are systems which
absolutely must not FAIL.
25

Copyright 2011, Semantech Inc.

As Complexity increases ± the ingenuity needed to master it must continuously improve. Our thing, Nuclear Reactors are Web Servers are onearchitecture strategies will play a bit more dangerous ± there are systems which an enormous role in determining whether absolutely must not FAIL. we¶re successful.
Copyright 2011, Semantech Inc.

26

Conclusion
‡ Enterprise Architecture is more than any one architecture specialty ± it is the synergistic combination of them all. ‡ Architecture Frameworks are a symbolic framework for documenting and illustrating both characteristics and complex relationships in system of systems environments. ‡ Frameworks are models of reality and frameworks are still evolving as is the practice of Enterprise Architecture.
Copyright 2011, Semantech Inc.

27

About Semantech Inc.
‡ Semantech Inc. is an IT solutions provider founded in 2007. Our company is located in the Dayton, Ohio metro area. Since our inception we have supported clients in a more than half a dozen industries nationwide. ‡ Our company represents a unique approach ± we¶re not offering just IT or Management Consulting. We specialize in facilitating complex organizational Transformations. Semantech was founded to facilitate change«
Copyright 2011, Semantech Inc.

28

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->