Sequence diagram

The notation of the UML sequence diagram: lifelines, synchronous, asynchronous and return messages, activation bars, creation and destruction, alt, opt and loop fragments.

  • 26 cards
  • 4 topics
  • Free

The outline, topic by topic

Each topic is weighted the way the exam weighs it.

  1. Concepts
  2. Questions
  3. Sort and link
  4. On the diagram

A few cards from the deck

  • Lifeline: what is it?

    Show the answer

    A dashed vertical line under a participant: it stands for its existence over time, which flows from top to bottom.

    A message is a horizontal arrow between two of these lines; the lower it sits, the later it happens.

  • On a diagram, a solid arrow goes from Client to Server, then a dashed arrow comes back to Client. What does this drawing mean in code?

    • A method call, with the value it returns
    • Two independent calls, in both directions
    • An asynchronous message, the client does not wait for the reply
    • The creation of a Server object by the client
    Show the answer

    A method call, with the value it returns

    A solid arrow then a dashed return: the classic synchronous call, the client waits. Two independent calls would have two solid arrows; an asynchronous one would have an open arrowhead.

  • The … fragment chooses between several branches separated by a dashed line; the … fragment only runs its messages when its condition is true.

    Show the answer

    The alt fragment chooses between several branches separated by a dashed line; the opt fragment only runs its messages when its condition is true.

    alt is an if … else, opt is an if with no else.

  • Synchronous message: what is it?

    Show the answer

    A call drawn as a solid line with a filled arrowhead: the sender waits for the processing to finish before going on.

    It is the ordinary method call: bank.checkCode(code) blocks the caller until it returns.