Made with
ConceptDraw
DIAGRAM 14

Sequence Diagram Tool

The definition of the Unified Modelling Language can be found in other articles on this site, but to remind about it, we can mention that it is basically one of the developmental, general-purpose as well as modelling languages widely used in software engineering for providing a standard way for visualizing the design of a system, being originally developed for standardizing the disparate notational systems as well as approaches to software design in 1994. It was better developed by its “inventors” through 1996 and already in 1997 it was adopted as a standard by the so called “Object Management Group”, being managed by this organization ever since.

In 2005 UML was also published by the well-known “ISO” (“International Organization for Standardization”) as an approved ISO standard, after what it was revised to cover the latest revisions. Unified Modelling Language (or simply “UML”) provides an opportunity to visualize a system's architectural blueprints in a diagram. The elements of such diagram can be individual components of the system, activities or simply “jobs”, external user interface, with help of which it’s not a problem to represent the process of their interaction with other software components and follow the way the system can run as well as to see how the mentioned entities can interact with other components and interfaces.

The mentioned “UML” was extended to a larger set of design documentation, becoming very useful in many contexts, such as in software development, being designed to become compatible with the leading object-oriented software development methods, such as “Booch method”, “OMT” (object-modelling technique), so called “objectory” (or simply “object-oriented methodology”) and “RUP”, which is a Rational Unified Process — an iterative software development process framework created by the “Rational Software Corporation”.

It is important to describe the UML model correctly, opposing it to the other diagrams of a system. At the same time, a model may also contain documentation that drives the model elements and diagrams, for example the “written use cases”. All the “UML diagrams” represent two different views of a system model, which is a dynamic (also known as “behavioural”) view and a static one (known as “structural”). Thus, a dynamic view is used for showing the collaborations among different objects as well as changes to the internal states of such objects, which includes creating diagrams, such as “activity” ones, “state machine” ones and “sequence” ones. At the same time, the static view insists on the static structure of the system using attributes, objects, relationships and operations. The last view includes composite structure diagrams as well as the class diagrams.

Using the “XML Metadata Interchange” format (widely known as simply “.xmi” one), which is an object management group standard, used for exchanging any metadata information via XML means enabling the UML models to be exchanged among UML tools. “UML 2” has many different types of diagrams, divided into two categories, representing both structural information and general types of behaviour, including some, which represent different aspects of different interactions. The mentioned diagrams can be categorized as a hierarchy, including so called “interaction diagrams”, emphasizing the flow of data and control among the things in the system, which are being modelled. Thus, the “sequence diagram” shows the way objects communicate with each other, taking into consideration a sequence of messages.

The mentioned sequence diagram is basically one of the interaction diagrams, showing the way different objects operate with each another, also illustrating the order of such operation. Sequence diagram is known to be a construct of a “message sequence chart”, showing the object interactions arranged in a time sequence and depicting such objects as well as classes involved in the scenario. Within the sequence diagram, there’s a representation of the sequence of messages exchanging between the objects, which have to carry out the scenario, or, if to be clearer, its functionality.

All sequence diagrams can be associated with “use case realizations” due to the “Logical View” of any system, which is being under development. They can be also called as “event diagrams” (or “event scenarios”) and they all can be always created with the usage of ConceptDraw DIAGRAM drawing software. In order to show different objects or processes living simultaneously, you can draw the parallel vertical lines (so called “lifelines”) and to illustrate the messages exchanged between such objects, you can always draw the horizontal arrows in the needed order — the one, in which they occur, allowing the opportunity to show the specification of simple runtime scenarios in a graphical manner to appear.

If the mentioned “lifeline”, represented as the parallel vertical lines, is that of an object, then it’s known to be demonstrating a “role”. If you leave the instance name blank, then you represent unnamed and anonymous instances. Those messages, which are written with a use of horizontal arrows with the message name written just above them, display “interaction”, when solid arrow heads represent so called “synchronous calls”. The asynchronous messages are represented in a way of using the open arrow heads and the reply messages are represented simple by the dashed lines.

In case a caller sends a synchronous message, then it must wait until this message is done, but if he sends an asynchronous message, then it can continue processing and there’s no need to wait for any response. Asynchronous calls can be presented in the multi-threaded applications as well as in so called “message-oriented middleware”. Method-call boxes (also known as “activation boxes) are illustrated as the opaque rectangles, which are drawn on top of “lifelines” in order to represent that process is being performed in response to the message.

ConceptDraw DIAGRAM diagramming and vector drawing software as a sequence diagram tool provides the Rapid UML Solution from the Software Development Area that contains the UML Sequence library.

Sequence Diagram Tool *

Example 1. Sequence Diagram Tool

The UML Sequence library from the Rapid UML Solution includes 50 vector objects for quick and easy designing the UML Sequence diagrams of any complexity. Simply drag the needed objects to the document and arrange them to make a desired sequence diagram.

Sequence Diagram Tool - UML Sequence Library Design Elements

Example 2. Sequence Diagram Tool — UML Sequence Library Design Elements

Another way of your own sequence diagram creating is to use as the base already predesigned sequence diagrams included in Rapid UML solution and located in ConceptDraw STORE.

UML Sequence Diagram - Help Desk

Example 3. UML Sequence Diagram — Checking Process

In the case of using the offered template or sample, you need to choose the most suitable for you from the set and change it according to your needs.

UML Sequence Diagram - Checking Process

Example 4. UML Sequence Diagram — Help Desk

The Sequence diagrams you see on this page were created in ConceptDraw DIAGRAM using the vector objects from the UML Sequence library of Rapid UML Solution. An experienced user spent 10 minutes creating every of these samples. All these examples are available for ConceptDraw users from ConceptDraw STORE.

Use the Rapid UML solution to create your own UML diagrams of any type quick, easy and effective.

All source documents are vector graphic documents. They are available for reviewing, modifying, or converting to a variety of formats (PDF file, MS PowerPoint, MS Visio, and many other graphic formats) from the ConceptDraw STORE. The Rapid UML Solution is available for all ConceptDraw DIAGRAM or later users.







TEN RELATED HOW TO's:

Data Flow Diagram Process →

When you are a beginner in software development, you make a lot of mistakes. Developing logical models, or data flow diagrams is a way to see the the whole project and all the processes clearly. And some novices, unfortunately for them, miss modeling stage at the beginning of project life cycle, and get into troubles as the project grows. This image represents the data flow diagram applying symbols of Yourdon and Coad notation. This DFD depicts the data flow inside an organization department deals with receivables. The icons of standard Yourdon and Coad notation provides possibility to draw professional looking and well- readable DFD for business documentation. This data flow diagram was designed with the help of ConceptDraw DIAGRAM and its Data Flow Diagrams solution. The solution delivers three vector graphic libraries including elements of Yourdon and Coad and Gane-Sarson notations.Data Flow Diagram Process *
Picture: Data Flow Diagram Process
Related Solution:

UML Diagram for System →

This sample shows the UML Class Diagram of delivery system. On this diagram you can see the classes that are connected with aggregation and composition associations indicated with the multiplicity. This sample can be used by delivery services, postal services.UML Diagram for System *
Picture: UML Diagram for System
Related Solution:

UML Use Case Diagram Example - Estate Agency →

UML Diagram Estate Agency. This sample was created in ConceptDraw DIAGRAM diagramming and vector drawing software using the UML Use Case Diagram library of the Rapid UML Solution from the Software Development area of ConceptDraw Solution Park. This sample shows the work of the estate agency and is used by the estate agencies, building companies, at the trainings of the estate agencies, for understanding the working processes of the estate agencies.UML Use Case Diagram Example - Estate Agency *
Picture: UML Use Case Diagram Example - Estate Agency
Related Solution:

UML Flowchart Symbols →

The UML diagram is a powerful tool which lets visually represent all system's components, the interactions between them and relationships with external user interface. The Rapid UML solution for ConceptDraw DIAGRAM software offers diversity of UML flowchart symbols for drawing all types of UML diagrams.UML Flowchart Symbols *
Picture: UML Flowchart Symbols
Related Solution:

UML Timing Diagram, Design Elements →

UML Timing Diagram as special form of a sequence diagram are used to explore the behaviors of objects throughout a given period of time. ConceptDraw has 393 vector stencils in the 13 libraries that helps you to start using software for designing your own UML Diagrams. You can use the appropriate stencils of UML notation from UML Timing library.UML Timing Diagram, Design Elements *
Picture: UML Timing Diagram, Design Elements
Related Solution:

Business process Flow Chart — Event-Driven Process chain (EPC) diagrams →

Event-Driven Process chain Diagrams for improvement throughout an organisation. Best software for Process Flow Diagram. The Event-driven Process Chain (EPC) Diagrams allows managers to plan processes and resources.Business process Flow Chart — <br>Event-Driven Process chain (EPC) diagrams *
Picture: Business process Flow Chart — Event-Driven Process chain (EPC) diagrams
Related Solution:

About UML →

Use Case Diagram Taxi Service UML. This sample was created in ConceptDraw DIAGRAM diagramming and vector drawing software using the UML Use Case Diagram library of the Rapid UML Solution from the Software Development area of ConceptDraw Solution Park. This sample shows the work of the taxi service and is used by taxi stations, by airports, in the tourism field and delivery service.About UML *
Picture: About UML
Related Solution:

How to create a UML Diagram →

ConceptDraw DIAGRAM extended with the Rapid UML solution is perfect for drawing professional UML diagrams.How to create a UML Diagram *
Picture: How to create a UML Diagram
Related Solution:

An Event-driven Process Chain (EPC) - flowchart used for business process modelling →

Event-Driven Process Chain flowcharts for improvement throughout an organisation. ConceptDraw DIAGRAM is a software for making EPC flowcharts to provide business process modelling. Its excellent business process improvement tools.An Event-driven Process Chain (EPC) - <br>flowchart used for business process modelling *
Picture: An Event-driven Process Chain (EPC) - flowchart used for business process modelling
Related Solution:

How to Simplify Flow Charting — Cross-functional Flowchart →

In ConceptDraw DIAGRAM it really is sp simple to draw even the most complex cross-functional flowcharts. Use the RapidDraw technology and Cross-Functional libraries in ConceptDraw DIAGRAM for the best results.How to Simplify Flow Charting — Cross-functional Flowchart *
Picture: How to Simplify Flow Charting — Cross-functional Flowchart
Related Solution:
ConceptDraw
DIAGRAM 14