Changes

Adaptive enterprise architecture theory, sometimes abbreviated to AEA, involves adapting, defining, operating, managing and supporting (ADOMS)  enterprise architecture design (Gill 2015). The focus of design is on the  design of adaptive enterprise as an "adaptive enterprise service system" operating in the networked and connected ecosystem (system of systems).  

Adaptive enterprise architecture theory, sometimes abbreviated to AEA, involves adapting, defining, operating, managing and supporting (ADOMS)  enterprise architecture design (Gill 2015). The focus of design is on the  design of adaptive enterprise as an "adaptive enterprise service system" operating in the networked and connected ecosystem (system of systems).  

The AEA theory provides the ADOMS approach, which is organized into two layers: outer layer and inner layer. The outer layer presents the adapting capability and the inner layer presents the defining, operating, managing, and supporting capabilities. The integrated inner and outer capabilities collectively define the “ADOMS” approach for the adaptive enterprise architecture. The outer layer identifies and feeds the adaptation changes (threat and opportunities) to inner layer. The inner layer handles the changes through the integrated engagement and governance.

 

The AEA theory focuses on the data-driven capability to "continuously '''scan and sense''' the internal and external environment for '''data''' about known and unknown events (complex event processing), changes or disruptions, '''interpret and analyses''' the collected data, and '''decide and respond''' based on intuition and rationale to expected and unexpected changes (threats and or opportunities) for adaptations".

 

 

The AEA theory includes the ADOMS approach, which is organized into two layers: outer layer and inner layer. The outer layer presents the adapting capability and the inner layer presents the defining, operating, managing, and supporting capabilities. The integrated inner and outer capabilities collectively define the “ADOMS” approach for the adaptive enterprise architecture. The outer layer identifies and feeds the adaptation changes (threat and opportunities) to inner layer. The inner layer handles the changes through the integrated engagement and governance.

Outer layer: The adapting capability involves context awareness, enterprise architecture assessment, rationalisation, realisation, and unrealisation of changes for adaptation.  The adapting capability includes: scan and sense, interpret and analyse, decide and respond to internal and external changes (data-driven adaptability). The adapting capability in the outer layer initially identifies the change requirements (initiatives or ideas) that may initiate 1 or many projects. These project(s) initiatives or ideas can be further defined and handled through the inner layer via integrated engagement and governance. Deferred or low priority changes are pushed to unrealisation, which can be pulled again and reprioritized for realisation, if required.  Inner layer: This includes defining, operating, managing and supporting the integrated adaptive enterprise architecture capability for handling the change for adaptation via identified projects from the outer layer.  

Outer layer: The adapting capability involves context awareness, enterprise architecture assessment, rationalisation, realisation, and unrealisation of changes for adaptation.  The adapting capability includes: scan and sense, interpret and analyse, decide and respond to internal and external changes (data-driven adaptability). The adapting capability in the outer layer initially identifies the change requirements (initiatives or ideas) that may initiate 1 or many projects. These project(s) initiatives or ideas can be further defined and handled through the inner layer via integrated engagement and governance. Deferred or low priority changes are pushed to unrealisation, which can be pulled again and reprioritized for realisation, if required.  Inner layer: This includes defining, operating, managing and supporting the integrated adaptive enterprise architecture capability for handling the change for adaptation via identified projects from the outer layer.  

Qumer, A. and Henderson-Sellers, B. (2006). Measuring agility and adaptibility of agile methods: A 4 dimensional analytical tool. In ''The IADIS international conference on applied computing 2006''. IADIS Press.

Qumer, A. and Henderson-Sellers, B. (2006). Measuring agility and adaptibility of agile methods: A 4 dimensional analytical tool. In ''The IADIS international conference on applied computing 2006''. IADIS Press.

Qumer, A. and Henderson-Sellers, B. (2008). An evaluation of the degree of agility in six agile methods and its applicability for method engineering. ''Information and software technology'', ''50''(4), pp.280-295.

Qumer, A. and Henderson-Sellers, B. (2008). An evaluation of the degree of agility in six agile methods and its applicability for method engineering. ''Information and software technology'', ''50''(4), pp.280-295.

Gill, A.Q. (2013). Towards the Development of an Adaptive Enterprise Service System Model. ''Proceedings of the Nineteenth Americas Conference on Information Systems'', ''Chicago, Illinois''.

Gill, A.Q. (2013). Towards the Development of an Adaptive Enterprise Service System Model. ''Proceedings of the Nineteenth Americas Conference on Information Systems'', ''Chicago, Illinois''.

Alzoubi, Y.I., & Gill, A.Q. (2020). An Empirical Investigation of Geographically Distributed Agile Development: The Agile Enterprise Architecture Is a Communication Enabler. ''IEEE Access'', 80269-80289.

Alzoubi, Y.I., & Gill, A.Q. (2020). An Empirical Investigation of Geographically Distributed Agile Development: The Agile Enterprise Architecture Is a Communication Enabler. ''IEEE Access'', 80269-80289.

Srinivas, S., Gill, A.Q., & Roach, T. (2021). Can Business Architecture Modeling be Adaptive? ''IT Professional'', ''23''(2), 81-88.

Srinivas, S., Gill, A.Q., & Roach, T. (2021). Can Business Architecture Modeling be Adaptive? ''IT Professional'', ''23''(2), 81-88.

==Level of analysis==

==Level of analysis==

Design of an enterprise, ecosystem

Design of a service, capability, enterprise, ecosystem

==Links from this theory to other theories==

==Links from this theory to other theories==