Shulou(Shulou.com)06/03 Report--

What this article shares with you is about what the framework is. The editor thinks it is very practical, so I share it with you to learn. I hope you can get something after reading this article. Let's take a look at it with the editor.

A Framework is a set of collaborative classes that make up a specific class of software reusable designs. The framework defines the architecture of your application, defining the overall structure, the division of classes and objects, the main responsibilities of each part, how classes and objects work together, and controlling processes.

The framework predefines these design parameters so that the application designer or implementer can focus on the specific details of the application itself.

Why use frames?

Because the development of the software system has been very complex today, especially the server-side software, involving too much knowledge, content, problems. Using someone else's mature framework in some ways is tantamount to asking others to help you with some basic work, and you just need to focus on the business logic design of the system. And the framework is generally mature and robust, it can deal with many details of the system, such as transaction processing, security, data flow control and so on. And the framework is generally used by a lot of people, so the structure is very good, so the scalability is also very good, and it is constantly upgraded, you can directly enjoy the benefits of other people's code upgrade.

The framework is generally in the middle layer between the low-level application platform (such as J2EE) and the high-level business logic.

Why should the software be layered? To achieve "high cohesion and low coupling". Divide the problem into individual solutions, easy to control, easy to extend, easy to allocate resources. Anyway, it's a lot of good.

Framework and design patterns

The two concepts of framework and design pattern are always easy to be confused, but there are differences between them. The component is usually code reuse, while the design pattern is design reuse, and the framework is somewhere in between, part of the code reuse, part of the design reuse, and sometimes the analysis can be reused. There are three levels of reuse in software production: internal reuse, that is, abstract blocks that can be used publicly in the same application; code reuse, which combines common modules into libraries or toolsets that can be used in multiple applications and domains; reuse of application frameworks, that is, providing a general or off-the-shelf infrastructure for dedicated domains to achieve the highest level of reuse.

Although the framework is similar to the design pattern, it is fundamentally different. A design pattern is a description of a recurring problem in an environment and a solution to the problem. It is more abstract than the framework. The framework can be represented by code, or it can be directly executed or reused, while for patterns, only instances can be represented by code; design patterns are smaller elements than the framework, and a framework often contains one or more design patterns. The framework is always aimed at a specific application domain, but the same pattern can be applied to a variety of applications. It can be said that the framework is software, and design patterns are software knowledge.

Framework development

The biggest advantage of the framework is reuse. The biggest reuse way of object-oriented system is framework, and a large application system may be composed of multi-tier cooperative framework.

Because the framework can reuse code, it is very easy to build applications from an existing component library, because the components use the interface uniformly defined by the framework, which makes the communication between components simple.

The framework can reuse design. It provides reusable abstract algorithms and high-level design, decomposes large systems into smaller components, and describes the internal interfaces between components. These standard interfaces make it possible to build a variety of systems through assembly based on existing components. As long as the interface definition is met, the new component can be inserted into the framework, and the component designer can reuse the design of the architecture.

The framework can also reuse analysis. If all personnel analyze the transaction according to the idea of the framework, then it can be divided into the same components and adopt similar solutions, so that analysts using the same framework can communicate with each other.

Main features

Good consistency of software structure in the domain; establish a more open system

The reuse code has been greatly increased, and the software production efficiency and quality have also been improved.

Software designers should focus on the understanding of the domain and make the requirement analysis more sufficient.

Experience is stored to allow experienced people to design frameworks and domain components without being limited to low-level programming

Allow rapid prototyping technology

It is convenient for multiple people to work together in a project.

The heavy reuse reduces the average development cost, accelerates the development speed, reduces the number of developers and reduces the maintenance cost, while the parameterized framework enhances the adaptability and flexibility.

The above is what the framework is, and the editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.