UML Drawing Document-use case diagram

 

Reading videos or tool books, including summaries, is in the theoretical stage. "The last word on the paper is superficial. I know that this is a must ." Now we are in the UML document stage, and it won't work unless we do it.

I have done the "Data Center Charging System" before. To put it bluntly, I am blind. I have no rules to follow the feeling. The training solution provides the following explanation: "We have already done this because of the data room charging system, and we are very familiar with his needs. However, we need to be clear that the document guides our development and is written before code development, rather than after development. At this point, we need to abandon our previous design scheme and re-acquire the requirements at and design them. ." Therefore, all previous understandings of the data center charging system can only be put aside. In the face of the data center charging system, you should be an SB.

U ml involves nine types of diagrams in total, and you should start with the example diagram first. After all, it is the first step from the software requirements to the final implementation. In UML, use case diagrams are used to visualize the behavior of systems, subsystems, or classes, so that users of the system can better understand the purpose of these elements, software developers can also ultimately implement these elements.

In reality, for users, how the system is implemented and how the internal structure of the system is not what they care about. The use case diagram describes the requirements for software products from the user's perspective rather than the developer's perspective, and analyzes the functions and dynamic behaviors required by the products. Therefore, for the entire software development process, the use case diagram is crucial. Its correctness directly affects the user's satisfaction with the final product.

The "Data room Charging System" function is quite simple:

1.OKACTOR:(The order is "ordinary" in descending order.
User, operator, and Administrator, in which high-level users can exercise permissions of low-level users)

2.
Confirm use case:

(1) The three most basic functions (all levels of users have the right to exercise)

System Logon

Student computer

Students go offline

(2) Querying student information (users of all levels have the right to exercise)

Query balance

Query Machine Records

Query machine status

Query recharge records

Query card return information

(3) Student Management (only "operator" and "Administrator" users have this right)

Register

Recharge

Card return

Basic student information maintenance

(4) query user information (only "Administrator"-level users have this right)

Query user work records

Query users on duty

(5) Bill Management (only "Administrator" users have this right)

Daily settlement management

Weekly settlement management

(6) System Management (only "Administrator" users have this right)

Computer parameter settings

Add or delete users

Change Password

3.Use rational
RoseTo draw: