1. Ch. 28 Larman UML & Patterns
Activity Diagrams
Ch. 28 Larman UML & Patterns

2. Fig. 28.1 Rich notation: sequence & parallel activities
Business modeling: understand the structure and dynamics of the organization
Control & data flow
Automatic outgoing transition
DFD: Data Flow Diagram

3. Fig. 28.7 Any input leads to continuation
In contrast to join, in which case all inputs have to arrive before it continues, decision symbol continues if only one arrives
Guidelines: use activity diagrams for complex processes that involve many parties. Simple processes can be described with use case diagrams
Rake – subprocess, l2, l3 diagrams
Is this diagram complex enough to deserve an activity diagram?

4. Exercise Booking a Room in a hotel – Activity diagram
When customer requests a room, the hotel employee looks for room availability, then he insert customer’s data and verifies if the provided credit card number has enough credit to pay the room: in this case the booking is confirmed and we wait customer arrival.
The Hotel information system allows customer to modify or cancel his/her reservation. If customer arrives he uses the room and then he pays, in case of no-show a penalty is accounted on his credit card and the booking is canceled.