| |
The following list of links provides a knowledge index of Enterprise Architecture Frameworks, standards and related other methodologies which we as an organisation practise. If you are looking specifically for research information at any level upon any of these subject matters then please do call us to see how we can help you. Recommended Frameworks: Other Industry Specific and Proprietary Frameworks: Comparison of Frameworks: Comparison Of Enterprise Architecture Frameworks The Open Group defines TOGAFTM as a framework - a detailed method and a set of supporting tools for developing IT and Enterprise Architecture. There are many architecture frameworks, but TOGAFTM is unique in containing a method for developing architecture - the TOGAFTM Architecture Development Method (ADM). The ADM can be used with other popular frameworks and so we might call it framework-agnostic. TOGAFTM is the result of best practice, as gathered by The Open Group's Architecture Forum. Consequently, TOGAFTM's great strength is that it is non-proprietary and free to use. However, this does mean that architects need to customise and tailor TOGAFTM to their organisation's specific needs. TOGAFTM web site The Zachman Framework is a framework providing a view of the subjects and models needed to develop a complete enterprise architecture. This framework is described in detail at the ZIFA web site. An alternative source is the University of Nebraska at Omaha, which gives a very detailed and highly readable description of the Zachman Framework. The Zachman Framework is a widely used approach for developing and/or documenting an enterprise-wide Information Systems Architecture. Zachman based his framework on practices in traditional architecture and engineering. This resulted in an approach which on the vertical axis provides multiple perspectives of the overall architecture, and on the horizontal axis a classification of the various artifacts of the architecture. The purpose of the Framework is to provide a basic structure which supports the organization, access, integration, interpretation, development, management, and changing of a set of architectural representations of the organization's information systems. Such objects or descriptions of architectural representations are usually referred to as artifacts. The framework, then, can contain global plans as well as technical details, lists, and charts as well as natural language statements. Any appropriate approach, standard, role, method, technique, or tool may be placed in it. In fact, the Framework can be viewed as a tool to organize any form of metadata for the enterprise. Zachman web site The Department of Defense Architecture Framework (DoDAF) defines a standard way to organize an enterprise architecture (EA) or systems architecture into complementary and consistent views. All major U.S. Government Department of Defense (DoD) weapons and information technology system procurements are required to develop and document an EA using the views prescribed in the DoDAF. While it is clearly aimed at military systems, DoDAF has broad applicability across the private, public and voluntary sectors around the world, and represents only one of a large number of systems architecture frameworks. It is especially suited to large systems with complex integration and interoperability challenges, and is apparently unique in its use of "operational views" detailing the external customer's operating domain in which the developing system will operate. DODAF web site The cross-Governement Enterprise Architecture (xGEA) is a fundamental element of the governement's "Transformational Governement - Enabled by Technology" strategy which was published in November 2005. In that strategy the first priority of the CTO Council was identified as being to agree and publish a standard Enterprise Architecture reference model which would help align existing and emerging technical architectures across governement with the xGEA. Governement like most enterprises is extremely complex and subject to an ever increasing rate of change. Accommodating change is costly, time-consuming and can be an obstacle to success. Information Technology is a complex and fundamental enabler, but difficult to change quickly. Against this background we have created a practical, pragmatic approach to developing our xGEA. Many parts of the public sector are already in the process of creating or are maintaining an enterprise architecture. The xGEA is intended to supplement not replace the architecture capabilities of specific public sector bodies. The xGEA will define a set of views to allow decision makers to make the right choices to best transform governement enabled by IT. The focus of Release 1 is to create views that will facilitate both the production and consumption of reusable assets. In order to rapidly achieve value an 'exemplars approach' has been adopted. Exemplars are tested and proven processes, methods, tools, techniques, systems or services nominated for collective use by their business leader, CTO or CIO. It will enable public sector bodies to submit the good practice assets for consumption from other organisations and will facilitate the consumption of those assets. This process has been designed by contributions from Departments, Agencies, Local Governement and the Devolved Administrations. In order to communicate across the organisations a common language will be required. To facilitate this, a Reference Model has been built, and is being populated with exemplars' details. It is envisaged that the process to capture and assign exemplars will continue to develop over time. As this work evolves the models will change to reflect the language being used. Our iterative approach will allow us to develop this work in a pragmatic and achievable way. xGEA web site Federal Enterprise Architecture (FEA) is the Enterprise Architecture of a Federal Government, which provide a common methodology for information technology (IT) acquisition, use, and disposal in that Federal government. Structure of the U.S. "Federal Enterprise Architecture Framework" (FEAF) Components, presented in 2001. Enterprise Architecture (EA) is a management practice for aligning resources to improve business performance and help agencies better execute their core missions. An EA describes the current and future state of the agency, and lays out a plan for transitioning from the current state to the desired future state. Federal Enterprise Architecture is a work in progress to achieve these goals. The U.S. Federal Enterprise Architecture (FEA) is an initiative of the U.S. Office of Management and Budget that aims to comply with the Clinger-Cohen Act and provide a common methodology for information technology (IT) acquisition in the United States federal government. It is designed to ease sharing of information and resources across federal agencies, reduce costs, and improve citizen services. FEAF web site Capgemini has been developing its own architecture approach that covers business, information and technology since 1993. This approach, or framework, which is called the Integrated Architecture Framework (IAF), has been developed from the experience of practicing architects on projects for clients across the group. IAF is:
MODAF is an internationally recognised enterprise architecture framework developed by the MOD to support Defence planning and change management activities. It does this by enabling the capture and presentation of information in a rigorous, coherent and comprehensive way that aids the understanding of complex issues. MODAF web site Comparison Of Enterprise Architecture Frameworks This article Provides a comparison of the major EA frameworks. Enterprises can use different EA frameworks based on their needs and available resources. EA frameworks can be very complex to have different views as demonstrated in the Zachman framework, the TOGAFTM framework, the FEAF framework and the DODAF. View Comparison
|
