History of Enterprise Architecture
To learn any theory, I think the best way to get started is to explore its historical roots and development process, so as to clarify the true reasons for the theory, and to prevent readers from falling into the obscure vortex shared by various theories at first. Ultimately, even why the school is not clear. The same goes for learning about enterprise architecture and enterprise architecture framework theory. Enterprise architecture is a set of theories developed since the 1970s and 1980s. Many different theoretical frameworks for enterprise architecture have been derived during the development of these decades, and many large international companies and governments have In the process of repeated exploration, an enterprise architecture that meets their respective characteristics has been created, and the methodology on how to establish an enterprise architecture, the enterprise architecture framework, and the corresponding enterprise architecture tools have also been widely used in the industry.
As with many technologies, there is an interest in technology related to the integration of informatization, the sharing of information resources, and the conservation of resources. The organization that has sufficient resources to conduct research is always the military. In the mid-1970s, the United States launched the C4ISR program (Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance). The goal of this plan is not to establish the theory of enterprise architecture or enterprise architecture framework, but to establish a large and comprehensive system that can make the US military commanding authority make major strategic decisions and the commanders of the strategic forces implement their troops. The equipment, equipment and procedures used in command and control and management are linked together to form the nerve center of the modern US military. After a series of wars and the ups and downs of the war, the system has matured, and the methodology for constructing such a complex system that spans many fields has gradually become a system. Finally, during the Iraq war in 2003, the American military’s “enterprise structure” "Framework" has also been developed from the C4ISR AF (C4ISR Architecture Framework), which originally focused on serving the C4ISR system, to a more mature DoDAF, that is, the overall framework framework for informationization of the US Department of Defense.This process was long and full of twists and turns, during which many departments involved, as early as 1986, the US Defense Information Systems Agency/Center began to develop TAFIM (which is also the basis of TOGAF in the early 1995 edition), and by 1991 The first draft of the TAFIM was completed. The reference model was designed to guide the development of U.S. Department of Defense-wide applications using open systems and commercial market technologies. In June 1996, the US Department of Defense completed the TAFIM project. At the same time, the first edition of DODAF was released. The name was then called C4ISR AF until the official DODAF v1.0 was released in August 2003. The latest version is DODAF v2.0, released on March 28, 2009.
After the military developed such an enterprise architecture framework theory, the company also followed the military's footsteps and began to study the theory of enterprise architecture framework. In 1987, John Zachman, who also worked at IBM, wrote the famous paper "A Framework for Information Systems Architecture". Although the definition of the enterprise architecture and the enterprise architecture framework is not explicitly stated in this paper, he did put forward the concept of the "Information System Architecture Framework" for the first time, and he believed that a logical enterprise architecture blueprint was used to define and manage each enterprise. The integration of systems and components is very useful. In this paper, Mr. Zachman designed all the design elements required for the construction of an information system and the relationship between them by taking the building of a house in real life as an example and in a streamlined manner. This paper has also been regarded as the beginning of the enterprise architecture framework theory in the industry. Mr. Zachman himself is also known as the father of enterprise architecture framework theory.
The Zachman framework does not propose the concept of "enterprise architecture". The Clinger-Cohen law promulgated in the United States in 1996 required the US government's CIO to be responsible for the development, maintenance, and implementation of an inherited IT architecture. "ITA" is now being interpreted as the origin of the IT enterprise architecture, the concept of the Enterprise Architecture (EA), and it also opened the prelude to FEAF and FEA research. It can be said that the enterprise architecture was first applied to some U.S. government agencies, and the U.S. government has played an important role in promoting the application of enterprise architecture.
Actually, as early as this bill, several departments in the U.S. government began to study and build their own enterprise architecture. After introducing the Zachman framework into the U.S. government, the National Institute of Standards and Technology released the NIST framework in 1989. Since then, many frameworks have emerged within the federal government, such as DOD of the Ministry of Defense and the DOT of the Ministry of Finance. However, this state of war is not in line with the spirit of the enterprise architecture, because the federal government should create a corporate structure as a whole, so in September 1999, the Federal CIO Committee of the United States published the Federal Enterprise Architecture Framework (FEAF). In order to provide federal agencies with a common structure and implementation guide for the architecture, they help the federal agencies in the areas of public business processes, technology introduction, information flow, and system investment coordination.
In February 2002, the responsibility for building a federal enterprise architecture was transferred from the CIO committee to the OMB (US Government Office of Management and Budget), and it established a Federal Enterprise Architecture Program Management Office (FEA-PMO) to develop the federal enterprise architecture. (FEA) proposes the concept of a five-tiered reference model for cross-departmental analysis within the federal agency process and cross-institutional processes to find duplicate investments and find mutual gaps, thereby contributing to the scope of the federal government. Internal collaboration, interoperability, and interaction. The office launched the Enterprise Architecture Assessment Framework (EAAF, upgraded to 3.0 in 2008) in 2006 and launched the Federation Overarching Framework (FTF) the same year. In addition, around the use of the FEA reference model, the OMB also issued announcements such as announcements A-11 for budget preparation, submission and execution, and A-130 for federal information resource management. In particular, Exhibit 53 and Exhibit 300 in A-11 detail the matching and connection relationship between budget submission and FEA, making FEA an important tool for the federal government to find gaps, sharing, cooperation, and reuse opportunities among agencies. Look at China's e-government top-level design from FEA.)
In fact, in the first few years of the twenty-first century, the development of the Federal Enterprise Framework by the U.S. government was quite frustrating. According to the GAO (General Accounting Office) statistics in 2004, of the 96 departments surveyed, there were only 20 departments. The foundation for effective structure management has been established, and since 2001, 22 departments have improved their maturity, 24 departments have declined, and 47 departments have remained unchanged. And in January 2005, the GAO strongly condemned the failure of some U.S. government agencies to implement and use enterprise architecture well. This includes the FBI, the Department of Defense, the Department of Homeland Security, and NASA. However, with the passage of time, the development of FEA is indeed moving in a good direction. A survey conducted in 2007 showed that 19 out of the 24 departments under evaluation had achieved a satisfactory “green” rating, and compared to the previous year’s enterprises used for enterprise architecture assessment. The Architecture Assessment Framework (EAAF) has just been updated and the assessment criteria have become more stringent. From this we can see that the construction of enterprise architecture is a long and bumpy process.
After the rise of enterprise architecture from the United States federal government, the concept of enterprise architecture was quickly recognized by various consulting companies and research institutions. The earliest research institution for research on enterprise architecture was the Meta Group, which published the Enterprise Architecture Desk Reference in 2000. It provides a validated methodology for the implementation of enterprise architecture and looks forward to This builds a bridge across business strategy and technology implementation. Driven by these consulting and research institutions, Microsoft, IBM, Hewlett-Packard and other companies have also focused their attention on the enterprise architecture, hoping to position their products and services from the perspective of the enterprise. In 2005, a well-known consulting firm Gartner acquired Meta Group and started the development of the Gartner architecture framework. Prior to the merger, Gartner was already the most influential consulting firm specializing in CIO-level consulting, but in some specific areas of the enterprise architecture, the Meta Group was the most, and although Gartner is also committed to establishing some enterprise architecture Practice, but it is always not up to the level of the Meta Group.With the promotion of this background, the two eventually merged. After the merger, although it has become a legal entity, because of the huge differences in the methodologies of the enterprise architecture that they originally held, they spent a year seeking to integrate the existing enterprise architecture experience and methodology. The path eventually produced the Gartner framework.
With the continuous entry of governments, companies, consulting companies, research institutions, and manufacturers, the concept of enterprise architecture has become more and more popular, and its standardization work has become increasingly important, which has also spawned some research groups and standard frameworks. The most important and currently most influential enterprise architecture framework theory is TOGAF, founded by the Open Group. Since its development, TOGAF has released the 9.1th edition in 2011, TOGAF 9.1. In fact, the development of TOGAF has also undergone a long process. Since 1993, The Open Group has begun to customize the standards of enterprise architecture at the request of its customers. In 1995, under the permission and encouragement of the US Department of Defense, it released the first edition of TOGAF based on the Technical Architecture Framework for Information Management (TAFIM). TAFIM himself officially retired from the Ministry of Defense in 1998.After several years of development, The Open Group released TOGAF 7 (Technical Edition) in December 2001 and TOGAF 8 (Enterprise Edition) in December of the following year. After a long period of tinkering, more significant changes took place in 2009, TOGAF 9, which added important content such as the Content Framework to TOGAF 8 to complete the TOGAF standard. Today, TOGAF has become the industry's most popular enterprise architecture framework standard. Not only is 80% of Forbes' global top 50 companies in use, but it also supports open, standard SOA reference architectures. In addition, international mainstream manufacturers are also actively promoting the popularization of this standard. For example, SAP is being promoted in Germany, IBM, Hewlett-Packard and Oracle are promoting in the United States.
As with many technologies, there is an interest in technology related to the integration of informatization, the sharing of information resources, and the conservation of resources. The organization that has sufficient resources to conduct research is always the military. In the mid-1970s, the United States launched the C4ISR program (Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance). The goal of this plan is not to establish the theory of enterprise architecture or enterprise architecture framework, but to establish a large and comprehensive system that can make the US military commanding authority make major strategic decisions and the commanders of the strategic forces implement their troops. The equipment, equipment and procedures used in command and control and management are linked together to form the nerve center of the modern US military. After a series of wars and the ups and downs of the war, the system has matured, and the methodology for constructing such a complex system that spans many fields has gradually become a system. Finally, during the Iraq war in 2003, the American military’s “enterprise structure” "Framework" has also been developed from the C4ISR AF (C4ISR Architecture Framework), which originally focused on serving the C4ISR system, to a more mature DoDAF, that is, the overall framework framework for informationization of the US Department of Defense.This process was long and full of twists and turns, during which many departments involved, as early as 1986, the US Defense Information Systems Agency/Center began to develop TAFIM (which is also the basis of TOGAF in the early 1995 edition), and by 1991 The first draft of the TAFIM was completed. The reference model was designed to guide the development of U.S. Department of Defense-wide applications using open systems and commercial market technologies. In June 1996, the US Department of Defense completed the TAFIM project. At the same time, the first edition of DODAF was released. The name was then called C4ISR AF until the official DODAF v1.0 was released in August 2003. The latest version is DODAF v2.0, released on March 28, 2009.
After the military developed such an enterprise architecture framework theory, the company also followed the military's footsteps and began to study the theory of enterprise architecture framework. In 1987, John Zachman, who also worked at IBM, wrote the famous paper "A Framework for Information Systems Architecture". Although the definition of the enterprise architecture and the enterprise architecture framework is not explicitly stated in this paper, he did put forward the concept of the "Information System Architecture Framework" for the first time, and he believed that a logical enterprise architecture blueprint was used to define and manage each enterprise. The integration of systems and components is very useful. In this paper, Mr. Zachman designed all the design elements required for the construction of an information system and the relationship between them by taking the building of a house in real life as an example and in a streamlined manner. This paper has also been regarded as the beginning of the enterprise architecture framework theory in the industry. Mr. Zachman himself is also known as the father of enterprise architecture framework theory.
The Zachman framework does not propose the concept of "enterprise architecture". The Clinger-Cohen law promulgated in the United States in 1996 required the US government's CIO to be responsible for the development, maintenance, and implementation of an inherited IT architecture. "ITA" is now being interpreted as the origin of the IT enterprise architecture, the concept of the Enterprise Architecture (EA), and it also opened the prelude to FEAF and FEA research. It can be said that the enterprise architecture was first applied to some U.S. government agencies, and the U.S. government has played an important role in promoting the application of enterprise architecture.
Actually, as early as this bill, several departments in the U.S. government began to study and build their own enterprise architecture. After introducing the Zachman framework into the U.S. government, the National Institute of Standards and Technology released the NIST framework in 1989. Since then, many frameworks have emerged within the federal government, such as DOD of the Ministry of Defense and the DOT of the Ministry of Finance. However, this state of war is not in line with the spirit of the enterprise architecture, because the federal government should create a corporate structure as a whole, so in September 1999, the Federal CIO Committee of the United States published the Federal Enterprise Architecture Framework (FEAF). In order to provide federal agencies with a common structure and implementation guide for the architecture, they help the federal agencies in the areas of public business processes, technology introduction, information flow, and system investment coordination.
In February 2002, the responsibility for building a federal enterprise architecture was transferred from the CIO committee to the OMB (US Government Office of Management and Budget), and it established a Federal Enterprise Architecture Program Management Office (FEA-PMO) to develop the federal enterprise architecture. (FEA) proposes the concept of a five-tiered reference model for cross-departmental analysis within the federal agency process and cross-institutional processes to find duplicate investments and find mutual gaps, thereby contributing to the scope of the federal government. Internal collaboration, interoperability, and interaction. The office launched the Enterprise Architecture Assessment Framework (EAAF, upgraded to 3.0 in 2008) in 2006 and launched the Federation Overarching Framework (FTF) the same year. In addition, around the use of the FEA reference model, the OMB also issued announcements such as announcements A-11 for budget preparation, submission and execution, and A-130 for federal information resource management. In particular, Exhibit 53 and Exhibit 300 in A-11 detail the matching and connection relationship between budget submission and FEA, making FEA an important tool for the federal government to find gaps, sharing, cooperation, and reuse opportunities among agencies. Look at China's e-government top-level design from FEA.)
In fact, in the first few years of the twenty-first century, the development of the Federal Enterprise Framework by the U.S. government was quite frustrating. According to the GAO (General Accounting Office) statistics in 2004, of the 96 departments surveyed, there were only 20 departments. The foundation for effective structure management has been established, and since 2001, 22 departments have improved their maturity, 24 departments have declined, and 47 departments have remained unchanged. And in January 2005, the GAO strongly condemned the failure of some U.S. government agencies to implement and use enterprise architecture well. This includes the FBI, the Department of Defense, the Department of Homeland Security, and NASA. However, with the passage of time, the development of FEA is indeed moving in a good direction. A survey conducted in 2007 showed that 19 out of the 24 departments under evaluation had achieved a satisfactory “green” rating, and compared to the previous year’s enterprises used for enterprise architecture assessment. The Architecture Assessment Framework (EAAF) has just been updated and the assessment criteria have become more stringent. From this we can see that the construction of enterprise architecture is a long and bumpy process.
After the rise of enterprise architecture from the United States federal government, the concept of enterprise architecture was quickly recognized by various consulting companies and research institutions. The earliest research institution for research on enterprise architecture was the Meta Group, which published the Enterprise Architecture Desk Reference in 2000. It provides a validated methodology for the implementation of enterprise architecture and looks forward to This builds a bridge across business strategy and technology implementation. Driven by these consulting and research institutions, Microsoft, IBM, Hewlett-Packard and other companies have also focused their attention on the enterprise architecture, hoping to position their products and services from the perspective of the enterprise. In 2005, a well-known consulting firm Gartner acquired Meta Group and started the development of the Gartner architecture framework. Prior to the merger, Gartner was already the most influential consulting firm specializing in CIO-level consulting, but in some specific areas of the enterprise architecture, the Meta Group was the most, and although Gartner is also committed to establishing some enterprise architecture Practice, but it is always not up to the level of the Meta Group.With the promotion of this background, the two eventually merged. After the merger, although it has become a legal entity, because of the huge differences in the methodologies of the enterprise architecture that they originally held, they spent a year seeking to integrate the existing enterprise architecture experience and methodology. The path eventually produced the Gartner framework.
With the continuous entry of governments, companies, consulting companies, research institutions, and manufacturers, the concept of enterprise architecture has become more and more popular, and its standardization work has become increasingly important, which has also spawned some research groups and standard frameworks. The most important and currently most influential enterprise architecture framework theory is TOGAF, founded by the Open Group. Since its development, TOGAF has released the 9.1th edition in 2011, TOGAF 9.1. In fact, the development of TOGAF has also undergone a long process. Since 1993, The Open Group has begun to customize the standards of enterprise architecture at the request of its customers. In 1995, under the permission and encouragement of the US Department of Defense, it released the first edition of TOGAF based on the Technical Architecture Framework for Information Management (TAFIM). TAFIM himself officially retired from the Ministry of Defense in 1998.After several years of development, The Open Group released TOGAF 7 (Technical Edition) in December 2001 and TOGAF 8 (Enterprise Edition) in December of the following year. After a long period of tinkering, more significant changes took place in 2009, TOGAF 9, which added important content such as the Content Framework to TOGAF 8 to complete the TOGAF standard. Today, TOGAF has become the industry's most popular enterprise architecture framework standard. Not only is 80% of Forbes' global top 50 companies in use, but it also supports open, standard SOA reference architectures. In addition, international mainstream manufacturers are also actively promoting the popularization of this standard. For example, SAP is being promoted in Germany, IBM, Hewlett-Packard and Oracle are promoting in the United States.
References:
- Visual Paradigm - TOGAF ADM guide-through
- The Open Group
Comments
Post a Comment