Gartner suggest to use an Emergent Enterprise Architecture




Gartner has identified seven properties that differentiate emergent architecture from the traditional approach to EA:

  1. Non-deterministic - In the past, enterprise architects applied centralised decision-making to design outcomes. Using emergent architecture, they instead must decentralise decision-making to enable innovation.

  2. Autonomous actors - Enterprise architects can no longer control all aspects of architecture as they once did. They must now recognise the broader business ecosystem and devolve control to constituents.

  3. Rule-bound actors - Where in the past enterprise architects provided detailed design specifications for all aspects of the EA, they must now define a minimal set of rules and enable choice.

  4. Goal-oriented actors - Previously, the only goals that mattered were the corporate goals but this has now shifted to each constituent acting in their own best interests.

  5. Local Influences: Actors are influenced by local interactions and limited information. Feedback within their sphere of communication alters the behaviour of individuals. No individual actor has data about all of an emergent system. EA must increasingly coordinate.

  6. Dynamic or Adaptive Systems: The system (the individual actors as well as the environment) changes over time. EA must design emergent systems sense and respond to changes in their environment.

  7. Resource-Constrained Environment: An environment of abundance does not enable emergence; rather, the scarcity of resources drives emergence.

The original article from Gartner:  Gartner Identifies New Approach for Enterprise Architecture
And the reactions:  Reactions to Gartner’s Suggestion to Use an “Emergent Architecture”


If you are surprised by the Gartner suggestions maybe you are interested to read this:  Agile Architecture


Print | posted @ Wednesday, December 2, 2009 11:58 PM

Comments have been closed on this topic.