Cutting EA to the bone

Home

Comments About Us FAQ Search
Home
PeaF - Foundation
PeaF - Communication
PeaF - Model
PeaF - Governance
PeaF - Management
Downloads
Frameworks
Training
Licensing
Certification
Practitioners
Trainers
Training Providers
Consultancies
Tool Vendors

EA Framework Survey

Which Framework do you think is most suited to helping organisations implement, operate and gain the benefits of Enterprise Architecture in a fast and low cost manner?

TOGAF
Zachman
IAF
TEAF
E2AF
MoDAF
DoDAF
PeaF

  See Results

........Don't Forget to Register For Updates...........

To make sure you hear about changes to PeaF please register here to receive updates.

e-mail address:

e-mail address confirmation:

Subscribe
Un-subscribe

  
Last Updated
02/07/2009 09:39:03

Enquiries: Info@PragmaticEA.com

This section details the tasks and artefacts that are required to instigate and gain approval for an EA programme of work.

Using these as a starting point allows a rapid definition and proposal to be formulated This part of the framework covers the communication aspects of Enterprise Architecture.
					
Although a small section, this is probably the most important part of the whole framework since if this aspect is not successful your Enterprise Architecture initiative will fail. No if’s or but’s. It will fail.

It is also probably the hardest part of EA to get right, which probably accounts for why so many EA initiatives fail. This part of the framework covers the main artefact of an EA initiative - the EA Model.

The EA Model is the bedrock of EA. While Communication is key to its success, the EA Model forms the backbone of an EA imitative as it is the main repository of information about the organisation, its objectives, Goals, Targets and Strategies.

The model is not meant to be used by an elite group of individuals. The more people use it, and the more people contribute to it the more benefit the organisation will attain. This part of the framework covers the quality control which makes sure that either agreed principles, policies and standards are being followed, or, if not, that the impacts, risks and implications of not doing so are costed, understood, accepted and managed.

A key point regarding governance is that it should not be viewed as a policing environment where things are rejected and accepted or that penalties are incurred for breaking the rules.

The approach must be culture based, with the organisation (business and IS) understanding the reasons behind the principles, policies and standards existing and how they contribute to move the organisation from where it is to where it wants to be. This part of the framework covers the management aspects of the EA initiative.
					
This provides the context and support for all other EA work to take place within. What is PeaF?  PeaF is a vendor and consultancy independent, technology neutral, Pragmatic Enterprise Architecture Framework which allows organisations to kick start or re-start an EA initiative and provides a comprehensive EA Framework and associated Toolkit of everything required to hit the ground running.

What is in the PeaF Toolkit? The Toolkit consists of; Foundation (Vision, Maturity Model, Plan & Risks), Communication (Slide-sets), Model (Metamodel, Tool Evaluation & Content, Gathering Process), Governance (Principles & Process), Management (Metrics & Process)

What do the analysts say? - Henry Peyret of Forrester Research says

"It is hard to find free alternatives to TOGAF as most of the alternatives come from consulting companies. Pragmatic EA Framework (PeaF) is one freely downloadable EA Framework for end user companies which is comparable in terms of coverage to TOGAF. It claims to be more pragmatic but since it was published in November 2008 it is too early to judge its pragmatic-ness at the moment. However, some companies looking for simpler approach can at least take a look to PeaF and may find it useful either as a complement or a replacement to TOGAF."

How does PeaF relate to other Frameworks?  PeaF bridges the gap between minimal "EA Frameworks" like Zachman which is only a Metamodel and “EA Frameworks” like TOGAF which is huge and complicated and difficult for Enterprise Architects and Organisations to get to grips with.

PeaF is not meant to replace other frameworks but fill the void between the very small and the very large by “Cutting EA to the Bone” and providing everything you need, and nothing you don’t.

Take a look at the Comparison of Zachman, TOGAF and PeaF.

Who will benefit from PeaF? Any Company or Government Agency where the relationship between the Business and IT is not one of a harmonious partnership.

Where did PeaF come from? PeaF has been formulated over a 7 year period by understanding why so many EA initiatives fail and plugging all those holes.

Where should I begin?


The framework splits into 5 main areas: -

  Foundation The foundation provides the starting point for initiating all other EA work.
  Communication Communication is the key to EA. Without it, everything else is superfluous.
  Model The main artefact of EA are the models which allow information to be gathered, viewed and analysed.
  Governance Providing an environment to guide change as it happens throughout the organisation.
  Management Providing the process to manage the work and measure success.

 

Share/Save/Bookmark