Enterprise architecture framework
An Architecture Framework is a specification of how to organize and present an Enterprise Architecture. Because the discipline of Enterprise Architecture is so broad, and because the enterprises it describes are often large, it can result in very complex models. To manage this complexity, an Architecture Framework defines a standard set of model categories (called “Views” ) which each have a specific purpose. Some of the larger Architecture Frameworks define categories of views in terms of the domain they address - e.g. "business", "technical", "information", etc.
The Zachman framework is widely regarded as the first Architecture Framework, from which others such as DoDAF and MODAF evolved. Another widely used framework is TOGAF, though this has much more of a methodological flavour to it than the aforementioned frameworks.
Usage
Architecture Frameworks are commonly used in IT/IS governance. An organization may wish to mandate that certain models be produced before a system design can be approved. Similarly, they may wish to specify certain views be used in the documentation of procured systems - the U.S. Department of Defense stipulates that specific DoDAF views be provided by equipment suppliers for capital project above a certain value.
In recent years, it has become apparent that a key benefit to be gained from Enterprise architecture is the ability to support decision making in changing businesses. Because Enterprise Architecture brings together business models (e.g. process models, organizational charts, etc.) and technical models (e.g. systems architectures, data models, state diagrams, etc.) it is possible to trace the impact of organizational change on the systems, and also the business impact of changes to the systems. The views-based approach of most Architecture Frameworks can provide decision support to a certain degree - i.e. the decision maker can look to the models and work out where the critical dependencies are. However, in more complex scenarios with large enterprise models, and numerous variables and dependencies, the granularity of a views-based approach is not sufficiently fine. Many of the more recent Architecture Frameworks such as DoDAF, MODAF, or AGATE are underpinned by a standard meta model which defines the critical architectural elements and the dependencies between them. Applications based on these models can then query the underlying architectural information.
References
- Tony Shan and Winnie Hua (2006). Solution Architecting Mechanism. Proceedings of the 10th IEEE International EDOC Enterprise Computing Conference (EDOC 2006), October 2006, p23-32.
- Tony Shan and Winnie Hua (2006). A Service-Oriented Solution Framework for Internet Banking. International Journal of Web Services Research, Vol. 3, Issue 1, pp 29-48.
See also
- DoDAF, the framework promoted by the United States Department of Defense (DoD)
- MODAF, the framework promoted by the UK Ministry of Defence (MoD)
- AGATE, the framework promoted by the French Délégation Générale pour l'Armement (DGA)
- TOGAF