IS5411 Chap.5 Events and Use Case Discovery
Events and Use Case Discovery
Discovery needs several starting points
User-goal analysis begins with potential users and the tasks they seek to accomplish. Event decomposition begins with occurrences that require a response. CRUD analysis checks how remembered things are created, read, updated and deleted.
The techniques expose different omissions, so the strongest catalogue uses one to build a first list and the others to challenge it.
Events create required responses
External events originate outside the system, temporal events occur when a time is reached and state events arise when an internal condition changes. For each event, the analyst names the system response with a verb and noun.
The event is the business occurrence requiring action, not necessarily the actor's first visible interface gesture.
Completeness is relative to the boundary
A catalogue is complete enough when in-scope requests, scheduled obligations and meaningful state changes have responses, and every response can be traced to a goal or rule.
CRUD then identifies unmanaged information without mechanically creating four functions for every entity. Unresolved triggers and duplicate outcomes remain visible for stakeholder review.
What this chapter covers
- 01
User categories
- 02
User goals
- 03
CRUD coverage
- 04
External events
- 05
Temporal events
- 06
State events
- 07
Event tables
- 08
Catalogue review
Worked example · free
Respond to a reorder state
- 2Classify the triggering event.
- 4Name the business response and result.
- 2Use another technique to extend the analysis.
Key terms
- User Goal
- A result a particular actor seeks when interacting with the system.
- Event Decomposition
- A technique that discovers use cases by identifying occurrences requiring system responses.
- External Event
- An event initiated outside the system by an actor or external source.
- Temporal Event
- An event created by reaching a specified point in time.
- State Event
- An event created when an internal condition changes enough to require action.
- Event Table
- A catalogue connecting events, sources, use cases, destinations and results.
Events and Use Case Discovery FAQ
Which use-case discovery technique is most complete?
Event decomposition offers broad coverage because it includes external, temporal and state triggers, but users and data can still reveal gaps. Combine it with user-goal interviews and CRUD analysis. The techniques are valuable because their blind spots differ, not because one replaces the others.
How is an event different from a user action?
An event is the business occurrence that requires a system response. Typing into a field may be a step inside a use case, while a threshold change can create an event without a person acting at that moment. Follow the business consequence rather than the interface gesture.
Does CRUD create four use cases for every class?
No. CRUD is a coverage check and question generator. A missing update path may belong inside an existing business goal, deletion may be prohibited, and reading may support several goals. Return to stakeholders to identify the value and trigger before adding a use case. Treat every apparent gap as an investigation prompt, not an automatic new function.
Exam move
Build one use-case list from actor interviews, then attack it twice. Scan for external, temporal and state events with no response. Next create a lightweight CRUD matrix for the important domain things. For every gap, ask whether it reveals a new goal, a rule inside an existing use case or an out-of-scope responsibility. Create a compact event table with source, event, response, destination and stable result.
Challenge each row by asking whether the event is the true business trigger or merely an interface action inside a larger response. Look especially for scheduled obligations and internal thresholds, because users often remember external requests and omit work that begins without a person asking. Then compare outcomes to find duplicates described in different language.
Do not merge items only because their names resemble one another; merge them when they leave the same business result for the same relevant actors. End by reviewing the catalogue from two perspectives, one actor-centred and one subsystem-centred. Mark uncertain boundaries explicitly.
This routine prepares you to defend completeness without claiming that discovery is permanent or that every data operation deserves its own use case. For rapid revision, take each event type and invent one case where the trigger would be missed by a user-goal interview. Then explain how CRUD would test the resulting response for information maintenance without mechanically multiplying the use-case list.
Working through Events and Use Case Discovery in IS5411? Sia is AskSia’s AI Information Technology tutor — ask any IS5411 Events and Use Case Discovery 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.