Java Reference
In-Depth Information
functionality (such as real-time applications) and for complex
scenarios where time dependencies are critical. It has two
aspects namely Time and Various objects participating in a
sequence of events required for a purpose.
Usually the sequence of events to which the objects of the
system are subject is important in real-time applications, the
time axis is an important measurement. This view identifies
the roles of the objects in your system through the sequence
of states they traverse to accomplish the goal. This view is an
event driven perspective of the system. The relationships
among the roles are not shown. Class and object diagrams
present such static views. Sequence and interaction diagrams
are dynamic. They describe how objects collaborate or
interact. A sequence diagram is an interaction diagram that
details the functionality and messages (requests and
responses) and the timing. The time progresses as you move
down the page. The objects involved in the operation are
listed from left to right according to when they take part in the
message sequence. The sequence diagram can have a
clarifying note, text inside a dog-eared rectangle. Notes can
be put into any kind of UML diagram.
Sequence diagrams are models of business processes that
represent the different interactions between actors and objects
in the system. Each process has a process owner and goals
(such as cycle time, defect rate, and cost) and consists of a set
of business activities (in sequence and/or in parallel).
Sequence or collaboration diagram should be covered for
each specified use case. Do not roll one or more use cases
together into a single diagram to save time. Sequence
diagrams should be clear and broadly map to the complexity
