0.4.12 Contrasting Object, Activity, and Class Diagrams

Three Views of One Training Rule

The Wildcats record whether a player is available. A structure view defines that information, a snapshot records its current value, and a flow view explains how the application uses it. These are complementary abstractions, not competing answers.

Class View: What Information Is Supported?
Player defines a text name and a Boolean availability attribute.
Player structure
  • New
  • Changed
  • Removed

This class supports different players and different values. It does not claim that a particular player is available now.

Object View: What Is True at This Pause?
Jordan is one Player instance with availability true at the selected pause.
One current Player instance
  • New
  • Changed
  • Removed

The instance follows the class structure and supplies particular values. The snapshot does not contain the action order that produced them.

Activity View: What Happens When Availability Is Checked?
The process selects an available player or leaves an unavailable player out of the round.
A process reads player state
  • New
  • Changed
  • Removed

The activity reads the same Boolean concept. Jordan's shown state takes the true route. If Jordan later becomes unavailable, the object value changes and this execution takes the false route; the Player attribute definition remains the same.

Choose Two Pieces of Evidence