Computer room charges. NET version of personal refactoring--summary

Computer room Toll system personal reconstruction version finally to fall the curtain, this 1.5 months experience of "pain" and the joy of success may also only oneself can experience it, now back to, carry on a summary, particles!

Computer room charge Personal reconstruction the approximate experience should be divided into four stages: requirements analysis, software architecture (UML diagram and soft work document), code writing, program debugging perfect.

Demand analysis

The requirement analysis of Personal Reconstruction Edition is more clear than VB version, among which three points need to be pointed out:

A. The user of the software is a teacher or other faculty, and the student is not directly exposed to the system as a consumer.

B. Three users (general users, operators, administrators) only have different permissions, and have an inheritance relationship.

C. Feel that there should be a Super Administrator (Boss), there is a more privileged account, above the three types of users.

( with a pair of fishbone diagrams, as opposed to the first version has changed)

Software architecture

Database Design

After understanding the requirements, we should design the database, which is the basis of our follow-up work. Before we design the database, we need to analyze the entities in the system, and the relationship between them, draw out the E-r diagram, through the E-r diagram we can clearly understand that we need those tables, which are strong entities and weak entities and the main foreign key of each table is what, to reduce redundancy, as far as possible to conform to the three paradigms.

Overview Design

Draw a class diagram, implement three layers, consider where to add the design patterns, and draw a package diagram.

Detailed Design

This part of the focus is to draw a time series diagram, which is the source of ideas in our code writing phase.

Code writing

This stage is also the expansion of some new knowledge, we need to solve a lot of issues that have not been considered, such as the use of views to simplify the operation of the database view, the use of stored procedures to simplify the operation and deletion, to ensure the atomicity and consistency of the transaction; the use of sqlhelper reduces the amount of code, easier to maintain; for a generic collection, by putting the data in a DataTable into a generic collection, we can invoke the corresponding value only based on the attributes of the entity, instead of looking at the field's face.

Perfect Commissioning

after the system has been done, the necessary interface beautification, there are errors are unavoidable, we also need Debug the system, install the test, this part must not be ignored, the effort so long, not bad in the last few steps. Once you have written your user manual, you are ready to deploy the release.

Summary

The formation of any thing requires a process, a good software is no exception, we should step-by step, both from the overall situation, but also to take into account the details, in accordance with the nearly standardized process, to produce a user satisfaction with the software.

Computer room charges. NET version of personal refactoring--summary