Enterprise Architecture Frameworks

22,419 views
23,048 views

Published on

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.

Published in: Technology, Business
2 Comments
31 Likes
Statistics
Notes
No Downloads
Views
Total views
22,419
On SlideShare
0
From Embeds
0
Number of Embeds
6,465
Actions
Shares
0
Downloads
0
Comments
2
Likes
31
Embeds 0
No embeds

No notes for slide

Enterprise Architecture Frameworks

  1. 2. Introduction Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. <ul><li>The presentation series, “ EA Practice ” is dedicated to highlighting some of the key aspects of the evolving IT practice of Enterprise Architecture. </li></ul><ul><li>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. </li></ul><ul><li>These briefings are presented by the Semantech Inc. Enterprise Architecture Center of Excellence which is dedicated to making EA actionable… </li></ul>
  2. 3. Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. IT Complexity is the most Disruptive trend of all – and it will only get worse…
  3. 4. The Importance of Architecture <ul><li>Not everyone practices Enterprise Architecture, not everyone agrees what it is and more importantly not everyone fully appreciates its relevance. </li></ul><ul><li>Enterprise Architecture is Meta-Architecture; it encompasses all possible architectures present within an enterprise; Application, Infrastructure, Data, SOA, Cloud, Security and many more. </li></ul><ul><li>Architecture is both medium and message – it provides an organizational framework and helps communicate it. </li></ul><ul><li>Architecture is the most important tool we have to manage technology related disruption and complexity in today’s enterprise. </li></ul>
  4. 5. Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. Enterprise Architecture is more than a Blueprint – it is the sum total of all elements necessary to actualize a capability.
  5. 6. What is Architecture ? Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. <ul><li>Architecture is Design. </li></ul><ul><li>Architecture is Conceptual Visualization. </li></ul><ul><li>Architecture is the attempt to quantify existing and future capabilities. </li></ul><ul><li>Architecture is a communication medium for bringing together the stakeholders who rely on that capability. </li></ul><ul><li>Architecture is complex; there is more than one type of architecture, these are often symbiotic in nature. </li></ul><ul><li>A typical enterprise is a system of systems, represented by an architecture of architectures which is generally referred to as Enterprise Architecture. </li></ul><ul><li>Architecture is a Evolutionary, it changes just as we do. </li></ul><ul><li>Architecture is data, it can be automated. </li></ul>
  6. 7. What is EA ? Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. <ul><li>Enterprise Architecture represents the top level of enterprise IT capabilities and systems representations. </li></ul><ul><li>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. </li></ul><ul><li>Not all Enterprise Architecture is depicted using EA Frameworks. Enterprise Architecture is often viewed as a mandated lifecycle management tool rather than a system design approach, but it is in fact both. </li></ul>
  7. 8. EA - The Big Picture Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL.
  8. 9. Talking about Meta-Architecture Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. <ul><li>The previous diagram illustrates an important point we made at the beginning of the presentation. Enterprise Architecture is Meta-Architecture. </li></ul><ul><li>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 ? </li></ul><ul><li>Meta-Architecture represents the deliberate attempt to reconcile architecture perspectives and the unique requirements of many systems which must co-exist in a unified enterprise environment. </li></ul>
  9. 10. Frameworks & Meta-Architecture Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. EA Frameworks support Lifecycle Management EA & lifecycle support support systems design DoDAF is an EA Framework example
  10. 11. What is a Framework ? Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. <ul><li>Enterprise Architecture Frameworks are a deliberate attempt to provide a mechanism for managing Meta-Architecture. </li></ul><ul><li>Frameworks allow architects to both describe and illustrate system and environmental characteristics within any given enterprise, parts thereof or even a conglomeration of enterprises. </li></ul><ul><li>Frameworks are generally thought of as collections of views or perspectives within a shared ‘generic’ enterprise taxonomy. That core taxonomy is often segregated by capability or technology type. </li></ul>
  11. 12. Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. A single house is much like a single system – it has various types of architecture within it and it exists within ever-larger ecosystems…
  12. 13. Frameworks are Metamodels Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. <ul><li>Enterprise Architecture Frameworks are the most familiar parts of EA, yet many people do not realize that they are essentially, flexible data models. </li></ul><ul><li>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.” </li></ul><ul><li>Metamodel integration makes it possible to map data back and forth across any Framework. There are several products that now automate such mappings. </li></ul><ul><li>Metamodels in general are attempts to provide outlines for capabilities and relationships – they can evolve. </li></ul>
  13. 14. An Example Metamodel Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. Part of the CADM Metamodel for DoDAF 1.5
  14. 15. Framework Example: DoDAF Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. <ul><li>DoDAF is the Department of Defense Architecture Framework. DoDAF evolved from several modeling approaches including C4ISR and IDEF. </li></ul><ul><li>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. </li></ul><ul><li>The latest version of DoDAF is 2.0, but many organizations still use version 1.5. The main difference between the versions is the shift in focus from ‘products’ to data models in 2.0, to facilitate automation and integration of architectures. </li></ul>
  15. 16. Meta-Model Flexibility Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. Even within the DoDAF standard versions, there is a great deal of flexibility on how to exploit the products or models…
  16. 17. Framework Example: Zachman Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. 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.
  17. 18. Framework Example: ToGAF Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. ToGAF is requirements focused – this is an important differentiation from other frameworks and has significant automation implications.
  18. 19. Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. 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.
  19. 20. Framework Example: ITIL Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. 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 industry standard template for a variety of IT security solutions.
  20. 21. Frameworks are Semantics Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. 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.
  21. 22. Semantic Integration Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. <ul><li>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. </li></ul><ul><li>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 the Lifecycle (both the development and management portions) of an enterprise. </li></ul>
  22. 23. SOA Architecture Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL.
  23. 24. SOA & Cloud Architecture Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. <ul><li>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. </li></ul><ul><li>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 are thought through and documented. Very few if any solutions (including all SOA & Cloud solutions) are ready ‘out of the box’ to deploy. </li></ul>
  24. 25. Future EA Presentations Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. <ul><li>Many of the topics we’ve introduced here are extremely complex and cannot be properly introduced within the context of this overview presentation. </li></ul><ul><li>We will be presenting a number of these topics within their own presentations, including: </li></ul><ul><ul><ul><li>An Introduction to DoDAF 2.0 </li></ul></ul></ul><ul><ul><ul><li>An Introduction to ToGAF </li></ul></ul></ul><ul><ul><ul><li>Understanding ITIL </li></ul></ul></ul><ul><ul><ul><li>An Introduction to Zachman </li></ul></ul></ul><ul><ul><ul><li>SOA, The Cloud & Enterprise Architecture </li></ul></ul></ul><ul><ul><ul><li>Enterprise Architecture & Semantic Integration </li></ul></ul></ul>
  25. 26. Web Servers are one thing, Nuclear Reactors are a bit more dangerous – there are systems which absolutely must not FAIL. As Complexity increases – the ingenuity needed to master it must continuously improve. Our architecture strategies will play an enormous role in determining whether we’re successful.
  26. 27. Conclusion <ul><li>Enterprise Architecture is more than any one architecture specialty – it is the synergistic combination of them all. </li></ul><ul><li>Architecture Frameworks are a symbolic framework for documenting and illustrating both characteristics and complex relationships in system of systems environments. </li></ul><ul><li>Frameworks are models of reality and frameworks are still evolving as is the practice of Enterprise Architecture. </li></ul>
  27. 28. About Semantech Inc. <ul><li>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. </li></ul><ul><li>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… </li></ul>

×