UML use case diagram-detailed tutorial description) UML use case diagram-detailed tutorial description

Http://www.cnblogs.com/zhaolijing/archive/2013/02/28/2936321.html

UML use case diagram-detailed tutorial

I. Definition of use case diagram:

ByActors and Use Cases)And the relationship between themDescribe system functionsThe dynamic view of is called the use case diagram. Draw a participant (representing a system user) on the example graph to draw a humanoid symbol. The relationships between participants and use cases are described by line segments with or without arrows. Arrows indicate which party is the active initiator of the conversation in this relationship, the arrow indicates the passive receiver of the conversation.

The use case diagram describes a function unit provided by the system..The purpose of the use case diagram is to help the development team understand the functional requirements of the system in a graphical manner.,Including"Role"Relationship, and the relationship between the internal use cases of the system. The use case diagram shows the Organizational Relationship of the use case. This organizational relationship includes all the use cases of the entire system or a set of use cases that complete related functions..

 

2. Relationship between Use Cases

1,Inclusion relationship

1)Inclusion relationshipA use case can simply contain the behaviors of other use cases and act the behaviors of the use cases contained in itIs part of your own behavior. In UML, the inclusion relationship is throughArrowsAdd dotted lines <include>WordsThe arrow is pointed by the base to the included use case ).

 

 

The inclusion relationship indicates that the basic use case is used in the included use case. Specifically, the event stream that includes the use case is used.Insert it to the event stream of the basic use case. It should be noted that the relationship of the same semantics is expressedUse(Uses).

 

 

2)When dealing with include relationships, the specific method is to separate the public parts of several use cases into one.New Use Cases.There are two main scenarios that require the inclusion relationship:

A)First,Multiple Use Cases use the same behavior SectionTo separate and abstract the common behavior into one.And other use cases to include this use case.

B)Second,When a use case has too many functions and events flow through complicated conditionsWe can also stream a certain event.As an included use case to simplify the description.

 

2, Extended relationships

1)Under certain conditions, add new behaviors to existing use cases. The obtained new use cases are calledExtended use cases(Extension)The original use case is calledBasic Use Cases(Base)The Relationship Between Extended use cases and basic use cases isExtended relationships.A basic use case can have one or more extension use cases, which can be used together.

 

 3, Generalized relationship

The generalization of use cases means that a parent case can be specially formed into multiple child cases, while the parent case and child caseIsGeneral Relationship.In the general relationship of a use case, the sub-Use Case inherits all the structures, behaviors, and relationships of the parent case. The sub-use case is the parent case.A special form of use cases.Child cases can also be used to add, overwrite, or change inheritance behaviors. In UML, the general relationship of a use case is described as follows:ItemsWithStraight line of the hollow arrowIt is represented by pointing the child case to the parent case.

 

General example: there are two types of bank deposits: bank counter deposits and at M machine deposits. InHere, both bank counter deposits and at M machine deposits are a special method of deposit, so "deposit" is the parent use case, and "bank counter deposits" and "ATM machine deposits" are subuse cases.

 

 

 

 

 

Example:

The following example is based on the permissions of the operator in the IDC charging system:

 

 

 

I. Definition of use case diagram:

ByActors and Use Cases)And the relationship between themDescribe system functionsThe dynamic view of is called the use case diagram. Draw a participant (representing a system user) on the example graph to draw a humanoid symbol. The relationships between participants and use cases are described by line segments with or without arrows. Arrows indicate which party is the active initiator of the conversation in this relationship, the arrow indicates the passive receiver of the conversation.

The use case diagram describes a function unit provided by the system..The purpose of the use case diagram is to help the development team understand the functional requirements of the system in a graphical manner.,Including"Role"Relationship, and the relationship between the internal use cases of the system. The use case diagram shows the Organizational Relationship of the use case. This organizational relationship includes all the use cases of the entire system or a set of use cases that complete related functions..

 

2. Relationship between Use Cases

1,Inclusion relationship

1)Inclusion relationshipA use case can simply contain the behaviors of other use cases and act the behaviors of the use cases contained in itIs part of your own behavior. In UML, the inclusion relationship is throughArrowsAdd dotted lines <include>WordsThe arrow is pointed by the base to the included use case ).

 

 

The inclusion relationship indicates that the basic use case is used in the included use case. Specifically, the event stream that includes the use case is used.Insert it to the event stream of the basic use case. It should be noted that the relationship of the same semantics is expressedUse(Uses).

 

 

2)When dealing with include relationships, the specific method is to separate the public parts of several use cases into one.New Use Cases.There are two main scenarios that require the inclusion relationship:

A)First,Multiple Use Cases use the same behavior SectionTo separate and abstract the common behavior into one.And other use cases to include this use case.

B)Second,When a use case has too many functions and events flow through complicated conditionsWe can also stream a certain event.As an included use case to simplify the description.

 

2, Extended relationships

1)Under certain conditions, add new behaviors to existing use cases. The obtained new use cases are calledExtended use cases(Extension)The original use case is calledBasic Use Cases(Base)The Relationship Between Extended use cases and basic use cases isExtended relationships.A basic use case can have one or more extension use cases, which can be used together.

 

 3, Generalized relationship

The generalization of use cases means that a parent case can be specially formed into multiple child cases, while the parent case and child caseIsGeneral Relationship.In the general relationship of a use case, the sub-Use Case inherits all the structures, behaviors, and relationships of the parent case. The sub-use case is the parent case.A special form of use cases.Child cases can also be used to add, overwrite, or change inheritance behaviors. In UML, the general relationship of a use case is described as follows:ItemsWithStraight line of the hollow arrowIt is represented by pointing the child case to the parent case.

 

General example: there are two types of bank deposits: bank counter deposits and at M machine deposits. InHere, both bank counter deposits and at M machine deposits are a special method of deposit, so "deposit" is the parent use case, and "bank counter deposits" and "ATM machine deposits" are subuse cases.

 

 

 

 

 

Example:

The following example is based on the permissions of the operator in the IDC charging system: