Software Architecture (i)

Software architecture

What is it, why, what, what, classic three-paragraph theory, also applicable to software architecture

Software Architecture:

First of all, according to the actual problem to be solved, the boundary of the target system is clearly defined.

Secondly, the choice of suitable system, suitable for the actual situation of the principle, according to the specific principles of the System Division, is so-called no rules inadequate surrounding area.

Then, after the system according to a principle division, become fragmented, need to establish a certain communication mechanism.

Finally, according to the communication mechanism, the organic combination of the various parts to complete the work of the target system.

In short, it is a process of principle, mechanism, piecemeal, peers of the system. Among them, the principle of infiltration, mechanism is the value of the structure.

Why should there be a software architecture?

In the process of creating software, due to the constraints of manpower, material resources, time and other factors, will produce a variety of expected and unexpected situation, in order to better solve these conditions, we need certain norms and guidelines to work to assist, so the software architecture has its existence of necessity.

What sort of software architecture does it have?

Decision-making & Composition Faction

Composition Faction:

The architecture of the software system describes the system as the interaction between the computer building and the components

Characteristics:

1, focus on the object of the framework practice----software, the software itself as the description object.

2, analysis of the composition of the software, that is, the components of the different computing tasks, these components through mutual interaction to complete a higher level of computing tasks.

The decision-making faction:

The software architecture contains important decisions about the organization of software systems, the structure elements and their interfaces that make up the system, the behavior that these elements embody when collaborating, how to organize these elements so that they are synthesized into larger systems, and to guide the architectural style of the system organization.

Characteristics:

1, focus on the main body of the framework practice----people, people's decision-making as a descriptive object.

2, summed up the type of framework decision-making, and pointed out that the framework decision-making includes not only the organization, elements, subsystems and architectural styles of the software system, but also the decision of many non-functional requirements.

So, with the most basic understanding of architecture, what should be done next?

Understand!

Because there are all kinds of unpredictable and unexpected things in reality, what we can do is to accept and understand them first, then we can solve them according to our own ideas. Therefore, the necessary understanding of the ability to be able to have.

In addition, things are often not full of concrete image, encounter abstract problems need a comprehensive and specific understanding, when you need to make abstract summary or summary, the precondition is to have a full understanding of something.

Lack of good understanding ability, will inevitably lead to the result of the generalize, that is, the software architecture embodied lost it should be correct, lost the correctness of the software architecture has lost its existence of necessity.

Software Architecture (i)