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 - I think it is a more an easier framwork to pick up that others - Solution Architect, HealthNow New York, USA, Feb 2015

  Introduction   Context   Methods   Artefacts   Culture   Environment   Adoption  

Desktop

Mobile






 

<< Previous <<

>> Next >>

To carry out the work in the EA domain (Strategising and Roadmapping) effectively and efficiency, tools are mandatory.

There are two fundamental domains (types) of information that any tool needs to be able to work with (Structural and Transformational) and this information is consumed and produced by various Disciplines.

In general (because of their history and initial focus) tools operating primarily on Structural information have tended to be called EA Modelling tools and tools operating primarily on Transformational information have tended to be called EA Planning Tools. This is not a hard and fast rule though as many tools describe themselves using various adjectives - it's not what they call themselves, it's what information they manipulate.

 

Which tools do you currently use?

What domains (Structural/Transformational) do they cover?

What disciplines utilise them?

Are they adequate?

If so, does this present any issues or problems?

What will you do to alleviate or solve them?

 


 

2008-2016 Pragmatic EA Ltd