On the understanding of software architecture

Hear the framework, I first think of a software system outline, like building a house to first to draw a design diagram, the shape of the house is what, the same I think the framework of software system is to achieve what kind of function, its interface layout is what, what functional modules. After touching the course "software Architecture", I learned that architecture is one or more structures of a software system. These structures are composed of software elements, externally visible attributes of the elements, and the relationships between those elements.

After reading the "Architecture Ramble" series, I learned that software architecture is more than just a software architecture, it is affected by many aspects, but also affects many aspects. "Architecture Ramble" proposes the framework is to solve the problem of the target system definition, the target system according to a principle of segmentation, and the segmentation of the part of the establishment of a communication mechanism, so that these parts can be organically connected to become a whole, complete the target system of all work. There are several answers to the explanation of the architecture. Everyone thinks they have understood the concept of architecture, but in fact is not very accurate, only know that the meaning, as to why there is no explanation.

For the abstract, I do not have a lot of knowledge, I feel that I can not imagine is abstract, and the subjective see is not the same is abstract. The "Architectural ramble" interprets the abstract meaning as merging the similar parts of different concepts into one new concept. This gives me a new understanding of abstraction.

The architecture solves the problem of people, knowing that it is the problem of solving people, it is easy to know what problems to solve. This requires an architect, who has always felt that the architect is a highly skilled position, what he does is to design the function of the system, design the overall style of the system. The "Architecture Ramble" suggests that a person who is only committed to accomplishing his or her job as the primary goal of his work is incapable of becoming an architect. To be an architect is to go beyond a fear that when you solve other people's problems on time to become your own problems, there will be time pressure, which will create a fear of time. Because there is fear, we will take various means to complete the work in time, in exchange for remuneration. It also suggested that the architect must be the leader of an organization, which I did not think of, I always thought that the architect is to report the architecture of the system to the leadership to organize the implementation of personnel, the architect as long as the technology can be, the other without the tube. It seems that architects have not only the technical requirements, but also the business areas are required.

The code also needs to be architected, and the "Architecture ramble" is divided into two responsibilities for dividing the code into units of deployment: The code that expresses the business logic and the code that provides access to the user and saves the result of running the business logic. For the second responsibility I don't quite understand, the feeling is not the user interface and so on code.

Always thought that the software architecture is only a technical problem, with the business does not have much relationship, the architecture is only the problem of software design, now it seems that their understanding has a lot of problems, there are many shortcomings.

On the understanding of software architecture