How was Training?


The course organized my knowledge and experience in enterprise architecture into a practical and pragmatic framework. - Solutions Architect, Board of Equalization, USA, Jan 2015

Recommend PEAF?


Yes - I don't have yet sufficient knowledgement on PEAF so to recommend or not to others (but in the previous question I just had the yes/no option) - Directora General - Miembro de la Comisi, Poder Legislativo del Uruguay, Uruguay, Jan 2015

  Introduction   Context   Methods   Artefacts   Culture   Environment   Adoption  




<< Previous <<

>> Next >>

Transformational Complexity is a function of:

      The Structural Complexity of the being transformed (S).

      The Transformational Volatility of changing it (V).

      The reason for the transformation - the Requirements (R).

      How much of the thing needs to be changed - its Scope (S).

To complicate matters, Scope is also a function of the Structural Complexity of the "thing" being transformed in addition to the Requirements. For example, a small requirement may cause a large change to the "thing" in question purely because of that "thing's" structural complexity. Conversely a large requirement may cause a small change to the "thing" in question again purely because of that "thing's" structural complexity.

While Transformational Complexity is low, people can deal with it easily, but as Transformational Complexity rises tools and techniques are required to cope. One tool/technique specifically designed to address this is The Architecture Paradigm.

"Seven thousand years of known history of humankind establishes that the only known strategy for accommodating extreme complexity and extreme change is... ARCHITECTURE!!!"

- John A. Zachman

Are you aware of your Enterprise's Transformational Complexity?

How would you define it?

How would you measure it?

Do you care?


2008-2016 Pragmatic EA Ltd