How was Training?

more

It was an interesting course however I believe that the focus on selling 'EA' was too much. The first 2 days should be condensed and an explanation of what EA is should preceed selling EA otherwise you have no idea what you are selling!!! I found this ver - Enterprise Architect, EBRD, UK, Feb 2012

Recommend PEAF?

more

Yes - Coverage of who, what, why and a framework on how. - Technical architect, ActewAGL, Australia, Jan 2015

  Introduction   Context   Methods   Artefacts   Culture   Environment   Adoption  

Desktop

Mobile

 

<< Previous <<

>> Next >>

Here we have highlighted one phase of the transformation cascade to look at, but please keep in mind that although we are using one phase as an example, everything you will now see can be equally applied to any other phase.

      Solid lines indicate models that are created in this phase. Outputs.

      Dotted lines indicate models that are created in another phase (either below or above). Inputs.

      Models indicated with blue lines are structural models (defined by MACE) models indicated with red lines are transformational models (defined by MAGMA).

There are five fundamental disciplines defined:

      Requirements Management - Where requirements are understood and refined to the level required to drive the phase.

      Discovery - Where information about the current structural state is obtained.

      Analysis & Design - Where the information about the Target state and the means to achieve it is created.

      Governance & Lobbying - Where the information is reviewed and any Enterprise Debt is exposed and managed.

      Modelling - An overall pseudo-discipline which is used by all other disciplines.

 

Are there other fundamental disciplines that you think should be included?

Why?

 

 

2008-2016 Pragmatic EA Ltd