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.2, the use case in the figure is a typical scenario between the user and the computer.
Figure 12.2 use case diagram
diagram.The following fragment types can be used to change this interpretation:
Fragment type
Name
Description
Consider
Consider
Specifies the list of messages described by this fragment. Other messages can occur on a running system, but this is not a very meaningful description.Type the list in the Messages property.
Ignore
Ignore
A list of messages not described in this fragment. These messages can occur in a running syst
diagram.The following fragment types can be used to change this interpretation:
Fragment type
Name
Description
Consider
Consider
Specifies the list of messages described by this fragment. Other messages can occur on a running system, but this is not a very meaningful description.Type the list in the Messages property.
Ignore
Ignore
A list of messages not described in this fragment. These messages can occur in a running syst
diagram.The following fragment types can be used to change this interpretation:
Fragment type
Name
Description
Consider
Consider
Specifies the list of messages described by this fragment. Other messages can occur on a running system, but this is not a very meaningful description.Type the list in the Messages property.
Ignore
Ignore
A list of messages not described in this fragment. These messages can occur in a running syst
Class diagram, the British Civilization Yue: Class diagram, then the class is after how magical transformation, into a class diagram? As we all know, classes are descriptors of a set of objects with similar structures, behaviors, and relationships, classes are the most important building blocks in object-oriented systems, and class diagrams show a set of classes,
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 case or reload it. The parent case is usually abstract.
[Arrow pointing]: pointing to the parent use case
C. Include)
The include relation is used to break down the Functions Represented by a complex use case into smaller steps.
[Arrow pointing]: points
multiple links1Written by one party1, Write by multiple partiesN;
Multiple-to-many relationships are written in the direction of the two physical connections.N, m
UML:
The first use case diagram (Use Case digoal)
The second type is static digraphs, including class graphs, object graphs, and packet graphs.
The third type is the behavior diagra
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 case);3, generalization, inherit, I read it as " inherit in ", of course, the arrows point to the father;4, Dependency, I read " depends on", I know the dir
ArticleDirectory
Types of products, such as artificial intelligence, artificial intelligence, and artificial intelligence.
Reference (REF)
Conditional differentiation (ALT)
Conditional judgment (OPT)
And column allocation (PAR)
Loop)
Break)
Please wait until there are too many critical errors (critical)
Snapshot has been created (assert)
The specifie
. For this long square lattice, I have never understood what it actually means. I encountered an open-minded explanation on "Baidu Encyclopedia:You can think of activation as a "{}",From the beginning to the end, it can be understood as a method, an action;
The lifeline is used to describe the time when an object exists. Add the destroy symbol below to delete the object or recycle the object. It is actually a Roman's dragon nest. When it's done, let's leave.
There are four types of messages, but
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, establish a dependency between the role and the other role.
How to identify the participants. who is providing information to the system? Who gets information from the system. Who operating system. What external resource sy
member variable;Dependency relationship (dependency)A dependency is represented by a set of dashed lines with arrows, such as a dependent on B; He describes the relationship of an object to another object while it is running;Unlike association relationships, it is a temporary relationship that usually occurs during operation and changes with the runtime, and dependencies can change;Obviously, the dependence also has the direction, the bidirectional dependence is one kind of very bad structure,
Symbol:+:p Ublic-:p Rovite#:p Rotected~:p ackageRelationship:
Relationship Name
Code relations
Uml
Generalization (generalization)
Inherited
Solid Line Triangle Arrow
Implementation (Interface realization)
Implementation of subclass inheritance of virtual base function
Dashed triangular arrow
Dependency (Dependency)
One class as a function parameter or ret
This article reprint casually, Please retain the Source: http://blog.csdn.net/dylgsy/
UML class diagram relationships include association, aggregation/combination, dependency, and generalization (inheritance ). The Association is divided into two-way Association, one-way Association, and self-Association. Let's take a look at what these relationships are and what their differences are.
1. Association
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 case describes a complete system service.
3System boundaries
4Relationship: the relationship between executors and use cases.
Generalization
Dependency
Association
Aggregation and combination
Implementation
You can read books, roles, system boun
Class diagrams are the most commonly used diagrams in UML. We can see that class diagrams are very important.
A class chart is a class digoal. The shape is very simple. It consists of a rectangle, two rectangles, or three rectangles.
For example:
The top column shown in is the class name. The second column is the class property. (A class can have one or more attributes. Of course, some classes have no attributes) the third column is the cl
. Proxy modeIntent: Provides a proxy for other objects to control access to this object.21. Single case (Singleton) modeIntent: Ensure that a class has only one instance and provides a global access point to access it.22. Status (State) modeIntent: Allows an object to change its behavior when its internal state changes.23. Policy (strategy) modeIntent: Define a series of algorithms, encapsulate them one by one, and make them interchangeable with each other.24. Template Method ModeIntent: Define
consistent.Just, the class involved in the association is logically a level, such as the student teacher above, but the aggregation involves the class is not a level.Look at the following example:It can be expressed as a has a/some B, at which point B is able to separate from a and exist independently. Without a car tire or a tire.Combination compositionThe composition relationship is a bit tighter than the aggregation relationshipThe limbs and the people are die.Non-separable.As for generaliza
Class digraphs are graphs describing classes, interfaces, collaboration, and relationships between them.
A class diagram is a part of a static view in the system. A static view can contain many class diagrams.
Static views are used for Structural Modeling of the software system. They construct the vocabulary and relationships of the system, and the visualization of structural models is achieved through class diagrams.
A class chart consists of the
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.