How was Training?


A very positive and educational experience. - Business Analyst - MGR IT, PPDI, USA, Sep 2010

Recommend PEAF?


Yes - Concise and re-usable and do not need to go through other frameworks in detail - Security Architect, Visa Europe, UK, Feb 2015

  Introduction   Context   Methods   Artefacts   Culture   Environment   Adoption  




<< Previous <<

>> Next >>

Here we consider the Artefacts for the whole Transformation domain (as defined by POET) and highlight the Artefacts within the EA domain.

Essentially we are concerned with the Transformational and Structural information utilised by the Strategising and Roadmapping phases (as defined in the Methods section) and the associated Governance/Lobbying work down to projects.

The structural information is represented at three levels of abstraction: Enterprise Context, Contextual and Conceptual, and in support of these three Structural levels, there are two Transformational levels that support the phases and allow the transformation between the Structural Levels to happen.


In what way does your Enterprise consider Transformational and Structural models at these levels?

What ontologies and Meta-models are you using?

How do they map to, and fit into this Ontology?

Are they any gaps or overlaps?

If there are gaps and or overlaps, is it useful to know that?

What will you do to fill the gaps and remove the overlaps?



2008-2016 Pragmatic EA Ltd