Background of Enterprise Architecture (EA)

-
With the extensive and in-depth penetration of information technology, the level of social informatization in countries around the world continues to increase, and human society is accelerating into the information society. In this wave of rapid development of information, all kinds of economic and social activities are accelerating transformation. Whether it is production tools, production objects, or business management methods, or even people's lifestyles, the value of information technology is getting higher and higher. Whether it is the management of a company, the management of a government department, or even the management of an entire country, the virtual information-based management model is becoming more and more common and deeper and deeper. Information management brings about a kind of "fine, parallel and transparent" management. At the national level, it will mean a new kind of e-government management model. Informatization and e-government have become the trend of the times and cannot be stopped. However, in the process of deepening informatization and e-government, we have to face a large number of difficulties and problems that need to be resolved urgently. Such as a large number of repeated construction and waste; a large number of information islands and chimneys; a large number of reversals and failures, as well as a large number of investment black holes and traps. Informatization and e-government are not just simple applications of information technology, but more importantly, economic and social transformation. This transformation is a long-term process. We need a systematic methodological guidance.The EA (Enterprise Architecture) methodology was born under this background and developed rapidly. At present, there is no unified Chinese translation. The main EA translations are enterprise architecture, architecture, and entity architecture. It is an issue that defines the development of the enterprise from an overall perspective. EA presents the internal structure and relationships of the enterprise from the perspectives of business, data, applications, and technologies, so that stakeholders can make effective efforts on how to build a borderless information flow capability. A discipline of decision-making.

In 1987, Zachman proposed the first architectural framework at the system architecture level, the Zachman framework. The Zachman framework later developed into a classic framework for EA, and Zachman himself is also known as the father of EA. Since then, EA's framework and methodology have been constantly proposed. Currently, the EA framework and methodologies that have a relatively large impact and are widely used are TOGAF, FEA, Zachman, and DoDAF.

References:

Comments

Post a Comment

Popular posts from this blog

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 t...
Read more

Enterprise Architecture - Organizational Roles and Skills

-
Image
Scrum development will have three roles: PO, Scrum Master, and Development Team. What are the roles of the development enterprise architecture? What skills are required for each role to be able to take on the work of the architecture? This article describes the role and skill requirements in architecture development so that everyone knows who will do it when implementing TOGAF and what skills need to be improved or improved. Software development management is more complicated, and the development and management of the architecture is more complicated. Since there is no specific practice yet, for the time being there is no in-depth understanding and refinement of these contents. The following describes most of the framework capabilities framework from TOGAF . Emerging corporate architect role The role of the enterprise architect is described in TOGAF or Non-TOGAF: Extending Enterprise Architecture over RUP . Enterprise architects are thought leaders, visionaries, and industry ...
Read more

Enterprise Architecture Design Methodology - TOGAF

-
Image
The ADM method is composed of a set of stages arranged in a ring according to the architecture development order of the architecture field. Through these development stages, the designer can confirm whether or not the complex business requirements have been fully discussed. One of the most famous ADM infrastructure diagrams in TOGAF is as follows: The ADM method is applied iteratively throughout the architecture development process, between phases, and within each phase. In the entire life cycle of ADM, each phase needs to confirm the design results based on the original business requirements. This also includes some unique stages in the business process. Confirmation work requires review of the company's coverage, time frame, level of detail, plan, and milestones. Each stage should take into account the reuse of architectural assets (formerly ADM iterations, other frameworks, system models, industry models, etc.). Photo source: TOGAF management tool from Visual Paradig...
Read more