Software Evolution-Enterprise Application Software Architecture Maturity Model Software Enterprise infrastructure

As an industry, application software development has been developing for more than 30 years. However, it may be complicated or invisible to software, but it is still in the original production mode of manual workshop, development relies on a large amount of manpower, making it difficult to ensure the quality and high cost of use and O & M.

There are many reasons for this situation, but I think the most fundamental reason is not management, but lack of scientific understanding of the rational construction of application software, no standards or specific products have been set up for the enterprise application architecture. We analyze all industrial products in human society. They all have a unified and unified structural standard framework, such as automobiles, including power systems, walking systems, control systems, and bearer spaces, however, when we analyze the history of automobile development, we will find that it has gradually evolved from a rough and primitive model to a complete and scientific structure. In the early days, there were no simple necessary components such as wipers.

A system structure and structure are the most critical. Ignoring the software structure, it is difficult to do a good job of software only when talking about management. Just like an automobile company has an advanced management system, but I don't know what a car should look like. This cannot be a good car manufacturing company. I only care about the CMM-Capability Maturity Model for software, it is impossible to become a good software enterprise regardless of the software scientific structure.

Therefore, this paper discusses the Scientific Construction of application software and establishes the software architecture Maturity Model.Amm-Architecture Maturity Model for software is more important and fundamental for software enterprises. To export the scientific software architecture, we need to study the Software Evolution Process and analyze the software's evolution direction,OKBasic structure and architecture of advanced software systemsIn this way, we can establish an architecture Maturity Model. Under the correct direction, we can move in the correct direction. I think that, just as high-level mammals have basically the same structure (for example, mice and elephants all have mouths, eyes, noses, ears, and six organs and limbs, the structure of advanced software systems must be homogeneous. If we can establish such an architecture, it is easy to compile specific applications on this basis.

I thought AMM was a concept independently invented by myself. As early as 1987, J. a. zachman published "a framework for information systems architecture" in an internal publication of IBMArticleFor the first time, the Enterprise Architecture EA-Enterprise Architecture concept was proposed. It is unclear when eamm was created. However, eamm basically divides the maturity of EA into six levels based on the CMM classification method:

EA level 0-no program

EA Level 1-informal Program

EA Level 2-repeatable Program

EA Level 3-well-defined Program

EA Level 4-managed Program

EA Level 5-continuously improving vital program