Framework, architecture, model, and Reconstruction

Some concepts have been mentioned.

There are many frameworks, various, different platforms, different languages, and different functions.
Currently, almost all software projects use the framework. What is the framework and why it should be used.
The so-called framework is a visible software product and a semi-finished product. Since he is a product, he should have been there. If you want to, you can use him. Just like a five-story building with half of construction, beams and columns, floors and simple stairs, you can climb the stairs and exercise as long as you want. But he is a semi-finished product, which means that he is incomplete and needs to be filled in. These blank items determine what the "finished" is. Buildings that have just exercised can become office buildings or houses according to different la S and decorations. Because of the reproducibility of software, the commonality of most buildings can be extracted. On this basis, a relatively small amount of construction can meet the needs of the market and improve the production efficiency of software.
Likewise, due to software reproducibility and frameworkCodeIt is often a long time of accumulation and practical testing, with a high quality. The building I mentioned above ensures that the height of each floor is the same, and the structure can withstand magnitude 8 earthquakes. As long as the construction is based on this structure, no matter how many people work together, the house will not have this problem, whether you understand engineering mechanics or not. Therefore, the software quality is improved, the development difficulty and risks are reduced, the possibility of team development is enhanced, and the cost of construction personnel is reduced. This is the second.
The Framework has inherent limitations. If you want to build a national stadium on the foundation of the building, there is certainly no possibility. If you just want to unload Daliang, it may not be far from the news and reports. Therefore, the framework should be appropriate, and the use of the framework should also follow the idea of the original framework designer. Third.

The architecture is about the software architecture. It is an idea that you cannot see. There is no one-to-one product. He is a kind of thought summarized in practice that guides how to design software to meet certain requirements.
You need to build a two-storey small house. It is simple. Just add some nice wood and a few car bricks. The Brick and wood structure will work. Three to four layers? Brick-and-mortar structure. Layer 5 to layer 15? Steel-concrete structure. Layer 15 to layer 40? All steel structures. More than 40 layers? That's complicated. Ask experts for help.
The architecture is abstract, and he points out the general direction in a general scenario. In the Framework Design, one or more architectural ideas are always applied.

What about the mode? It is a solution that can be practiced repeatedly to solve a certain problem in a certain range of scenarios. High-rise Buildings with elevators. Make the room bright and have floor-to-ceiling windows. These enable us to have a perfect solution in some scenarios without making great efforts to think about it. It's like a mathematical formula.
In the Framework, the structure may be very complex, and too many problems need to be solved in the middle. Therefore, in the Framework Design, there are usually a lot of applications to the mode.

This is complicated. You do not have to take all the details into account before starting the project. Some unreasonable aspects of the current structure were found during the construction process. I didn't think about which door to use before building the building. I should cover it first. When I started loading the door, I found that every room door was built by myself. The cost was high and the effect was poor. So a Senior said: Don't be so troublesome. Call XXX factory to provide them with various specifications of a series of doors, door-to-door delivery, package installation, and warranty. Well, refactoring is the process of eliminating the odor in the software during the design process so that it conforms to a certain design pattern.