Object Oriented Software Engineering   View all facts   Glossary   Help
subject > representation > coding technique > diagram > UML diagram > interaction diagram > sequence diagram
Next interaction diagramcollaboration diagram    Upinteraction diagram

sequence diagram
subjectfact 
sequence diagramarranges objects from left to right across the diagram with an actor that initiates the interaction often shown on the left2001-08-30 14:57:28.0
has definition A UML interaction diagram showing the sequence of messages exchanged by the set of objects and optionally an actor. Actors and objects are on one axis, and time is on the other2001-08-30 14:57:28.0
has part activation box2001-08-30 14:57:28.0
has part iteration expression2001-08-30 14:57:28.0
has part lifeline2001-08-30 14:57:28.0
is better than collaboration diagram when:
  • You want the reader to be able to easily see the order in which messages occur
  • You want to build an interaction model from a use case
  • You need to show details of messages, such as parameters and return values
2001-08-30 14:57:28.0
is a subtopic of 5.1 - What is UML?2001-08-30 14:57:28.0
is a kind of interaction diagram2001-08-30 14:57:28.0
represents iteration over objects by preceding the message name with an asterisk, and showing an iteration expression in square brackets2001-08-30 14:57:28.0
represents message as an arrow between activation boxes of the sender and receiver2001-08-30 14:57:28.0
represents time as the vertical dimension with time progressing downwards to the bottom of the diagram2001-08-30 14:57:28.0
shows the destruction of an object using a big 'X' symbol on a lifeline2001-08-30 14:57:28.0
shows the sequence of messages exchanged by the set of objects (and optionally an actor) performing a certain task2001-08-30 14:57:28.0
interaction diagramcan be used to define the protocol used when two components communicate with each other2001-08-30 14:56:01.0
can contain more or less detail depending on what you wish to communicate2001-08-30 14:56:01.0
has purpose to better understand the sequence of messages2001-08-30 14:56:01.0
helps you to visualize how the system runs2001-08-30 14:56:01.0
models the dynamic aspects of a software system2001-08-30 14:56:01.0
should be created after developing a class diagram and a use case model because you need to know the actors and objects involved in an interaction2001-08-30 14:56:01.0
UML diagramdescribes aspects of the architectural model2001-08-30 14:58:07.0
has part constraint2001-08-30 14:58:07.0
has part note2001-08-30 14:58:07.0
see also Unified Modelling Language2001-08-30 14:58:07.0
diagramhas advantages it conveys or summarizes complex concepts or mechanisms more easily than other techniques2001-08-30 14:55:19.0
has problems
  • can be hard for users to interact with or interpret
  • not usable by blind people
  • it can be expensive to program diagram drawing software
2001-08-30 14:55:19.0
should have a label if its meaning is not obvious, using a caption or pop-up label that appears when the user moves the mouse over it2001-08-30 14:55:19.0

Kinds of sequence diagram :

Next interaction diagramcollaboration diagram    Upinteraction diagram