It is not short time to use NET development, and the project is not very good, but there is a little unwritten ... (I don't know what it is good?), Please criticize (welcome criticism refer to ninglng @ 163. COM)
Program architecture, functional division:
Database (including stored procedure) Data Access (including version 2.0 version of Microsoft Application Blocks for .NET) Data Structure (equivalent to Strong Type Dataset) Business Logic Layer Business Express Layer
Database: Don't say, it is the database; excluding business logic, the main role of stored procedures is to complete basic operations for the table, including add, delete, modify, select, etc.
Data Access Layer: Implementing the basic operation method of the database, adding. Modify. Delete, determination, whether or not, select data, etc. Granularity implementation in business rules
Data Structure: You can use strong type DataSet, this layer is a mapping of the C # to the database structure, and is provided to other hierarchical calls;
Business logic layer: The data access layer does not need to care about the data legal, etc., and the processing content here should be a further package of the data access layer, and one of the functions of the number of data can be called small. The process of processing; so it can be said to be a coarse particle size;
Business Express Layer: This layer is the friendly operation interface, but for more complex systems, the legal verification of data can be handled separately, while the business logic layer only needs to handle the logic of the business; and general scale small The system, business logic, and business performance can be intended to be an implementation;
The above is the analysis of 'longitudinal', in the actual development, in order to more easily and efficiently develop, completely 'horizontal' analysis, division module:
System Architecture (General) Permissions (General) Personal Processing (General) Specific Business Implementation About / Help (General)
All systems must use someone, so this is handled separately here; (Welcome criticism refers to ninglng@163.com)
System Architecture: Main implementation, processing of the system configuration, the basic operating conditions of the commonly used settings, and the implementation of the architecture of the entire system. The system will require basic operating conditions, this part is handled separately, make a universal module, afterward Can be used directly in the system;
Permission processing: Manage the permissions of the system, the handling process has more mature schemes on the Internet, the shape color, each have the advantages, we can exchange our own content while absorbing their strengths, complying with us The permission processing module of the general principles, the part of the package, and the system architecture is a common module;
Personnel Management: This module is ideas to join the permission management, because they are close-in, but they want to make a relatively universal module, and the system's handling demand is not very detailed, some rough, difficult to coordinate Perhaps we can make a module that can meet most of the needs of most systems can be merged into the permission module, so permission is designed to be more efficient;
About / Help: This is a system or the entire company's similar products about products and help, and it is an advertisement in an angle;
The specific business: is the difference between the system, and the core of our work (if the work of the above module has been completed), this module is customized according to the content of the business, nothing to say.
The division of the transverse / longitudinal direction is interpolated, not from one angle distinguishing.
This is a little bit of ideas, written here, brick, etc., just throw (but please don't face it!)
