UML Weekend Crash Course™ - To Parent Directory

Session 25—Modeling the Static View: The Component Diagram 259
receiving.exe
purchaseorder.dll
Figure 25-6
Step 2: Adding a library component and drawing the dependency
3. Figure 25-7 adds two more resource components. The product.dll component allows
the Receiving application to update the product status to received. The inventory.dll
component supports checks on the availability of locations where they can
put the new product. It then adds the dependency from the Receiving.exe to the
product.dll to show that the Receiving.exe needs access to the product.dll, and the
dependency from the Receiving.exe to the inventory.dll to show that the
Receiving.exe needs access to the inventory.dll in order to update inventory.
receiving.exe
purchaseorder.dll
product.dll
inventory.dll
Figure 25-7 Step 3: Adding two more resource components and the dependencies
4. Figure 25-8 adds the client application that manages the user interface. The
Receiving application provides the PO (or Purchase Order) interface. Figure 25-8
models the interface using the lollipop notation. The user interface application
(ui.exe) accesses the Receiving application using the PO interface. This access is
modeled as a dependency from ui.exe to the PO lollipop style interface to illustrate
that the ui.exe will not work properly unless it can access the receiving application
through the PO interface.