UML Weekend Crash Course™ - To Parent Directory

326
Appendix A
15. A Sequence diagram only models one scenario. An object may participate in many
scenarios. So you need to use all the Sequence diagrams in which the object participates
to build one complete Statechart diagram for the object.
16. The Package diagram may be used just like any directory structure, to hold files of
any type including UML diagrams, documentation, and sample documents. The
most common usage is to organize the parts of the system into subsystems and
finally down to the Class diagrams that model the resources of the system.
17. The package stereotype helps to characterize the usage of the package. For
example, the stereotype describes a package that will only
contain classes and other packages that describe the makeup of the system. The
stereotype characterizes the package as a repository for project
work products.
18. The dependency arrow shows that one or more classes in one package needs to
interact with a class or classes in another package. The direction of the arrow indicates
who has the need (the base of the arrow) and who supplies the help (the
head of the arrow).
19. The dependency stereotype describes the nature of the dependency. The
stereotype indicates that at run time the dependent package will
bring the class from the other package into itself to use along with its own classes.
The stereotype indicates that the dependent package will want to call
on the class or classes at run time without bringing them into itself.
20. A package typically only contains other packages, a Class diagram.
But it may contain any of the UML diagrams.
21. Components represent the physical implementations of your software design.
22. Deployment components, which are required to run the system. Work product
components including models, source code, and data files used to create deployment
components. Execution components, components created while running the
application.
23. One way to draw a component interface is to use a class with the stereotype
attached to the component with a realization relationship. A second,
more common technique, is to use a “lollipop” attached to the component by
a realization relationship, which is shown simply as a solid line when the lollipop
notation is used.
24. Dependencies between components are drawn with the dashed arrow from the
dependent component to the component it needs help from.
25. A component may be built from one or more classes. The interfaces of the classes
in the component make up the interface to the component.
26. A node is a physical object that represents a processing resource. Most often, this
means a computer of some type, but it may also mean a human resource.
27. The connections are modeled as associations. The association is labeled with a
stereotype that describes the type of connection.
28. A node may contain components and objects (that is, only run time resources).
29. An association between nodes represents a physical communication path like a
cable. The dependency between components is a logical communication requirement.
This is why the mapping of the components onto the nodes is so valuable.