UML Weekend Crash Course⢠- To Parent Directory
UML Weekend Crash Course⢠- To Parent Directory UML Weekend Crash Course⢠- To Parent Directory
SESSION 22 Modeling the Extended Features of the Statechart Session Checklist ✔ Explaining the various transition event types ✔ Explaining superstates and substates So far you’ve learned that events trigger transitions between states. Events come in a variety of forms, however. Clarifying at least five different event types, so that you know what to look for when you evaluate the problem statement, will be worth the time. In this section, I cover call events, time events, change events, send events, and guard conditions. I also explain how you can make these events conditional. Modeling Transition Events Figure 22-1 illustrates the Statechart diagram for an Order object. The Order is created in the initial state of Tentative. Two events could cause it to change to the Placed state. From Placed it may either be cancelled, or packed and made ready for shipping. After it is packed, it may be shipped. Then, whether it was cancelled or shipped, the Order is archived after 90 days.
228 Sunday Morning receivePmt(amt)[amt not < amt_due]/ placeOrder() Tentative authorizeOverride(mgr)/ placeOrder() Placed On entry/issueConf() Cancelled cancel(datetime) packed(packer)/ setPacked() Packaged after 3 days/upgradeShippingPriority() when today < (last update +90 days)/ setArchived() shipped(carrier, datetime)/ setShipped(), Customer.notify(Shipment, Order) Shipped Figure 22-1 when today < (last update + 90 days)/ setArchived() The Statechart for a typical Order object Call event A call event is the most common event type. It is basically the invocation of an operation on the receiving object. This type of event is the merge of an event and an event action. The event itself is an instruction to perform an operation. However, this doesn’t prevent you from adding other actions. Figure 22-2 shows the transition from Placed to Cancelled. The transition is triggered by the cancel(datetime) event. “cancel(datetime)” is actually the operation signature on the Order.
- Page 199 and 200: PART III # Saturday Afternoon Part
- Page 201 and 202: PART IV Saturday Evening Session 17
- Page 203 and 204: 180 Saturday Evening Scenario 1 Get
- Page 205 and 206: 182 Saturday Evening The next step
- Page 207 and 208: 184 Saturday Evening For Scenario 2
- Page 209 and 210: 186 Saturday Evening For subsequent
- Page 211 and 212: 188 Saturday Evening 6:addProduct(c
- Page 213 and 214: 190 Saturday Evening 7:addProduct(c
- Page 215 and 216: 192 Saturday Evening REVIEW The Col
- Page 217 and 218: 194 Saturday Evening Scenario 1 Get
- Page 219 and 220: 196 Saturday Evening pointing towar
- Page 221 and 222: 198 Saturday Evening :OrderFullfill
- 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 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 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
SESSION<br />
22<br />
Modeling the Extended<br />
Features of the Statechart<br />
Session Checklist<br />
✔ Explaining the various transition event types<br />
✔ Explaining superstates and substates<br />
So far you’ve learned that events trigger transitions between states. Events come in a<br />
variety of forms, however. Clarifying at least five different event types, so that you<br />
know what to look for when you evaluate the problem statement, will be worth the<br />
time. In this section, I cover call events, time events, change events, send events, and guard<br />
conditions. I also explain how you can make these events conditional.<br />
Modeling Transition Events<br />
Figure 22-1 illustrates the Statechart diagram for an Order object. The Order is created in<br />
the initial state of Tentative. Two events could cause it to change to the Placed state. From<br />
Placed it may either be cancelled, or packed and made ready for shipping. After it is packed,<br />
it may be shipped. Then, whether it was cancelled or shipped, the Order is archived after<br />
90 days.
Change language