Actions

Difference between revisions of "Adaptive Enterprise Framework (AEF)"

m
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
The Adaptive Enterprise Framework (AEF) is focused on the aspects of enterprise architecture that promote business alignment and enterprise agility. It is not meant to be a comprehensive, all-encompassing framework that addresses every perceivable enterprise architecture view. For example, it does not address security or infrastructure service components. However, as far as theauthors are aware, it can fit into other frameworks, such as the Federal Enterprise Architecture Framework, and make them more actionable as business tools. The AEF is an integration of [[Value-Chain-Analysis|value chain analysis]], [[Business-Process-Management|Business Process Management]], Service-Component Based Architecture, and Business Analytics in the context of MDA. Within the AEF enterprise, architecture becomes a function of the analytic processes that guide the enterprise. It is integral to strategy, design, implementation, and operations of a business enterprise. It does not start and stop as a periodic process for “cleaning house,” but is an everyday part of enterprise activities. It achieves this status by providing an enterprise modeling environment that can be integrated into ongoing business operations and can become an integral tool for managing the enterprise. In the GSA Portman Proof of Concept, which will be discussed later in the paper, we demonstrate an instance of using AEF to define a portion of an enterprise, and demonstrate how it can become part of the management infrastructure. <ref>What is Adaptive Enterprise Framework? [http://www.bptrends.com/publicationfiles/01-04%20WP%20Ent%20Arch%20Mod%20-%20Nelson.pdf BP Trends]</ref>
+
'''The Adaptive Enterprise Framework (AEF)''' is focused on the aspects of enterprise architecture that promote business alignment and enterprise agility. It is not meant to be a comprehensive, all-encompassing framework that addresses every perceivable enterprise architecture view. For example, it does not address security or infrastructure service components. However, as far as the authors are aware, it can fit into other frameworks, such as the [[Federal Enterprise Architecture Framework (FEA)|Federal Enterprise Architecture Framework]], and make them more actionable as business tools. The AEF is an integration of [[Value Chain Analysis|value chain analysis]], [[Business Process Management (BPM)|Business Process Management]], [[[Service Component Architecture (SCA)]]|Service-Component Based Architecture]], and [[Business Analytics]] in the context of [[Model Driven Architecture (MDA)|MDA]]. Within the AEF enterprise, architecture becomes a function of the analytic processes that guide the enterprise. It is integral to strategy, design, implementation, and operations of a business enterprise. It does not start and stop as a periodic process for “cleaning house,” but is an everyday part of enterprise activities. It achieves this status by providing an enterprise modeling environment that can be integrated into ongoing business operations and can become an integral tool for managing the enterprise. The GSA Portman Proof of Concept demonstrates an instance of using AEF to define a portion of an enterprise, and demonstratse how it can become part of the management infrastructure. <ref>What is Adaptive Enterprise Framework? [http://www.bptrends.com/publicationfiles/01-04%20WP%20Ent%20Arch%20Mod%20-%20Nelson.pdf BP Trends]</ref>
  
  
Line 12: Line 12:
 
*7. The Infrastructure is the Architecture: While it is helpful in most large enterprises to have a documented enterprise architecture, it is far more important to have a working one. Without a doubt, there are many well-documented and elegant architectures that never have been implemented, making them useless. There are also elegant and effective architectures with no central supporting documentation.
 
*7. The Infrastructure is the Architecture: While it is helpful in most large enterprises to have a documented enterprise architecture, it is far more important to have a working one. Without a doubt, there are many well-documented and elegant architectures that never have been implemented, making them useless. There are also elegant and effective architectures with no central supporting documentation.
  
[[File: Adaptive Enterprise Framewrk.jpg.|300px|Absorption Costing]]<br />
+
[[File: Adaptive Enterprise Framewrk.jpg|300px|Adaptive Enterprise Framework]]<br />
 
Source: [https://www.cgma.org/resources/tools/essential-tools/activity-based-costing.html CGMA]
 
Source: [https://www.cgma.org/resources/tools/essential-tools/activity-based-costing.html CGMA]
  
  
 
===See Also===
 
===See Also===
[[Enterprise_Architecture|Enterprise Architecture]]<br />
+
*[[Enterprise Architecture Framework]]
[[enterprise_architecture_framework|Enterprise Architecture Framework]]<br />
 
[[federal_enterprise_architecture_framework|Federal Enterprise Architecture Framework (FEA)]]<br />
 
[[Adaptive_Enterprise|Adaptive Enterprise]]<br />
 
[[The_Open_Group_Architecture_Framework_(TOGAF)|The Open Group Architecture Framework (TOGAF)]]<br />
 
[[Zachman_Framework|Zachman Framework]]<br />
 
[[Department_of_Defense_Architecture_Framework_(DoDAF)|Department of Defense Architecture Framework (DoDAF)]]<br />
 
[[Technical_Architecture_Framework_for_Information-Management_(TAFIM)|Technical Architecture Framework for Information Management (TAFIM)]]<br />
 
 
 
  
  
Line 33: Line 25:
  
 
====Further Reading====
 
====Further Reading====
*A Framework for a Business Intelligence-Enabled Adaptive Enterprise Architecture [https://link.springer.com/chapter/10.1007/978-3-319-12206-9_33 Akhigbe O., Amyot D., Richards G. (2014) In: Yu E., Dobbie G., Jarke M., Purao S. (eds) Conceptual Modeling. ER 2014. Lecture Notes in Computer Science, vol 8824. Springer, Cham]
+
*[https://link.springer.com/chapter/10.1007/978-3-319-12206-9_33 A Framework for a Business Intelligence-Enabled Adaptive Enterprise Architecture -Akhigbe O., Amyot D., Richards G. (2014) In: Yu E., Dobbie G., Jarke M., Purao S. (eds) Conceptual Modeling. ER 2014. Lecture Notes in Computer Science, vol 8824. Springer, Cham]
*The Gill Framework® – Adaptive Enterprise Architecture Management [http://www.aqgill.com/the-adaptive-enterprise-architecture-management/ AQ Gill]
+
*[http://www.aqgill.com/the-adaptive-enterprise-architecture-management/ The Gill Framework® – Adaptive Enterprise Architecture Management -AQ Gill]
*Adaptive Enterprise Architecture for the Future: Towards a Reconceptualization of EA [^http://ieeexplore.ieee.org/document/7780323/ IEEE]
+
*[^http://ieeexplore.ieee.org/document/7780323/ Adaptive Enterprise Architecture for the Future: Towards a Reconceptualization of EA -IEEE]
  
  
 
===CIO Desk Reference===
 
===CIO Desk Reference===
 
(Relevant content on this topic in the CIO Toolkit on CIO Index)
 
(Relevant content on this topic in the CIO Toolkit on CIO Index)
*EA: Using the Adaptive Enterprise Framework [https://www.cioindex.com/article/articleid/1159/ea-using-the-adaptive-enterprise-framework CIO Index]
+
*[https://cioindex.com/reference/ea-using-the-adaptive-enterprise-framework/ EA: Using The Adaptive Enterprise Framework]
*Commission Enterprise Architecture Framework V1.0 [https://www.cioindex.com/article/articleid/118529/commission-enterprise-it-architecture-framework-v1-0 CIO Index]
+
*[https://cioindex.com/reference/commission-enterprise-it-architecture-framework-v1-0/ Commission Enterprise Architecture Framework V1.0]

Latest revision as of 15:19, 14 March 2023

The Adaptive Enterprise Framework (AEF) is focused on the aspects of enterprise architecture that promote business alignment and enterprise agility. It is not meant to be a comprehensive, all-encompassing framework that addresses every perceivable enterprise architecture view. For example, it does not address security or infrastructure service components. However, as far as the authors are aware, it can fit into other frameworks, such as the Federal Enterprise Architecture Framework, and make them more actionable as business tools. The AEF is an integration of value chain analysis, Business Process Management, [[[Service Component Architecture (SCA)]]|Service-Component Based Architecture]], and Business Analytics in the context of MDA. Within the AEF enterprise, architecture becomes a function of the analytic processes that guide the enterprise. It is integral to strategy, design, implementation, and operations of a business enterprise. It does not start and stop as a periodic process for “cleaning house,” but is an everyday part of enterprise activities. It achieves this status by providing an enterprise modeling environment that can be integrated into ongoing business operations and can become an integral tool for managing the enterprise. The GSA Portman Proof of Concept demonstrates an instance of using AEF to define a portion of an enterprise, and demonstratse how it can become part of the management infrastructure. [1]


The Adaptive Enterprise Framework (AEF) Principles[2]
Unlike other more generic frameworks, AEF assumes an immediate commitment to several key architectural principles:

  • 1. Customer Value Driven: Using value chain analysis to effectively align the enterprise to customer and market place needs and realities;
  • 2. Integrated Business Model: Using BPM to define an integrated business model that includes business processes, application services, and information. This properly positions the definition of application and information logic into the business architecture where it belongs;
  • 3. Model Driven Architecture: Commitment to migrating business logic from legacy bound fragile programming languages to platform independent business modeling languages;
  • 4. Performance Based Enterprise Management: Making performance management an integral part of the enterprise model and using business analytics to provide predictive indicators of future performance or changes to market requirements;
  • 5. Service-Component Based Architecture: Commitment to provisioning business logic as reusable components that can be instantiated to support varying non-functional requirements, i.e., scaleability, security, QoS, reliability, and availability;
  • 6. Traceable Service Based Technology Architecture: Defines technology components as services with traceability to the business process areas supported;
  • 7. The Infrastructure is the Architecture: While it is helpful in most large enterprises to have a documented enterprise architecture, it is far more important to have a working one. Without a doubt, there are many well-documented and elegant architectures that never have been implemented, making them useless. There are also elegant and effective architectures with no central supporting documentation.

Adaptive Enterprise Framework
Source: CGMA


See Also


References

  1. What is Adaptive Enterprise Framework? BP Trends
  2. The Adaptive Enterprise Framework (AEF) Principles bptrends.com


Further Reading


CIO Desk Reference

(Relevant content on this topic in the CIO Toolkit on CIO Index)