A ramble on software architecture--reading sense

in my opinion, software architecture is the skeleton of a software, and then the code to fill the flesh. Obviously my knowledge is quite superficial, and I stay on the surface to understand the meaning of Chinese. So how do you understand software architectures and use software architectures?

(1) architecture is based on human social (people-oriented) and a division of labor to improve the productivity of the purpose (the nature of the problem) and a combination of processing and merging links. My understanding is that the division of labor is the module, the merger is the Assembly, the linkage is the assembly method.

(2) to do a good job in architecture, first of all, the concept of a correct understanding. That is, through the phenomenon of nature to solve the problem.

(3) Understand "who is the problem, what is the problem". The first is to determine the subject of the concept, because the subject is different, the understanding is different, as the user and the technician to the idea of dealing with the problem is not the same. The starting position determines whether the whole process is meaningful, so the discovery and determination of the nature of the problem is more important than solving the problem, and the identification problem often distinguishes between the solution and the problem itself, which needs to be traced back.

(4) in order to better achieve the goal, that is to get a higher productivity, higher personal interests, naturally produced a personal weaknesses, groups rely on a phenomenon of cooperation, that is, segmentation. Segmentation is the continuous movement of the system within the time, adjusted to the time parallel, spatial scale of the tree-like results, so that more reasonable use of time and labor. The lower the number of layers, the more conducive to communication, the higher the efficiency.

(5) software is used to simulate people and society. Then provide a lower cost, more efficient life. The Software engineer's task is too heavy, the splitting forms the software architecture,

(6) regarding the software architecture, it involves the business system of the software itself and the virtual business system. According to (3), the subject of the problem should be identified first, the problem has business problems and computer problems in two directions. Organizational structure should consider the role of participation, loss of information transmission, coordination between roles. Software is constantly split to form hardware architecture, code architecture, development system (participant) architecture.

The main steps of the virtualization business: Learning the business knowledge, recognizing the core interests of the business, modeling the business, and implementing it with code, learning how the business stakeholder to deal with the business, accomplishing everyone's work, and persisting the results of business operations.

(7) The architect is confident enough to overcome the fear of time pressure, to solve other people's problems, and to fulfill other people's work as their best interests. The architect is to balance the interests of others in order to achieve the balance of others ' duties in order to achieve the overall benefit of the leader. As an architect, there is more ability than others, first of all, language and technology is the basic handy tool, followed by the discovery of problems, problem solving, balance ability management ability.

(8) The code is responsible for code that expresses the business logic and reads the code that the user provides access to and saves the results of the business logic run. Code of the architecture: Software code related stakeholders Service-user requirements, Glue code-combination of calls, business-realize the core model of the business, repository-data preservation. The service is split into Service,glue code Repository. Other than business, there can be no logic, that is, a single sequential call, can not continue to split.

(9) Business is the premise of technology existence, the complex development of technology, split into a framework.

Conclusion: Learning software architecture mainly lies in solving the problems in nature, in order to obtain the greatest benefit, and how to form a reasonable structure.

A ramble on software architecture--reading sense