UML Weekend Crash Course™ - To Parent Directory

248
Sunday Morning
Shipping
Order
Processing
Figure 24-3 A bi-directional dependency
For simplicity’s sake, all the other dependencies illustrated in this session go only one
direction.
Dependency stereotypes
The package dependency may be labeled with a stereotype to describe the nature of the
dependency. The UML defines two dependency stereotypes, and .
The stereotype in Figure 24-4 means that the Receiving package adds a
Purchasing class (in this case the PurchaseOrder class) to itself at run time, allowing internal
references (references within the package) to the class without specifying the source
package name.
Purchasing
Receiving
Figure 24-4
The stereotype on a dependency
Tip
For Java programmers, the stereotype has the same effect as the
import statement in Java.
The stereotype in Figure 24-5 says that the Shipping subsystem will want to
communicate with the Receiving subsystem but will not actually pull the classes from
Receiving into Shipping at run time. At run time, you would then expect to see some object
from the Shipping subsystem making calls in the interface of the Receiving subsystem.
Receiving
Shipping
Figure 24-5
The stereotype on a dependency
Tip
There are a number of other stereotypes described in the UML specification
in the file 01-09-78 UML 1.4 Appendix A UML Standard Elements.pdf.