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

This article will explain in detail what is the rapid development framework on the Internet. The editor thinks it is very practical, so I share it for you as a reference. I hope you can get something after reading this article.

What is a rapid development framework?

Preface

As a programmer, in the process of development, we will find that there is a framework and no framework, doing things is a completely different concept, related to the efficiency of development, program robustness, performance, teamwork, follow-up function maintenance, expansion. Wait for everything. Many friends are learning to build their own frameworks, and many companies are creating or using their own frameworks. There are so many open source frameworks online, and I don't know how many new frameworks are launched every year. And keep repeating the wheels, but also let more friends shotgun change guns, run faster and faster, work more and more efficient. So what is a rapid development framework?

What is a rapid development framework?

The rapid development framework is the reusable design of the whole or part of the system, which is represented by a set of abstract components and the method of interaction between component instances; another definition is that the framework is an application that can be customized by application developers. The former is defined from the aspect of application while the latter is defined from the aspect of purpose.

It can be said that a rapid development framework is a reusable design component, which defines the architecture of the application, clarifies the dependency relationship, responsibility distribution and control flow among the whole design and collaborative components, and represents a set of abstract classes and the methods of cooperation between their instances, which provides a Context relationship for component reuse. Therefore, the large-scale reuse of component libraries also requires a rapid development framework.

The application rapid development framework refers to the underlying service that realizes the general and complete functions in a certain application field (excluding the parts of special applications). Programmers using this framework can start specific system development on the basis that a common function has been implemented. The framework provides a collection of classes that apply the desired default behavior. Specific applications support application-specific behavior by rewriting subclasses (which are the default behavior of the framework) or assembling objects.

Rapid development framework, that is. To put it simply, it is to use the stage set up by others, and you perform. Moreover, rapid development frameworks are generally mature, constantly upgrading and updating software

To put it simply, the software development framework can be understood as a reinforced concrete structural frame made of beams, columns and load-bearing walls when we build a building. The software functions are like different types and functions of houses to be realized in this rapid development framework, such as parking lots, shopping malls, hotels, restaurants, commercial housing.

If the framework with powerful function and solid structure can carry more types, its applicability will be stronger.

No matter what the development framework is, it is created for different business functions. A good rapid development framework can improve the competitiveness of enterprises, including reducing development costs, improving product quality, improving customer satisfaction, controlling development progress, and so on. At the same time, the rapid development framework is also the accumulation of knowledge in a certain field to achieve a certain business, it is a continuous activity, created with the implementation of specific business functions, and survive out of the software development cycle. A mature rapid development framework is not just code, it not only implements the basic functions of a certain field of business in the way of code, but also must write corresponding documents, models, flow charts, data dictionaries, development and usage instructions. And so on a series of documents to support, such a rapid development framework is more mature and robust.

Why use a rapid development framework

If you develop it from scratch every time, it will be a long time, and it may not be able to do it well. In team collaborative development, there is no unified standard, everyone writes their own, and the same repetitive functions are everywhere. Because there is no unified calling specification, it is difficult to understand the code written by others, and there is no way to start when there is Bug or secondary development and maintenance. (for the dark days without a frame, please see the previous chapter.)

And a mature rapid development framework, it is templated code, it will help us to achieve a lot of basic functions, we only need to concentrate on the implementation of the business logic. And many of the underlying functional operations, we can completely do not have to do too much consideration, rapid development framework has helped us to achieve. In this case, the development efficiency of the whole team can be imagined. In addition, don't worry too much about the changes in team members. The code specification of the rapid development framework makes it easy for us to understand the code written by other developers.

When building a rapid development framework, how do we position

Is it true that the extensibility, transferability, and functionality of the rapid development framework are the better?

Personally, I think we should look at it according to the specific situation in the actual development, because the more comprehensive the function, the greater the complexity, the higher the developer's ability and skills will be required, and the cost will be the greatest. For example, to make an undeveloped e-commerce network and want to make the system like JD.com, directly using JD.com 's sub-modular distributed framework to develop, then how to form this team? Not to mention development costs. Even if the team has the ability to do it, it is not necessary to do so, because in terms of cost budget and development cycle, it is more likely that the company will be dragged down before the project is completed.

Generally speaking, a small and medium-sized project with a development team of about 1 to 5 people can use a general three-tier structure without having to think about whether the framework should be divided into three or five layers, how to decouple each layer, and what design patterns should be used. Because of today's rapid development of the Internet era, fast is the king, to do a small and medium-sized project can be completed in a week, must not be delayed for a month to finish. As for extended functions, interfaces, distributions, concurrency, big data. In fact, it is not a good thing to think too much too early. Experienced programmers have already left extension plans or ideas when writing this rapid development framework, and developers who have not reached this level may not understand no matter how much you want to do. It is better to do it first and then slowly learn and upgrade the framework slowly.

Because the framework is not developed and will no longer change, it also needs to be constantly upgraded to integrate the new knowledge and technology you have learned into the framework to make it more powerful and robust. As for the rapid development framework that you can't control, after team development and production environment, you will find that there are a lot of pits waiting for you to landfill. this framework can only be used to practice first, and then slowly improve when you have time.

The rapid development framework expands slowly through small steps and continuous iterative upgrades, and when the project is in the production environment, it keeps adjusting according to the new requirements and problems encountered, and finally becomes more and more powerful. All frameworks are from version 1.0 to 2.0, 3.0. Evolved instead of skipping the initial version to the final mature version.

So when we create a framework, we must decide the final design scheme of the framework to be developed according to our current individual technical capability, team successful technical level, time, input cost, project status (scale and demand complexity), and future development prospects. Of course, it is not to say that it cannot be achieved in one step, and the world is as big as it is. As long as the individual ability and team ability match, the boss has a strong capital cost and plenty of time, and there is no problem directly using the super framework for large projects.

Main features and requirements of rapid development framework

1. Code templating

Rapid development framework generally has a unified code style, the same layer of different types of code, are more or less the same template structure, easy to use template tools to generate unified, reduce a large number of repetitive code writing. When learning, as long as you understand a representative class of a certain layer, it is tantamount to understanding most of the other class structures and functions of the same layer, and it is easy to start. Different people in the team use the same calling style for coding, which greatly improves the readability of the code and facilitates maintenance and management.

2. Reuse

Rapid development framework is generally clear, different developers will be put in the same location according to specific functions, coupled with the corresponding development documents, code reuse will be very high, what functions you want to call go directly into the corresponding location to find the relevant functions, instead of each developer writing the same set of methods.

3. High cohesion (encapsulation)

The functions in the rapid development framework will achieve high cohesion, and developers encapsulate various required functions in different layers for everyone to call, and when calling, you do not need to know if these methods are implemented. You just need to pay attention to whether the output is what you want.

4. Norms

When developing the rapid development framework, we must strictly implement the code development specification requirements, such as naming, annotation, architecture layering, coding, document writing and so on. Because you are not the only one to use the framework you have developed, it is very important to make it easier for others to understand and grasp.

5. Scalable

Or do you need to tear down the entire framework and redevelop it?

6. Maintainable

A mature rapid development framework should be very convenient for secondary development or maintenance of existing functions. For example, if a project wants to add, modify or delete a field or related function, it only needs a simple operation, which can be done in more than ten minutes or without too much effort. Add a data table and corresponding functions, which can also be completed quickly. Changes in functions will not adversely affect the system. There is no hard coding and so on to ensure the production efficiency and quality of software development.

7. Collaborative development

With the rapid development framework, we can organize large and small teams to better carry out collaborative development. A mature framework will greatly reduce the difficulty of project development, speed up development, reduce development costs, and reduce the difficulty of maintenance.

8. Versatility

The functions of rapid development frameworks in the same industry or field are more or less the same and can be applied to similar projects without much change. In the rapid development framework, we generally implement some homogeneous basic functions, such as rights management, role management, menu management, log management, exception handling. Or the general functions to be used in the industry, so that the framework can be applied to a certain industry or field, rather than just for a company's business (of course, there must be an application framework for those specific functions, this is only a very few special cases, it is not within our consideration).

This is the end of this article on "what is a rapid development framework on the Internet". I hope the above content can be of some help to you, so that you can learn more knowledge. If you think the article is good, please share it for more people to see.

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.