without an arrow, an arrow pointing to a use case, and an arrow pointing to a role. No matter whether there are arrows or not, these lines are used to connect roles (villains) and use cases (circles), indicating what use cases a role can "do.A line with arrows indicates the flow of data during the interaction between
Case modeling is a part of UML modeling and the most basic part of UML. The main function of case modeling is to express the functional requirements or behaviors of the system. To put it bluntly, it is to explain what the system is, so you don't have to worry about how to work. I think the
When you use Microsoft Visio to draw a use case diagram today, you find that the include relationship is not found in the Visio UML use case, which is the "arrow" + "Finally, a workable
, the general relationship can be expressed as follows:
The above is an article I have referenced. I think the difference between the three relations is very clear. Based on this, I will combine my own system to explain the project (Online Shopping System) as a whole.**************************************** *************************(1) overall system use case diagram
extension (Extension) use case, and then extends it from the extension point (Extension points) declared in the base use case to make the base case more concise and more focused. The extension use
Recently has been learning the basic knowledge of UML, after watching the video, and did not have a good summary, in the process of drawing found a lot of problems, the following is the process of reading their own summary of the UML use case diagram of a little knowledge, s
as an inheritance relationship. Child cases are similar to parent cases, but show more special behaviors. Child Cases inherit all structures, behaviors, and relationships of the parent case. A child use case can use a behavior of the parent use
In all UML diagrams, the most easy to understand is the use case diagram, which is also a UML diagram with the least elements, and also the most handy one for product managers.
I. Purpose
The
The previous blog summarized the use case diagram, in which the relationship between use cases is only included, because the relationship between use cases is not particularly profound. This is also because the UML
The use case diagram mainly includes use cases, activists, and relationships.
Use Cases: A description of the sequence of actions that the system, subsystem, or class interacts with external participants, including various normal sequences and error sequences.
The use case diagram is used to describe the relationship between users, requirements, and system functional units. It shows a system functional model diagram that can be observed by external users.
[PURPOSE]: help the development team understand the functional requirements of the system in a visual manner.
The
Use case diagram Structure
1Roles: Personnel roles-people and events;
Roles are not necessarily limited to people. They can also be things or things.
2. Use Case: function description;
Each use
Use Case Diagrams are used to determine the scope of requirements. These requirements are the basis for design and development. The use case diagram treats the system as a black box and understands the system from the perspective of external executors. As shown in Figure 12.
and generalization in UML [conversion]
Three relationships:
Between Generalized participants and Use Cases
Online Ordering by telephone
Between extension cases
Maintenance-Add entry inclusion
Drink between use cases-open bottle caps
Generalized representation is similar to the OO term "inheritance" or "polymorphism ". The general process of
UML Case Diagram (use cases) arrow direction:Always forget the direction of the arrows, provoke jokes.1, association, no arrows, actor connection usecase can;2, Directedassocition,actor connection UseCase, arrow by actor point to usecase (role point use
ArticleDirectory
(1) from the perspective of general users
(2) From the operator's perspective
(3) from the Administrator's perspective
Drawing a use case diagram is the first step from the software requirement to the final implementation. Its correctness directly affects the user's satisfaction with the final product. In fact, we can also s
Use case diagram: used to describe the relationship between users, requirements, and system function units. It shows a system function model diagram that can be observed by external users.
Main Purpose: To help developers understand the functional requirements of the system in a visualized manner
Take a look at the fol
the extension use case adds new behavior to the base use case
Diagram Description:
Association:
Depend on:
Generalization:
Contains:
Extended:
Two. Role: Describe the needs of the user (emphasizing the function, the performer of the function, the system in
Example
Defining system boundaries determines the boundaries between the system's interior and exterior.
The main character represents the role played by the external object. An object can assume several roles, so it can be represented by several leading roles.
Communication relationships are used to clarify the participation of the main character in the use case.
A
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.