How was Training?


The course clearly exposed what is required for Enterprise Architecture to be recognized and successfully managed within an organization. - Associate Director (EA), PPDI, USA, Sep 2010

Recommend PEAF?


Yes - Even if you don't adopt PEAF, it is a valuable source of information, and provides easily understood explanations and rationale for elements of EA - Enterprise Architect, Aviva , UK, Jul 2012

  Introduction   Context   Methods   Artefacts   Culture   Environment   Adoption  




<< Previous <<

>> Next >>

In relation to the Transformation of Enterprises, there are many tools (Pragmatic EA are tracking hundreds) that have been produced to help Enterprises deal with Enterprise Transformation in a more effective and efficient manner

These tools come in are of various types; Governance, Risk, Compliancy tools, Portfolio, Program, Project Management tools, Business, IT Strategy tools, Enterprise, Solution, Technical Architecture tools, Software Engineering tools, Change Management tools, Configuration Management tools, CASE tools, Test Management, Load Testing, Stress Testing tools, etc, etc, etc.

Each of these tools has been designed and engineered to operate with a specific domain or context, for example; strategic planning, project management, enterprise architecture, software design and development, service management, change management, etc, etc, etc.

We could categorise tools in different ways:

      Scope - Some tools exist to help with Strategising or Roadmapping, while others exist to help with the design of systems, or a particular discipline such as Project Management.

      Type - Some tools deal only with Structural elements of Transformation (Categories, Ontologies, meta-models) like Archimate while others deal more with Procedural elements of Transformation (Methods, Practices, Processes) like MS Project or Rational RequisitePro.


2008-2016 Pragmatic EA Ltd