IS5411 Chap.6 Use Case Descriptions and Diagrams
Use Case Descriptions and Diagrams
Descriptions carry processing detail
Brief, intermediate and fully developed descriptions represent increasing detail about one system response. A brief form supports early catalogue review, an intermediate form gives the main successful flow, and a fully developed form records trigger, conditions, alternatives and stable outcomes.
Detail should be added when it changes understanding rather than as a ritual.
Diagrams carry scope and participation
A use-case diagram shows actors, use cases, the automation boundary and selected relationships. Actors remain outside the system because they initiate or receive responses. The diagram does not replace the written flow.
Different views may be drawn for a subsystem or actor when they answer distinct review questions while retaining one authoritative catalogue.
Relationships have direction and meaning
An include relationship represents shared behaviour invoked as a subroutine, and its arrow points toward the included use case. Data overlap alone does not justify inclusion.
Comparing descriptions and diagrams reveals missing actors, functions with no trigger and relationships pointing the wrong way.
What this chapter covers
- 01
Brief descriptions
- 02
Intermediate flows
- 03
Fully developed flows
- 04
Primary actors
- 05
Automation boundaries
- 06
Include relationships
- 07
Audience-specific views
- 08
Cross-view defects
Worked example · free
Describe a volunteer shift claim
- 4State the trigger, precondition and main flow.
- 3Add capacity and certification alternatives.
- 3Identify actors, boundary and included behaviour.
Key terms
- Brief Description
- A short statement of a use-case goal and outcome used during early review.
- Main Flow
- The normal successful sequence of actor intentions and system responses.
- Alternative Flow
- A branch followed when a condition changes the normal sequence or outcome.
- Primary Actor
- The external role that initiates a use case to obtain its result.
- Automation Boundary
- The line separating system behaviour from external actors and work.
- Include Relationship
- A directed use-case relationship invoking shared behaviour as a subroutine.
Use Case Descriptions and Diagrams FAQ
When should a use case be fully developed?
Use the full form when detailed rules, alternatives and outcomes are needed for modelling or design. Early in discovery, brief descriptions are cheaper and easier to revise. Increase detail in response to questions the current model cannot answer rather than completing every field automatically.
Why can one system have several use-case diagrams?
Different audiences need different views. A user may review an actor-centred diagram, while the project team reviews a subsystem boundary. The views can select different subsets while sharing consistent names and one underlying catalogue. One crowded page is not evidence of completeness.
Which way does an include arrow point?
It points from the larger use case toward the included behaviour that it invokes, like a shared subroutine. Use inclusion only when the behaviour is genuinely part of the calling use cases. Mentioning the same entity does not establish an include relationship. Confirm the shared behaviour appears inside every calling flow before drawing the arrow.
Exam move
Take one use case and write it first as a brief description, then as an intermediate main flow and finally as a fully developed description with alternatives. Draw an actor-centred diagram after the prose. Compare every actor, use case and include arrow against the written trigger and processing rather than relying on visual familiarity.
In the full version, pair each actor intention with an observable system response and attach every alternative to the step it changes. State the postcondition for success, rejection and recoverable failure. Remove clicks, pages and database operations unless they have business meaning. Next draw two views from the same catalogue: one for the primary actor and one for the subsystem team.
Give each view a review purpose and verify that selected subsets do not change names or relationships. Trace every include arrow toward genuinely shared behaviour and explain why data overlap alone is insufficient. Finally, compare prose and picture for contradictions.
An actor present in a flow but missing from the diagram, or a use case with no trigger or outcome, is a question about the requirement rather than a cosmetic drawing defect. Add a final spoken walkthrough in which one person plays the actor and another plays the system. The exercise exposes missing responses and unclear conditions faster than silently inspecting notation, especially when an alternative has no stable ending.
Working through Use Case Descriptions and Diagrams in IS5411? Sia is AskSia’s AI Information Technology tutor — ask any IS5411 Use Case Descriptions and 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.