An include relationship is denoted as a dashed arrow with the keyword
?«include?» . The arrowhead points to the use case that ??™ s being included. For example,
in Figure 3.34 the secondary use case determine car usage data is included
in the use cases show car usage data and end car usage .
You use an include relationship to model a scenario that you would execute in
exactly the same way if you weren ??™ t describing your use cases in UML, but instead
just in text fi les. You ??™ d swap common areas in a separate document, while only
inserting references in the original documents.
3.6 The Activity Diagram
An activity diagram is used wherever flows have to be described. From business
process modeling [33] to system use case flows to detailed descriptions of algorithms
and operations.
This diagram represents a model that describes the sequence of elementary
actions. This sequence can be split sequentially or into several fl ows, it can be
174 CHAPTER 3 UML??”Unifi ed Modeling Language
concurrent, it can be synchronized, or it branches in various alternatives based on
conditions.
Pages:
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350