uml--use case diagram

Use case diagrams are a kind of consensus that developers and users have reached on requirements specifications during the requirements analysis phase, which describes the functional requirements of the system to be developed.

UML Video gives us a theoretical understanding of the basic elements, attributes, and granularity of use case diagrams, and we need to draw a picture ourselves to deepen our understanding of use case diagrams. Drawing the use case diagram, we first analyze the roles and use cases in the development system, then connect the roles and use cases through the relationship.

role: including the user of the system, maintenance personnel, the use of peripherals, so the role is not only people, can also be things, objects.

use case: refers to the system to implement the function, is a description of the system functions.

relationships: includes dependencies, generalizations, and associations three relationships, indicating the specific relationship between use cases and roles.

The first time you draw a use case diagram, the role and use case feel is relatively easy to analyze, but the role and use cases between the specific relationship between the silly points are not clear. UML includes dependency, association, generalization, implementation of four relationships, the initial understanding of these relationships is not very clear, and then exposed to the extension and inclusion of the relationship, and then found that in different diagrams these relationships will have some differences. After drawing 9 diagrams of UML, we will make a systematic understanding of these relationships and share them with you.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

uml--use case diagram