Enterprise Architecture ea

The EA concept was generated in 1987 in an article published in an internal IBM publication "A Framework for information Systems Architecture" by J.a Zachman, The concept is presented in response to increasingly complex IT systems, as well as high investment and low return issues. 20 years on, we're facing more complex IT system and architecture planning issues, as Roger Sessions mentioned, if you're just trying to build a small house on a small island, you don't need to do a master plan, but you're going to build a new York city, No master plan is necessarily unsuccessful.

A complete it plan includes three levels, one is the IT strategic level of planning, one is the IT architecture level of planning, and then another is it information system level planning, what is the relationship between these layers? It strategy mainly demonstrates the relationship between business strategy and it construction, and demonstrates the business value of it, and the structure is to make a more detailed description of it's concrete construction objectives and vision, and to refine it from data and application systems. Another aspect is that the IT infrastructure architecture includes standards and specifications related to the network platform, software platform, system management and development, and it architecture is based on the business architecture, that is, the business strategy to have a business it process system, the business structure is clear after the work out.

EA is a holistic planning solution that puts together business architecture and it architecture, and is driven by business architecture to do it architecture. After the architecture has been completed, the entire architectural blueprint is decomposed into a series of projects, defining requirements at the project level, specific design at the system level, and then implementing it, which is a complete it plan. The overall structure of the enterprise, including the business structure of the enterprise, the information technology architecture of the enterprise, the data application and the infrastructure, are all based on the strategic guidance of the enterprise. Today's more popular architectures include:

Figure 1. Different EA models in various literatures


feaf--U.S. Federal Enterprise Architecture Framework (Federal Enterprise Architecture Framework) teaf--US Treasury Enterprise Architecture Framework (Treasury Enterprises Architecture Framework) dodaf--United States Department of Defense Architecture Framework (Department of Defense Architecture framework) nascio--The National Association of Interstate CIOs Association of state Chief Information officers

Zachman's architectural framework model, Zachman, is IBM's chief architect, who, in the late 80 to the early 90, has already standardized the framework model for the entire IT architecture, which can be viewed from two dimensions, one landscape, one portrait, and the horizontal dimension as data, function, The network, the human factor, the driving force of the business; The vertical factor is the hierarchy of the architecture, such as the planning layer, the concept layer, the logical layer, the physical design, and the specific refinement criteria. Based on the entire architecture of the Zachman, it is now the target. International has extended a lot of different industry architecture models, the U.S. military, the Ministry of Defence, the Ministry of Finance, the Ministry of Commerce have their own concrete architectural model.

Roger Sessions's article describes some of his ideas for today's more popular class four EA architectures (A Comparison of the Top four enterprise-architecture methodologies). You can read that he has not improved on these systems to adapt to today's system, and put forward some of the ideas of the fall generation.