UML Weekend Crash Course™ - To Parent Directory

SESSION
16
Modeling the Dynamic View:
The Sequence Diagram
Session Checklist
✔ Reviewing the dynamic view
✔ Defining the purpose of the Sequence and Collaboration diagrams
✔ Modeling the Sequence diagram notation
The static view (Class and Object diagrams) represents how the objects are defined and
arranged into a structure. It does not tell you how the objects behave when you put
them to work. In contrast, the dynamic view represents the interactions of the objects
in a system. The dynamic view contains diagrams specifically designed to model how the
objects work together. It can represent how the system will respond to actions from the
users, how it maintains internal integrity, how data is moved from storage to a user view,
and how objects are created and manipulated.
Understanding the Dynamic View
Because system behaviors can be complex, the dynamic view tends to look at small, discrete
pieces of the system like individual scenarios or operations. You may not see the dynamic
view used as extensively as the Class diagram, simply because not all behaviors are complicated
enough to warrant the extra work involved. Even so, the Class diagram and the diagrams
of the dynamic view are the most often used diagrams in projects because they most
directly reveal the specific features required in the final code.