Note that although the syntax allows it, lifeline-ident cannot be empty. The lifeline head has a shape that is based on the classifier for the part that this lifeline represents. Usually the head is a white rectangle containing name of class.
If the name is the keyword self , then the lifeline represents the object of the classifier that encloses the Interaction that owns the Lifeline. Ports of the encloser may be shown separately even when self is included. A gate is a message end , connection point for relating a message outside of an interaction fragment with a message inside the interaction fragment. The purpose of gates and messages between gates is to specify the concrete sender and receiver for every message. Gates play different roles:.
The gates are named implicitly or explicitly. Implicit gate name is constructed by concatenating the direction of the message 'in' or 'out' and the message name, e. Interaction fragment is a named element representing the most general interaction unit.
Each interaction fragment is conceptually like an interaction by itself. There is no general notation for an interaction fragment. Its subclasses define their own notation. Occurrence complete UML name - occurrence specification , i. An occurrence specification is one of the basic semantic units of interactions. The meanings of interactions are specified by sequences of occurrences described by occurrence specifications.
Each occurrence specification appears on exactly one lifeline. Occurrence specifications of a lifeline are ordered along the lifeline. Occurrence specification has no notation and is just a point at the beginning or end of a message or at the beginning or end of an execution specification. Message occurrence complete UML name - message occurrence specification is an occurrence which represents such events as sending and receiving of signals or invoking or receiving of operation calls.
Destruction occurrence is a message occurrence which represents the destruction of the instance described by the lifeline. It may result in the subsequent destruction of other objects that this object owns by composition.
No other occurrence may appear below the destruction event on a given lifeline. Complete UML name of the occurrence is destruction occurrence specification. Until UML 2. The destruction of instance is depicted by a cross in the form of an X at the bottom of a lifeline. Execution occurrence complete UML name - execution occurrence specification is an occurrence which represents moments in time at which actions or behaviors start or finish.
Execution occurrence references exactly one execution specification which describes the execution that is started or finished at this execution occurrence. Execution full name - execution specification , informally called activation is interaction fragment which represents a period in the participant's lifetime when it is.
Note, that the execution specification includes the cases when behavior is not active, but just waiting for reply. The duration of an execution is represented by two execution occurrences - the start occurrence and the finish occurrence. Execution specification can be represented by a wider labeled rectangle, where the label usually identifies the action that was executed. For execution specifications that refer to atomic actions such as reading attributes of a signal conveyed by the message , the action symbol may be associated with the reception occurrence specification with a line in order to emphasize that the whole action is associated with only one occurrence specification and start and finish associations refer to the same occurrence specification.
Overlapping execution specifications on the same lifeline are represented by overlapping rectangles. A state invariant is an interaction fragment which represents a runtime constraint on the participants of the interaction. It may be used to specify different kinds of constraints, such as values of attributes or variables, internal or external states, etc. The constraint is evaluated immediately prior to the execution of the next occurrence specification such that all actions that are not explicitly modeled have been executed.
If the constraint is true, the trace is a valid trace, otherwise the trace is an invalid trace. Information identifying the lifeline is displayed inside the rectangle in the following format slightly modified from what's in UML 2.
Note that although the syntax allows it, lifeline-ident cannot be empty. The lifeline head has a shape that is based on the classifier for the part that this lifeline represents. Usually the head is a white rectangle containing name of class.
If the name is the keyword self , then the lifeline represents the object of the classifier that encloses the Interaction that owns the Lifeline. Ports of the encloser may be shown separately even when self is included. A gate is a message end , connection point for relating a message outside of an interaction fragment with a message inside the interaction fragment. The purpose of gates and messages between gates is to specify the concrete sender and receiver for every message.
Gates play different roles:. The gates are named implicitly or explicitly. Implicit gate name is constructed by concatenating the direction of the message 'in' or 'out' and the message name, e. Interaction fragment is a named element representing the most general interaction unit. Each interaction fragment is conceptually like an interaction by itself. There is no general notation for an interaction fragment.
Its subclasses define their own notation. Occurrence complete UML name - occurrence specification , i. An occurrence specification is one of the basic semantic units of interactions. The meanings of interactions are specified by sequences of occurrences described by occurrence specifications.
Each occurrence specification appears on exactly one lifeline. Occurrence specifications of a lifeline are ordered along the lifeline. Occurrence specification has no notation and is just a point at the beginning or end of a message or at the beginning or end of an execution specification. Message occurrence complete UML name - message occurrence specification is an occurrence which represents such events as sending and receiving of signals or invoking or receiving of operation calls.
Destruction occurrence is a message occurrence which represents the destruction of the instance described by the lifeline. It may result in the subsequent destruction of other objects that this object owns by composition. No other occurrence may appear below the destruction event on a given lifeline. Complete UML name of the occurrence is destruction occurrence specification. Until UML 2. The destruction of instance is depicted by a cross in the form of an X at the bottom of a lifeline.
Execution occurrence complete UML name - execution occurrence specification is an occurrence which represents moments in time at which actions or behaviors start or finish. Execution occurrence references exactly one execution specification which describes the execution that is started or finished at this execution occurrence.
Execution full name - execution specification , informally called activation is interaction fragment which represents a period in the participant's lifetime when it is. Note, that the execution specification includes the cases when behavior is not active, but just waiting for reply. The duration of an execution is represented by two execution occurrences - the start occurrence and the finish occurrence.
For more information, contact your Microsoft admin. If your admin has turned on "self-service purchasing," you can buy a license for Visio yourself. For more details, see Self-service purchase FAQ. Open Visio for the web. The first item in the row represents a blank template plus the companion stencil. The other items in the row are sample diagrams that have some shapes already drawn to help you get started quickly. In the Model Explorer tree view, right-click the package in which you want to include the static structure diagram, point to New , and click Sequence Diagram.
A blank page appears, and the UML Sequence stencil becomes the top-most stencil. An icon representing the diagram is added to the tree view.
Use an Object lifeline shape for each participant and system component in your process. An object lifeline represents the existence of an object at a particular time. If the object is created or destroyed during the time period the diagram represents, the lifeline stops or starts at the appropriate point.
An object's destruction is marked with a large X. Use a Lifeline shape to show conditionality on an object lifeline.
The message shape you choose depends upon the kind of message you want to send regular, asynchronous, procedure call, or return. Glue the message endpoint without the arrowhead to a connection point on the lifeline of the object sending the message. Glue the message endpoint with the arrowhead to a connection point on the lifeline of the object receiving the message. Double-click the message, and then type or choose the message name, stereotype, sequence expression, and flow kind. For a flat message or procedure call, choose the operation you want the message to generate.
If the operation doesn't exist, click New to create it. For an asynchronous message, choose the signal you want the message to generate. If no reception for the signal exists on the classifier that the object lifeline receiving the message is based on, click New to create the reception.
Tip: To indicate a message from an object to itself, glue the two endpoints on an arc-shaped Message shape to two connection points on the same object lifeline. If one or more interactions require a condition to be met to end the interaction, enclose those interactions in one of the constraint shapes:. A Constraint is a specification for conditions and propositions that must be maintained as true for the system to be valid.
Drag the control handle at the center of the Constraint shape and glue it to a connection point on another element. A 2-element Constraint applies to two elements, such as two classes or two associations.
An OR Constraint indicates that any instance of a class may participate in only one association at one time. The constraint is shown as a dashed line connecting two or more associations, which must have a class in common. Right-click the object, select Shape Display Options , and in the dialog box, select the Destruction marker box.
UML diagrams in Visio.
0コメント