UML Weekend Crash Course™ - To Parent Directory

266
Sunday Morning
Deployment diagrams can also function like network diagrams to illustrate the make-up
of your network. The object-level Deployment diagram can function as a requirements specification
for each node, defining the memory, processor, and storage requirements.
Mapping Software Components to an Architecture
The more common technique for modeling the components on a node is to combine the two
physical diagram notations for components and nodes. Model the component icons inside
the expanded node to show containment. To show the logical communication between the
components, draw a dashed dependency arrow just like you did on the Component diagram.
In Figure 26-3, the orderentry.exe resides on the server but is loaded onto the client at
runtime. The stereotype specifies this runtime migration. After the executable
is loaded, it depends on the orderproc.exe for help. Note that I could have drawn this at the
class level just as easily. But here I am modeling the fact that the logical design represented
by the classes has, in fact, been implemented in this physical architecture.
dept234:Server
orderdesk3:Client
orderproc.exe
orderentry.exe
orderentry.exe
Figure 26-3
Combined Component and Deployment diagrams
Applying the Combined Diagrams to the Case Study
In this section, you’ll build the combined Deployment and Component diagram for the case
study step by step.
1. The hardware architecture consists of three kinds of devices: the client PC, a
middle-tier server, and a database server. Draw three nodes, one for each kind of
hardware resource (see Figure 26-4).