Rebuilding the data room Charging System (1)

The school data room charging system was restructured since October 1. I did not expect this restructuring, overthrowing, or restructuring ...... It took two weeks.

The overall architecture adopted three layers and some design modes were integrated.

 

The following describes the reconstruction process:

1. Start with the UML use case diagram

I am already familiar with the requirements of the data room charging system, and the use cases and roles have been extracted. Here I have encountered a problem: what is the use case based on the role division, or divide the use cases based on functions?

Draw by role: it is easier to model next. The previous use case corresponds to a UI Layer interface and a use case corresponds to a business logic. However, in the data room charging system, it is not conducive to macro control of the system

 

Draw by function module: make the entire system look more intuitive and more easily grasp the functional requirements of the entire system.

However, the charging system for the data center is obviously not conducive to the next modeling. It is easy to miss the method when using abstract classes.

 

The two have their own advantages and disadvantages, which are different in different systems. In the data center charging system, I focus more on Role-Based usage examples. Based on the principle that we can describe both of them as long as we can describe our needs, the better we can.

1. By role:

System Administrator:

OPERATOR:

General Users:

2. By function:

Financial Information Management

Online/offline information management

System Information Management

Student Information Management

Restructuring of the IDC Charging System (II)