City University of Hong Kong · FACULTY OF INFORMATION TECHNOLOGY

IS5411 Chap.8 System Sequence Diagrams

- one subject, every graph, every model, every mark
8 Chapters4-page Bible
Our own words - no uploaded lecturer files
Updated for this semester
Chapter 8 of 8 · IS5411

System Sequence Diagrams

The system remains one black box

A system sequence diagram shows ordered input and output messages for one use-case scenario. External actors have lifelines and the entire system appears as one object.

Databases, controllers and interface components remain hidden because they answer design questions rather than the analytical question of what crosses the automation boundary.

Messages express business intent

An input message names what the actor asks the system to do and carries required information. A return message provides requested information, confirmation, status or reason.

Interface gestures and internal computations are omitted. Conditions and repetition appear only when the validated use-case flow requires them.

Several models must agree

The activity flow shows work and decisions, the system sequence shows boundary exchanges and the domain model shows durable things.

A message that creates a booking should leave a Booking in the domain model; a use-case rejection promising a reason should return that reason. Mismatches are requirement questions, not merely drawing errors.

In this chapter

What this chapter covers

  • 01

    Actor lifelines

  • 02

    Black-box systems

  • 03

    Input messages

  • 04

    Return messages

  • 05

    Time order

  • 06

    Conditions

  • 07

    Repetition

  • 08

    Cross-view reconciliation

Worked example · free

Sequence an equipment return

Q [10 marks]. AskSia-authored practice. A staff member returns a tagged item, records condition and closes a loan when all items are back. State the boundary messages. The marks shown are an AskSia study allocation.
The lifelines show ordered input and return messages while hiding all internal components behind one system object.The lifelines show ordered input and return messages while hiding all internal components behind one system object.Messages cross the black-box boundary in time orderActorSystemsubmitRequest(data)requestReferencecheckStatus(reference)currentStatus
The lifelines show ordered input and return messages while hiding all internal components behind one system object.
  • 2Identify actor and precondition.
  • 5Order the business-level inputs and returns.
  • 3Keep internal work hidden and state an alternative.
This mark allocation supports independent AskSia practice and is not an official University marking scheme. Staff sends scanItem(itemId), and the system returns loanSummary. Staff sends recordCondition(itemId, condition), and the system returns returnStatus showing either remaining items or closed loan, followed by a receipt reference. Internal inspection and storage remain hidden. A damage path that requires manager approval introduces another actor and should be modelled as a separate scenario.
Sia tip — Read the diagram aloud from the actor's perspective; any invisible fact needed by the story signals a missing message or precondition.
Glossary

Key terms

System Sequence Diagram
A UML interaction view showing actor-system messages in time order for one scenario.
Lifeline
The vertical time path associated with an actor or the black-box system.
Input Message
A business-level request sent from an external actor to the system.
Return Message
Information or a business result sent from the system back to an actor.
Guard Condition
A condition controlling whether a message or interaction path occurs.
Black-box System
A system represented by observable boundary behaviour while internal components remain hidden.
FAQ

System Sequence Diagrams FAQ

Why are databases omitted from a system sequence diagram?

The diagram models the observable interaction contract between external actors and the system as one object. A database is an internal design component. Showing it opens the black box and answers a different question about implementation rather than required boundary messages.

Should return messages always be shown?

Show returns the actor needs to continue, understand the result or establish traceability. Confirmation, requested data, status and rejection reasons can be essential obligations. Omitting them may hide a mismatch with the use-case description even when the inputs look correct.

When should an alternative get a separate diagram?

A small validation failure can fit as an alternative return. Use a separate scenario when the path introduces another actor, materially changes the set of messages or ends in a different stable result. Name the scenario so reviewers can trace it back to the use case. Separate diagrams are clearest when the business conversation, not merely one return value, changes.

Study strategy

Exam move

Select one fully developed use-case scenario and underline every actor-system exchange. Convert intentions into business-level messages, add required returns and hide all internal work. Read the sequence from top to bottom, then reconcile each result with the domain model and each condition with the written flow. Redraw a materially different alternative separately.

Practise removing interface and design language: replace click, page and database operations with messages that express business intent and required information. Add a return wherever the actor needs confirmation, requested data, status or a reason to continue. Test the black-box rule by circling every internal component; none belongs on the system sequence diagram.

For guards and loops, write the business rule beside the notation and verify that it appears in the use-case description. Narrate the finished diagram aloud from the actor's perspective. If the narration needs an unstated fact, add a precondition or message. If the diagram creates or changes a durable business thing, confirm that the domain model represents the result.

This final reconciliation is more valuable than adding extra notation. For a speed drill, take a short scenario and produce only the actor, system, inputs and necessary returns. Add conditions after the basic conversation is correct. This order prevents notation from obscuring the required exchange and makes alternative scenarios easier to separate.

Working through System Sequence Diagrams in IS5411? Sia is AskSia’s AI Information Technology tutor — ask any IS5411 System Sequence Diagrams question and get a clear, step-by-step explanation grounded in how IS5411 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.

A+Everything unlocked
Unlocks this Bible + all 31 of your subjects at City University of Hong Kong, plus 1,000+ more Bibles across the AskSia library.
Sia - your IS5411 tutor, unlimited, worked the way the exam marks it
The full 4-page Bible + practice bank with worked solutions
Chrome extension - sync your LMS so Sia knows your deadlines
Bilingual EN / Chinese on every Bible and every Sia answer
$0.99 Trial
30-day money-back · cancel in one tap · how it works