UML Weekend Crash Course⢠- To Parent Directory
UML Weekend Crash Course⢠- To Parent Directory 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.
260 Sunday Morning receiving.exe PO ui.exe purchaseorder.dll product.dll inventory.dll Figure 25-8 Step 4: Adding the user interface application and the shared interface Mapping the Logical Design to the Physical Implementation Making components from classes involves choices about how to assemble these classes into cohesive units. The interfaces of the classes in the component make up the interface to the component. Figure 25-9 shows a database table component, orders.tbl, which implements the classes that define an order, namely Order, LineItem, and Product, and their association. orders.tbl OrderProcessing::Order 1..1 1..* OrderProcessing::LineItem 0..1 Figure 25-9 A component is created from classes. In like manner, the main program in an application may implement some or all of the key classes in the logical model. To create the executable in Figure 25-10, you compile the classes together into a single executable. 1..1 Purchasing:Product
- Page 232 and 233: Session 20—Modeling the Dynamic V
- Page 234: Session 20—Modeling the Dynamic V
- Page 238 and 239: Part V — Sunday Morning Session 2
- Page 240 and 241: SESSION 21 Applying the Basic State
- Page 242 and 243: Session 21—Applying the Basic Sta
- Page 244 and 245: Session 21—Applying the Basic Sta
- Page 246 and 247: Session 21—Applying the Basic Sta
- Page 248: Session 21—Applying the Basic Sta
- Page 251 and 252: 228 Sunday Morning receivePmt(amt)[
- Page 253 and 254: 230 Sunday Morning Figure 22-4 repr
- Page 255 and 256: 232 Sunday Morning A substate is a
- Page 257 and 258: 234 Sunday Morning Monitor when tem
- Page 260 and 261: SESSION 23 Applying the Extended St
- Page 262 and 263: Session 23—Applying the Extended
- Page 264 and 265: Session 23—Applying the Extended
- Page 266 and 267: Session 23—Applying the Extended
- Page 268 and 269: SESSION 24 Modeling the Development
- Page 270 and 271: Session 24—Modeling the Developme
- Page 272 and 273: Session 24—Modeling the Developme
- Page 274 and 275: Session 24—Modeling the Developme
- Page 276 and 277: Session 24—Modeling the Developme
- Page 278 and 279: SESSION 25 Modeling the Static View
- Page 280 and 281: Session 25—Modeling the Static Vi
- Page 284 and 285: Session 25—Modeling the Static Vi
- Page 286 and 287: SESSION 26 Modeling the Static View
- Page 288 and 289: Session 26—Modeling the Static Vi
- Page 290 and 291: Session 26—Modeling the Static Vi
- Page 292 and 293: Session 26—Modeling the Static Vi
- Page 294 and 295: Session 26—Modeling the Static Vi
- Page 296 and 297: PART # V Sunday Morning Part Review
- Page 299 and 300: PART VI Sunday Afternoon Session 27
- Page 301 and 302: 278 Sunday Afternoon design, and mo
- Page 303 and 304: 280 Sunday Afternoon :User :Web Br
- Page 305 and 306: 282 Sunday Afternoon studied Java p
- Page 307 and 308: 284 Sunday Afternoon and time. A JS
- Page 310 and 311: SESSION 28 Analysis and Architectur
- Page 312 and 313: Session 28—Analysis and Architect
- Page 314 and 315: Session 28—Analysis and Architect
- Page 316 and 317: Session 28—Analysis and Architect
- Page 318 and 319: Session 28—Analysis and Architect
- Page 320 and 321: SESSION 29 Design of a Web Applicat
- Page 322 and 323: Session 29—Design of a Web Applic
- Page 324 and 325: Session 29—Design of a Web Applic
- Page 326 and 327: Session 29—Design of a Web Applic
- Page 328 and 329: Session 29—Design of a Web Applic
- Page 330 and 331: SESSION 30 UML Modeling Tools Sessi
260<br />
Sunday Morning<br />
<br />
receiving.exe<br />
PO<br />
<br />
ui.exe<br />
<br />
purchaseorder.dll<br />
<br />
product.dll<br />
<br />
inventory.dll<br />
Figure 25-8<br />
Step 4: Adding the user interface application and the shared interface<br />
Mapping the Logical Design to the Physical Implementation<br />
Making components from classes involves choices about how to assemble these classes into<br />
cohesive units. The interfaces of the classes in the component make up the interface to the<br />
component. Figure 25-9 shows a database table component, orders.tbl, which implements<br />
the classes that define an order, namely Order, LineItem, and Product, and their association.<br />
<br />
<br />
orders.tbl<br />
OrderProcessing::Order<br />
1..1<br />
<br />
<br />
1..*<br />
OrderProcessing::LineItem<br />
0..1<br />
Figure 25-9 A component is created from classes.<br />
In like manner, the main program in an application may implement some or all of the<br />
key classes in the logical model. <strong>To</strong> create the executable in Figure 25-10, you compile the<br />
classes together into a single executable.<br />
1..1<br />
Purchasing:Product
Change language