IDC charging system use case diagram

Introduction

The database design phase of the data room charging system was completed a few days ago. After the completion, I was not in the next stage, for fear, I am afraid that the professional courses and advanced courses do not have a reasonable plan of time, which leads to chaos on a daily basis. I am afraid that my thinking will fall into the dilemma that I don't know which one to learn, and eventually I will not learn anything, therefore, I made a decision to learn about my professional courses from Monday to Friday, learn more about Saturday and Sunday, and believe that it will not take long to learn professional courses, after completing those courses, I will spend most of the time from Monday to Friday on advanced courses.

Overview

The usage example of the data room charging system uses the object-oriented idea to divide the entire system into several objects. Each object includes its own functions, in this way, the user's needs are clearer and organized.

Use case diagram Relationships between participants

The operator functions of the operator include operator_level2 operator functions, operator_level2 operator functions include operator_level1 operator functions, operator_level1 operator functions include operator_common operator functions. It should be noted that there are no operator_common operations in the actual operator, and the operator at this level appears to make modules of other operators more cohesive.

Operator_common Operator Functions

The function of this operator is to log on to the charging system of the data center, exit the charging system of the data center, help the user to get on the machine, help the user to get off the machine, and perform operations to modify basic information, users cannot directly use the data center charging system. They must use the operator to perform operations on and off the machine.

Operator_level1 operator Function

The main functions of a level-1 operator are for users. We can regard a level-1 operator as a user and represent the user's functions. However, these functions are not operated by real users, instead, the first-level operation is used to complete the actual operation. Functions include adding, deleting, querying, and modifying users. User queries include queries of user records on the machine, queries of current online users, queries of basic user information, balance queries, and Bill queries. Because users and cards are bound, is one-to-one, the card can determine the unique user, the user can determine the unique card, so the user to edit this feature includes two small functions, one is the change of basic user information (user name, password, etc.); the other is the recharge and edit of the card. If the function of the user is described, this part should not appear here, however, the comparison is more appropriate here. After all, operator_level11 is also an operator rather than a user.

Operator_level2 operator Function

The permissions of the operator at this level are already very large and can be performed for common operations. The main function is to query all the things done by the operator, the operation function of the operator.

Operator_level3 operator Function

Operator_level3 operator functions more than operator_level2 operator functions in checkout and modification of basic billing information.

Summary

The purpose of a use case diagram is to express user needs. We can classify and summarize these requirements (functions) so that they can be structured and hierarchical. However, note that, the hierarchy here should not be applied in the class diagram, that is,ProgramThe structure hierarchy of the design is another new structure, which is not completely structured using the use case diagram function.

There are some errors in the above case, such as the representation of the extended relationship. You only need to understand it.