UML Weekend Crash Course⢠- To Parent Directory
UML Weekend Crash Course⢠- To Parent Directory UML Weekend Crash Course⢠- To Parent Directory
Session 14—Modeling the Functional View: The Activity Diagram 155 Synchronization Synchronization Figure 14-8 Merging control using the synchronization bar I should point out that identifying a concurrency opportunity does not necessarily dictate a concurrency requirement. It simply models the fact that sequential processing is not required, and if the implementation environment supports it, there may be a chance to optimize the performance of the application by exploiting the concurrency opportunity. REVIEW The Activity diagram is the UML version of the classic flowchart. It may be applied to any process, large or small. Three common applications of flowcharts are to explain workflow (a series of Use Cases), to explain a single Use Case, and to explain a method. The Activity diagram represents a task as an activity drawn as a rounded rectangle containing a freeform text description of the task. The transition from one activity to the next is shown as an arrow. The notation provides for start and end points, using a dot and a bull’s-eye, respectively. Model decisions with a diamond. Each transition exiting the decision must be labeled with a guard condition and the conditions must be mutually exclusive. The diamond may also be used to represent a merge point, joining two alternative paths in the sequence. Guard conditions may also be used on transitions leaving an activity, where the result of the activity provides all the information needed to meet one of the conditions. Concurrency allows multiple threads or processes to execute simultaneously. The fork bar shows one transition initiating multiple transitions. The synchronization bar shows multiple transitions coming to an end and one new transition taking over. QUIZ YOURSELF 1. Name two situations in which the Activity diagram is typically applied. (See “Introducing the Activity Diagram.”) 2. What notations indicate the start and end points in an Activity diagram (See “Start and end.”) 3. What symbol is used to show the start of concurrent processes (See “Concurrency.”) 4. How do you indicate the direction to follow out of a decision point (See “Decisions.”) 5. What is a transition (See “Activities and transitions.”)
- 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
- Page 159 and 160: 136 Saturday Afternoon Table 12-3 T
- Page 161 and 162: 138 Saturday Afternoon REVIEW The C
- Page 163 and 164: 140 Saturday Afternoon Introducing
- Page 165 and 166: 142 Saturday Afternoon Table 13-1 C
- Page 167 and 168: 144 Saturday Afternoon 28: VendorPr
- Page 169 and 170: 146 Saturday Afternoon 0..* VendorP
- Page 172 and 173: SESSION 14 Modeling the Functional
- Page 174 and 175: Session 14—Modeling the Functiona
- Page 176 and 177: Session 14—Modeling the Functiona
- Page 180 and 181: SESSION 15 Applying the Activity Di
- Page 182 and 183: Session 15—Applying the Activity
- Page 184 and 185: Session 15—Applying the Activity
- Page 186 and 187: Session 15—Applying the Activity
- Page 188: Session 15—Applying the Activity
- Page 191 and 192: 168 Saturday Afternoon Knowing the
- Page 193 and 194: 170 Saturday Afternoon A message or
- Page 195 and 196: 172 Saturday Afternoon Bill : Custo
- Page 197: 174 Saturday Afternoon REVIEW The d
- Page 200 and 201: Part III — Saturday Afternoon Par
- Page 202 and 203: SESSION 17 Applying the Sequence Di
- Page 204 and 205: Session 17—Applying the Sequence
- Page 206 and 207: Session 17—Applying the Sequence
- Page 208 and 209: Session 17—Applying the Sequence
- Page 210 and 211: SESSION 18 Modeling the Dynamic Vie
- Page 212 and 213: Session 18—Modeling the Dynamic V
- Page 214 and 215: Session 18—Modeling the Dynamic V
- Page 216 and 217: SESSION 19 Applying the Collaborati
- Page 218 and 219: Session 19—Applying the Collabora
- Page 220 and 221: Session 19—Applying the Collabora
- Page 222 and 223: Session 19—Applying the Collabora
- Page 224: Session 19—Applying the Collabora
- Page 227 and 228: 204 Saturday Evening When the curre
Session 14—Modeling the Functional View: The Activity Diagram 155<br />
Synchronization<br />
Synchronization<br />
Figure 14-8 Merging control using the synchronization bar<br />
I should point out that identifying a concurrency opportunity does not necessarily dictate<br />
a concurrency requirement. It simply models the fact that sequential processing is not<br />
required, and if the implementation environment supports it, there may be a chance to<br />
optimize the performance of the application by exploiting the concurrency opportunity.<br />
REVIEW<br />
The Activity diagram is the <strong>UML</strong> version of the classic flowchart. It may be applied to any<br />
process, large or small. Three common applications of flowcharts are to explain workflow (a<br />
series of Use Cases), to explain a single Use Case, and to explain a method.<br />
The Activity diagram represents a task as an activity drawn as a rounded rectangle<br />
containing a freeform text description of the task. The transition from one activity<br />
to the next is shown as an arrow. The notation provides for start and end points,<br />
using a dot and a bull’s-eye, respectively.<br />
Model decisions with a diamond. Each transition exiting the decision must be<br />
labeled with a guard condition and the conditions must be mutually exclusive. The<br />
diamond may also be used to represent a merge point, joining two alternative paths<br />
in the sequence.<br />
Guard conditions may also be used on transitions leaving an activity, where the result<br />
of the activity provides all the information needed to meet one of the conditions.<br />
Concurrency allows multiple threads or processes to execute simultaneously. The<br />
fork bar shows one transition initiating multiple transitions. The synchronization<br />
bar shows multiple transitions coming to an end and one new transition taking over.<br />
QUIZ YOURSELF<br />
1. Name two situations in which the Activity diagram is typically applied. (See<br />
“Introducing the Activity Diagram.”)<br />
2. What notations indicate the start and end points in an Activity diagram (See<br />
“Start and end.”)<br />
3. What symbol is used to show the start of concurrent processes (See “Concurrency.”)<br />
4. How do you indicate the direction to follow out of a decision point (See “Decisions.”)<br />
5. What is a transition (See “Activities and transitions.”)