The realization of the main structure of the anti-pattern reading notes (II.)

1 Introduction

A professional planner (Jack) said that 20% of an engineer's time should be used for planning. As our experience increases, so does the belief in this assertion. Productivity and efficiency can be greatly improved by planning for good organizational work. Unfortunately, many corporate organizations are trying to formalize too many planning activities. Planning is most effective when driven and leveraged by individuals, and a key element of the time management expert's stress reduction is the planning to keep the activities of life in balance. With the maturation of this practice, the forms and methods of the time State system are becoming more and more personal.

2 Implementing the principal architecture

The characteristic of this anti-pattern is that the system in development lacks architecture specification. The architects who are generally responsible for the project have previous systems

Architectural experience, so the document is considered unnecessary. This excess of self leads to increased risk in key areas that affect the success of the system. For example, some areas below are often missing schema definitions:

1 including the use of language and library, coding standards, memory management, etc. in your software architecture and specifications.

2 includes the hardware architecture of the client and server configuration.

3 includes the communication Architecture of network protocol and equipment.

4 includes the persistence architecture of database and document processing mechanisms.

5 includes the thread model and the application security architecture of the trust system set.

6 system Management structure.

3 Consequences to bring

1 lack of architectural planning and specification: inadequate definition of software, hardware, communication, persistence, security, and system management architectures.

2 hidden risks caused by scale, domain knowledge, technology and complexity are exposed as the project progresses.

3 The project is going to fail or the system will not succeed because of insufficient performance, excessive complexity, requirements understanding errors, availability issues, and other system features. For example, approximately 1/3 of systems experience serious performance problems during development and operation.

4 Do not understand the new technology.

5 Lack of back-up technology and contingency planning.

4 Reasons for the emergence

1 NO risk management.

2 managers, architects or developers are too confident.

3 depends on past experience, which differs from reality in some key regions.

4 The gaps in the system design activity lead to implicit and unresolved architectural problems.

5 refactoring Scheme

Refactoring scenarios require systematic definition in an organized manner and rely on multiple views of the system. Each view models the system from the perspective of a system stakeholder, where the stakeholders may or may not be true, and may be the aggregation of individuals or a group of people. Each stakeholder is responsible for a set of priority issues, each representing the entire system and answering this critical question. These views include diagrams, tables, and specification descriptions that are connected to a guaranteed consistency. Generally speaking, a view is a lightweight description. The role of a schema document is to communicate architectural decisions and other solutions to problems. Documents should be easy to understand and maintain low cost.

Only people who have a complete understanding of an architecture can successfully define and implement it. However, this is often not the case, as many projects adopt new technologies that are not well understood. So building a good architecture from scratch is an iterative process that everyone should recognize. The initial reference architecture should have a strong strategy that can be implemented during development of the first product. You can then refine it incrementally using a future reference schema version and use the first product or new version to drive the process.

Detailed process as shown: