Start learning the UML modeling language, starting with the use case diagram. Modeling Tools Select VisioThe use case diagram describes the system functions understood by the participan
I. Introduction to UML Use case modeling
Use case modeling is part of UML modeling, and it is the most basic part of UML. The most important function of
I,Description of the use case diagram
Use Case (Use Case) Refers to the interaction between the system's external things (activists, devices, or external systems) and the system. It e
One. UML OverviewThe role of 1.UML: a complex problem decomposition B realizes the visualizationUML is created by rational company 2.UML is what: is a language, has its own standard expression rules, is an analytical design language, is also a modeling language 3.UML including five large views, 13 kinds of Figure five
Original address: http://blog.csdn.net/zhuojiajin/article/details/8657853See the UML video, feel the UML content actually look very clear. When I started to paint, I found out that it was purely a teacher's job. Listen to understand or feel that you understand that it is just an illusion. For the UML diagram or underst
first, UML use case diagram basic conceptUML Use-case diagrams: Dynamic views that describe the functionality of a system, consisting of actors "actors", use cases, and their relationsh
UML Use case diagram Summary author: tianhai110 Published: 2012-01-30 15:33 read: 100,263 recommendations: 57 Original link [Favorites]Use case diagrams are primarily used to describe the relationship between users, requirements,
Original: UML Use case diagram summaryReprint Please specify source: http://blog.csdn.net/tianhai110Use case diagrams are primarily used to describe the relationships between users, requirements, and system functional units. It shows a model
Document directory
The UML use case diagram contains three relationships: (include), (extend), and (generalization ).
Overview
The Use Case attempts to summarize the relationship between roles and systems in the
as alternative streams in the parent case.
For example, there may be many tasks that require approval from department leaders in the business, but the approval process is very similar. In this case, 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
. Generalization (inheritance)Is the commonly understood inheritance relationship, where the child use case is similar to the parent use case, but behaves more specifically, and the child use case inherits all the structures, beha
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
message.Arrow point to: Point to the message receiverB. Generalization (inheritance)Is the commonly understood inheritance relationship, where the child use case is similar to the parent use case, but behaves more specifically, and the child use
In the UML 9 kinds of diagram, the use case diagram is the more important one kind of diagram, it is the diagram which produces in the system analysis stage, from the function carries o
To learn UML, you must first learn 14 types of UML graphics. To learn graphs, you must first know what elements are on the graphs.
[Note] This document is not a basic tutorial Of the use case diagram, but a graphical Summary of the use
Objective
UML is used to describe the entire design process of the system, and for this process produced a UML9 diagram: Use case diagram, Class diagram, object graph, collaboration diagram
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 stru
use case diagram.
composition: System boundaries. Participants. Case. Relationship.
Participant: Actor is not a person, but a role to play when participating in a use case.
If the action of one role is done by another role agent
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.