Idea of Rapid Development Based on. net

According to the characteristics of. net and the experience in the project development process, a set of rapid development modes are preliminarily summarized, hoping to improve the development efficiency of. net. Quick Development includes two purposes: first, to improve the efficiency of individual programmers involved in the project, and second, to improve the overall development efficiency of the project.
The first is to explicitly use the system architecture during. net development. I designed the system architecture as the following model.

In my system model, the core layer is the most basic component of the project, including the base class A and B for various data access operations with the database, A Class of various string operation functions (such as filtering dangerous characters) applied in the project. For the implementation of the Data Access Base Class A, refer to Microsoft's Data Access Application Block. For details about the Data Access Application Block, refer to the following website:

Http://www.microsoft.com/china/msdn/archives/library/dnbda/html/daab-rm.asp

At the same time, I derived A Class B from base class A, which added methods such as NewRow () and Update () to provide full support for the data layer at the upper layer. This core layer will be used in all projects, and it will be represented as a compiled dll (I name it common. dll), each member of the project can reference it and use its methods.

The data layer creates a class for each table in the database, and each field of the table corresponds to an attribute of the class in this class. This class inherits Data Access Class B in the core layer, therefore, you can add or modify records to a table in this class.

The problem here is that since it is a fast development mode, of course, this class corresponding to the tables in the database should not be generated manually every time. For this reason, I wrote a dedicated tool that can simply fill in the database connection information and read and retrieve all the user tables under the database, then select the expected table to automatically generate the required c # code. In this way, the above problems are solved and rapid development is realized.

For the logic layer in the middle, you can write a class for each module by module to implement the complicated process or encapsulate the Code involving SQL statements here.

The presentation layer is a specific UI interface that can be used by users. Generally, the pages that users end up with are displayed here.
This development idea can not only improve the development efficiency of a single programmer, but also improve the development efficiency of the entire project team as a whole. We can compare it with a common development model.

On the left is a traditional practice. In a project, the program is divided into modules, and the programmer is responsible for writing all the code of the module. This development method makes projects more dependent on individuals, and the differences in personal level make the module quality significantly different. At the same time, there are large risks in the project, mainly because everyone accesses the database directly, which may cause confusion in the data structure.

On the right side is the method I recommended. The underlying data layer is primarily the responsibility of the primary programmer and is called by everyone in a unified manner. The above is assigned to different programmers. At the same time, this model can also be evolved into a logic layer which is mainly undertaken by individual main programs, and the presentation layer is handed over to different programmers. This mainly depends on the project details.