UML Weekend Crash Course⢠- To Parent Directory
UML Weekend Crash Course⢠- To Parent Directory UML Weekend Crash Course⢠- To Parent Directory
Session 8—Identifying the Use Case Scenarios 85 For the FillOrder Use Case, I have drawn an Activity diagram (Figure 8-1) so that you can more easily see the logical steps involved in the execution of the Use Case. Get Order # Get Order (Find Order Use Case) Order Found [Yes] Display Order [No] Provide Error Message Done or no unfilled items [True] Any unfilled quantities [False] Choose Item [Yes] Create Back Order [No] Find Item (Locate Product) Use Case [No] Item Found Find Item Quantity [Yes] Reduce Inventory Figure 8-1 Activity diagram for Fill Order Use Case
86 Saturday Morning In Figure 8-2, trace the logic for the successful scenario first. Trace each step until you reach a decision point where the logic splits into multiple paths. Now you are faced with a choice. Scenario 1 Get Order # Get Order (Find Order Use Case) Order Found [Yes] [No] Figure 8-2 Trace the scenario to the first decision point.
- Page 59 and 60: 36 Friday Evening Remember to pay c
- Page 61 and 62: 38 Friday Evening Constraints The s
- Page 63 and 64: 40 Friday Evening An Inventory Cont
- Page 65 and 66: 42 Friday Evening Performance How
- Page 67 and 68: 44 Friday Evening In the effort to
- Page 70 and 71: Part II — Saturday Morning Sessio
- Page 72 and 73: SESSION 5 Understanding the Use Cas
- Page 74 and 75: Session 5—Understanding the Use C
- Page 76 and 77: Session 5—Understanding the Use C
- Page 78 and 79: Session 5—Understanding the Use C
- Page 80 and 81: Session 5—Understanding the Use C
- Page 82: Session 5—Understanding the Use C
- Page 85 and 86: 62 Saturday Morning Order Fulfillme
- Page 87 and 88: 64 Saturday Morning What does the
- Page 89 and 90: 66 Saturday Morning For example, th
- Page 91 and 92: 68 Saturday Morning REVIEW The goal
- Page 93 and 94: 70 Saturday Morning Much of this la
- Page 95 and 96: 72 Saturday Morning You reply that
- Page 97 and 98: 74 Saturday Morning Writing a Use C
- Page 99 and 100: 76 Saturday Morning Use Case dialog
- Page 101 and 102: 78 Saturday Morning Table 7-7 The F
- Page 104 and 105: SESSION 8 Identifying the Use Case
- Page 106 and 107: Session 8—Identifying the Use Cas
- Page 110 and 111: Session 8—Identifying the Use Cas
- Page 112 and 113: Session 8—Identifying the Use Cas
- Page 114: Session 8—Identifying the Use Cas
- Page 117 and 118: 94 Saturday Morning The Class diagr
- Page 119 and 120: 96 Saturday Morning Attribute visib
- Page 121 and 122: 98 Saturday Morning In a modeling t
- Page 123 and 124: 100 Saturday Morning Table 9-2 Cont
- Page 125 and 126: 102 Saturday Morning Operation comp
- Page 128 and 129: SESSION 10 The Class Diagram: Assoc
- Page 130 and 131: Session 10—The Class Diagram: Ass
- Page 132 and 133: Session 10—The Class Diagram: Ass
- Page 134 and 135: Session 10—The Class Diagram: Ass
- Page 136 and 137: Session 10—The Class Diagram: Ass
- Page 138 and 139: Part II — Saturday Morning Part R
- Page 140 and 141: SESSION 11 The Class Diagram: Aggre
- Page 142 and 143: Session 11—The Class Diagram: Agg
- Page 144 and 145: Session 11—The Class Diagram: Agg
- Page 146 and 147: Session 11—The Class Diagram: Agg
- Page 148 and 149: Session 11—The Class Diagram: Agg
- Page 150: Session 11—The Class Diagram: Agg
- Page 153 and 154: 130 Saturday Afternoon or not. Each
- Page 155 and 156: 132 Saturday Afternoon 5. “Any it
- Page 157 and 158: 134 Saturday Afternoon designed to
Session 8—Identifying the Use Case Scenarios 85<br />
For the FillOrder Use Case, I have drawn an Activity diagram (Figure 8-1) so that you can<br />
more easily see the logical steps involved in the execution of the Use Case.<br />
Get Order #<br />
Get Order<br />
(Find Order<br />
Use Case)<br />
Order<br />
Found<br />
[Yes]<br />
Display Order<br />
[No]<br />
Provide Error<br />
Message<br />
Done or<br />
no unfilled<br />
items<br />
[True]<br />
Any unfilled<br />
quantities<br />
[False]<br />
Choose Item<br />
[Yes]<br />
Create Back<br />
Order<br />
[No]<br />
Find Item<br />
(Locate Product)<br />
Use Case<br />
[No]<br />
Item<br />
Found<br />
Find Item<br />
Quantity<br />
[Yes]<br />
Reduce<br />
Inventory<br />
Figure 8-1<br />
Activity diagram for Fill Order Use Case
Change language