Products Solutions Samples Buy
✕
This site uses cookies. By continuing to browse the ConceptDraw site you are agreeing to our Use of Site Cookies.
This vector stencils library contains 32 SysML symbols.
Use it to design your sequence diagrams using ConceptDraw PRO diagramming and vector drawing software.
"A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order in which they occur. This allows the specification of simple runtime scenarios in a graphical manner. ...
If the lifeline is that of an object, it demonstrates a role. Leaving the instance name blank can represent anonymous and unnamed instances.
Messages, written with horizontal arrows with the message name written above them, display interaction. Solid arrow heads represent synchronous calls, open arrow heads represent asynchronous messages, and dashed lines represent reply messages. If a caller sends a synchronous message, it must wait until the message is done, such as invoking a subroutine. If a caller sends an asynchronous message, it can continue processing and doesn’t have to wait for a response. Asynchronous calls are present in multithreaded applications and in message-oriented middleware. Activation boxes, or method-call boxes, are opaque rectangles drawn on top of lifelines to represent that processes are being performed in response to the message (ExecutionSpecifications in UML).
Objects calling methods on themselves use messages and add new activation boxes on top of any others to indicate a further level of processing.
When an object is destroyed (removed from memory), an X is drawn on top of the lifeline, and the dashed line ceases to be drawn below it (this is not the case in the first example though). It should be the result of a message, either from the object itself, or another.
A message sent from outside the diagram can be represented by a message originating from a filled-in circle (found message in UML) or from a border of the sequence diagram (gate in UML)." [Sequence diagram. Wikipedia]
The vector stencils library "Sequence diagram" is included in the SysML solution from the Software Development area of ConceptDraw Solution Park.
Sequence diagram
Sequence diagram, sequence diagram,
Lifeline
Lifeline, lifeline,
Execution specification
Execution specification, execution specification,
Execution specification 2
Execution specification 2, execution specification,
Interaction use
Interaction use, interaction use,
Combined fragment
Combined fragment, sequence diagram, message, lifeline, combined fragment, alternative combined fragment, interaction operator alt, alternatives,
Combined fragment - Weak sequencing
Combined fragment - Weak sequencing, weak sequencing combined fragment, interaction operator seq,
Combined fragment - Alternatives
Combined fragment - Alternatives, alternative combined fragment, interaction operator alt, alternatives,
Combined fragment - Option
Combined fragment - Option, option combined fragment, interaction operator opt,
Combined fragment - Break
Combined fragment - Break, break combined fragment, interaction operator break,
Combined fragment - Parallel
Combined fragment - Parallel, parallel combined fragment, interaction operator par,
Combined fragment - Strict sequencing
Combined fragment - Strict sequencing, strict sequencing combined fragment, interaction operator strict,
Combined fragment - Loop
Combined fragment - Loop, loop combined fragment, interaction operator loop,
Combined fragment - Critical region
Combined fragment - Critical region, critical region combined fragment, interaction operator critical,
Combined fragment - Negative
Combined fragment - Negative, negative combined fragment, interaction operator neg,
Combined fragment - Assertion
Combined fragment - Assertion, assertion combined fragment, interaction operator assert,
Combined fragment - Ignore
Combined fragment - Ignore, ignore combined fragment, interaction operator ignore,
Combined fragment - Consider
Combined fragment - Consider, consider combined fragment, interaction operator consider,
State invariant / Continuations
State invariant / Continuations, continuation, state invariant,
Coregion
Coregion, coregion,
Creation event
Creation event, message, lifeline, execution specification, creation event,
Destruction event
Destruction event, message, lifeline, execution specification, destruction event,
Duration constraint
Duration constraint, duration constraint,
Duration observation
Duration observation, duration observation,
Time constraint
Time constraint, time constraint,
Time observation
Time observation, time observation,
Message, asynchronous signal
Message, asynchronous signal, asynchronous signal, message,
Message, synchronous call
Message, synchronous call, synchronous call, message,
Reply message
Reply message, reply message,
Lost message
Lost message, lost message,
Found message
Found message, found message,
General ordering
General ordering, general ordering,
Used Solutions
"An example scenario is presented to demonstrate how a common issue tracking system would work:
(1) A customer service technician receives a telephone call, email, or other communication from a customer about a problem. Some applications provide built-in messaging system and automatic error reporting from exception handling blocks.
(2) The technician verifies that the problem is real, and not just perceived. The technician will also ensure that enough information about the problem is obtained from the customer. This information generally includes the environment of the customer, when and how the issue occurs, and all other relevant circumstances.
(3) The technician creates the issue in the system, entering all relevant data, as provided by the customer.
(4) As work is done on that issue, the system is updated with new data by the technician. Any attempt at fixing the problem should be noted in the issue system. Ticket status most likely will be changed from open to pending.
(5) After the issue has been fully addressed, it is marked as resolved in the issue tracking system.
If the problem is not fully resolved, the ticket will be reopened once the technician receives new information from the customer. A Run Book Automation process that implements best practices for these workflows and increases IT personnel effectiveness is becoming very common." [Issue tracking system. Wikipedia]
The UML sequence diagram example "Ticket processing system" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.
UML sequence diagram
UML sequence diagram, lifeline, actor, lifeline, execution occurrence,
Used Solutions
The vector stencils library "Bank UML sequence diagram" contains 34 shapes for drawing UML sequence diagrams.
Use it for object-oriented modeling of your bank information system.
"A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order in which they occur. This allows the specification of simple runtime scenarios in a graphical manner.
Diagram building blocks.
If the lifeline is that of an object, it demonstrates a role. Leaving the instance name blank can represent anonymous and unnamed instances.
Messages, written with horizontal arrows with the message name written above them, display interaction. Solid arrow heads represent synchronous calls, open arrow heads represent asynchronous messages, and dashed lines represent reply messages. ...
Activation boxes, or method-call boxes, are opaque rectangles drawn on top of lifelines to represent that processes are being performed in response to the message (ExecutionSpecifications in UML).
Objects calling methods on themselves use messages and add new activation boxes on top of any others to indicate a further level of processing.
When an object is destroyed (removed from memory), an X is drawn on top of the lifeline, and the dashed line ceases to be drawn below it ...
A message sent from outside the diagram can be represented by a message originating from a filled-in circle (found message in UML) or from a border of the sequence diagram (gate in UML)." [Sequence diagram. Wikipedia]
This example of UML sequence diagram symbols for the ConceptDraw PRO diagramming and vector drawing software is included in the ATM UML Diagrams solution from the Software Development area of ConceptDraw Solution Park.
UML sequence diagram symbols
UML sequence diagram symbols, weak sequencing combined fragment, interaction operator seq, synchronous call, strict sequencing combined fragment, interaction operator strict, state invariant, constraint, reply message, parallel combined fragment, interaction operator par, option combined fragment, interaction operator opt, note, negative combined fragment, interaction operator neg, message to self, self message, self delegation, lost message, loop combined fragment, interaction operator loop, lifeline, interaction use, combined fragment, interaction operand, interaction constraint, gate, frame, found message, execution specification, entity, lifeline, destruction event, delete message, critical region combined fragment, interaction operator critical, create message, control, lifeline, continuation, state invariant, consider combined fragment, interaction operator consider, concurrent, comment note, break combined fragment, interaction operator break, boundary, lifeline, asynchronous call, assertion combined fragment, interaction operator assert, alternative combined fragment, interaction operator alt, alternatives, actor, lifeline,
Used Solutions
▸ ConceptDraw Solution Park ▸ Rapid UML ▸
▸ ConceptDraw Solution Park ▸ Business Process Diagram ▸
▸ ConceptDraw Solution Park ▸ Business Processes ▸