Recommended
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
PEAF - Where Does EA Fit?
- 1. Where does PEAF fit?
- 2. How does PEAF relate to Zachman and TOGAF
- 3. Context – The Organisation
- 4. Context – The Market
- 5. Context – The Enterprise
- 10. Context – Abstraction Layers to Models
- 11. How does PEAF relate to Governance?
- 14. To find out more, please visit us at www.PragmaticEA.com Cutting EA to the bone © Pragmatic EA Ltd
Editor's Notes
- Enterprise Architecture is probably one of, if not he the most, misunderstood terms in the business and IT world today. Most people have a definition for it - The problem is, a lot of those definitions are either incomplete or just plain wrong. I know because I used to be one of those people. It has become clear to me that Enterprise Architecture is not complicated, is not difficult, is not expensive. Of course there are elements out there who would prefer boards and organisations to think that it is complicated, is difficult and therefore is expensive. That is not to say that Enterprise Architecture does not have its issues problems and risks. However, so long as the key tenet’s are understood and the issues, problems and risks are managed, any organisation can instigate and reap the benefits of Enterprise Architecture.
- First in order to be better able to represent the mapping of various frameworks later on, we split The Organisation into three parts: - Everything that is IT – This includes all hardware and software and Technical Infrastructure such as Networks. Everything in the organisation that is not IT but touches IT – This includes generally Business Processes, Departments, divisions, Locations etc. Everything else in the organisation that does not touch IT – This includes Business Processes, Departments, Divisions and Locations that do not touch/utlise IT but also things like Trucks, Oil Rig Drill bits, etc
- The Organisation , however, is not an island. The Organisation , operates in the context of The Market consisting of, for example, the Regulators, Competitors, Suppliers and Customers.
- The Market , however, is not an island. The Market , operates in the context of The Enterprise consisting of, for example, the Communities, Governments, Non-Customers, Anti customers, etc. We can now use this high level view as a basis to overlay various frameworks to be better able to see what areas they cover and what areas they do not cover.
- The Zachman framework (or at least the rows) allow us to see the different levels within The Enterprise , The Market and The Organisation . Some levels are wholly contained within The Organisation such as Planning, Change Projects and Running the organisation, while others such as the Contextual (or Strategy) level involves considering the wider market and the much wider Enterprise and spans The Enterprise , The Market and The Organisation . Note that the Zachman “Component” level is not used as it is just a decomposition of the Physical level/
- We can see how an EITA framework such as TOGAF covers all the Logical, Physical and Component Layers and also some part of the Conceptual or Planning layer. It does not concern itself with anything in The Organisation that does not touch IT and therefore only covers a small part of the Conceptual or Planning layer. It largely ignores The Market and totally ignores The Enterprise .
- Now we see how an EA framework such as PEAF maps onto The Enterprise , The Market and The Organisation . The important things to consider are: EA Is bigger than The Organisation . EA is bigger than The Market which The Organisation operates within. EA considers the entire breadth of The Organisation and it’s context, of which IT is a part, but only a part. EA is concerned with Strategy, Change Planning and the governance of Change projects. PEAF and TOGAF are complimentary not contradictory. The area of overlap in Governance.
- For completeness we also add in the popular IT Infrastructure Library (ITIL) to see how this relates to the overall picture. We can see that ITIL is all about the Management of running IT Services although it does try to relate those operating services up to the level of change projects and strategy. Like most things these frameworks are not in competition but actually work in unison and compliment each other. Understanding where they sit and how they relate to each other (The Architecture of Frameworks) will help the reader in their understanding and application of them.
- This slide illustrates how the abstraction layers align to the various processes and various models required in the Organisation to enable it to coep with change.