UML Weekend Crash Course⢠- To Parent Directory
UML Weekend Crash Course⢠- To Parent Directory UML Weekend Crash Course⢠- To Parent Directory
Session 24—Modeling the Development Environment 251 Purchasing Receiving Shipping Figure 24-9 Step 3: Adding a dependency 4. Stereotype the dependency between Receiving and Purchasing as to show that Receiving makes references to classes within Purchasing by adding them into its own set of classes at run time. Figure 24-10 shows the addition of the stereotype. Purchasing Receiving Shipping Figure 24-10 Step 4: Adding the dependency stereotype 5. Add the stereotype to the dependency between Shipping and Receiving to show that Shipping needs to communicate with classes within Receiving without actually making them part of the Shipping subsystem at run time. Instead, the classes in the Shipping subsystem will make calls to one or more classes in Receiving. Figure 24-11 places the stereotype on the dashed dependency arrow between Shipping and Receiving.
252 Sunday Morning Purchasing Receiving Shipping Figure 24-11 Step 5: Adding the dependency stereotype 6. Add a package to handle the order processing requirements of the system. The new package, Order Processing, is modeled as a folder icon just like the other packages. The name is placed inside the icon. The package should be recognizable as a subsystem, so the stereotype is placed above the name. The Order Processing package needs to use the Inventory class in the Receiving package, so it pulls the class into itself to work with it. This requirement is implemented in Figure 24-12 with a dashed dependency arrow from Order Processing to Receiving using the dependency stereotype. Purchasing Receiving Order Processing Shipping Figure 24-12 stereotype Step 6: Adding Order Processing and the dependency
- Page 223 and 224: 200 Saturday Evening Scenario 5, in
- Page 226 and 227: SESSION 20 Modeling the Dynamic Vie
- Page 228 and 229: Session 20—Modeling the Dynamic V
- Page 230 and 231: Session 20—Modeling the Dynamic V
- 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 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 282 and 283: 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
252<br />
Sunday Morning<br />
<br />
Purchasing<br />
<br />
<br />
Receiving<br />
<br />
<br />
Shipping<br />
Figure 24-11<br />
Step 5: Adding the dependency stereotype<br />
6. Add a package to handle the order processing requirements of the system. The new<br />
package, Order Processing, is modeled as a folder icon just like the other packages.<br />
The name is placed inside the icon. The package should be recognizable as a subsystem,<br />
so the stereotype is placed above the name. The Order<br />
Processing package needs to use the Inventory class in the Receiving package, so it<br />
pulls the class into itself to work with it. This requirement is implemented in<br />
Figure 24-12 with a dashed dependency arrow from Order Processing to Receiving<br />
using the dependency stereotype.<br />
<br />
Purchasing<br />
<br />
<br />
Receiving<br />
<br />
<br />
<br />
Order<br />
Processing<br />
<br />
Shipping<br />
Figure 24-12<br />
stereotype<br />
Step 6: Adding Order Processing and the dependency
Change language