Java Reference
In-Depth Information
Deployment diagrams show the physical configurations of
software and hardware. The deployment diagram
complements the component diagram. It shows the
configuration of runtime processing elements such as servers
and other hardware and the software components, processes,
and objects that they comprise. Software component instances
represent runtime manifestations of classes. Components that
do not runtime entities do not appear on these diagrams they
are shown on component diagrams. Deployment diagram is a
graphical representation of nodes connected by
communication links or associations. Nodes may contain
component instances, which indicate that the component
resides and runs on the node. The deployment diagram can be
used to show which components run on which nodes. The
migration of components from node to node or objects from
component to component may also be represented.
Sequence
Diagram
-
from
Use
Cases
to
Sequence
Diagrams
Sequence diagram describes how groups of objects
collaborate in some behavior over time. It records the
behavior of a single use case. It displays objects and the
messages passed among these objects in the use case. A
design can have lots of methods in different classes. This
makes it difficult to determine the overall sequence of
behavior. This diagram is simple and logical, so as to make
the sequence and flow of control obvious.
The sequence diagram shows the explicit series of
interactions as they flow through the system to address the
desired
objective
or
result.
The
sequence
diagram
is
especially
useful
in
systems
with
time-dependent
