0.3.9 Contrasting Object and Activity Diagrams

Compare a State Snapshot with a Process

The Wildcats coach asks two questions: Is Jordan available now? What steps should the coach follow when choosing a drill? Those questions concern the same soccer situation, but they need different evidence.

An object diagram records selected state at one moment. An activity diagram records possible action order and route choices. Using two small diagrams keeps each question clear.

The Current Player State
At this pause, Jordan is an unavailable Player. The snapshot shows no reason or action history.
A snapshot says Jordan is unavailable
  • New
  • Changed
  • Removed

This box answers the current-availability question. It does not explain why Jordan became unavailable, whether a notification was sent, or what should happen next.

The Rule for Choosing a Drill Participant
Read availability, invite an available player or choose another player when unavailable, then finish this selection attempt.
A process responds to the stored availability
  • New
  • Changed
  • Removed

The diamond reads state; its answer selects work. For the Jordan snapshot, follow false to Choose another player. That path is consistent with the snapshot, but it does not prove the process has already executed.

Choose the View Before Drawing
  1. If the question is what exists or what is currently stored, choose an object snapshot and name its pause.
  2. If the question is what happens next or under which condition, choose an activity and name its boundary.
  3. Compare the two for consistency without adding arrows that invent missing history.