initial node activity diagram activity edge (control flow) [accepted] construction system (not automated) University of Toronto at Scarborough © Kersti Wain-Bantin final node CSCC 40 activity diagrams 1
activity diagram with activity partitions (swimlanes) order processing (partially automated) University of Toronto at Scarborough © Kersti Wain-Bantin CSCC 40 activity diagrams 2
activity diagram with joins and forks order processing (partially automated) University of Toronto at Scarborough © Kersti Wain-Bantin CSCC 40 activity diagrams 3
online order processing (automated) activity diagram with [ guard conditions ] and decision nodes University of Toronto at Scarborough © Kersti Wain-Bantin CSCC 40 activity diagrams 4
guard conditions need to be added book hotel room (partially automated) University of Toronto at Scarborough © Kersti Wain-Bantin CSCC 40 activity diagrams 5
activity diagrams for existing or proposed systems high level • model business activities (processes or tasks) low level • model a use case using object flows • describe the logic of an operation can be used • before objects/classes identified • again when system design is mature University of Toronto at Scarborough © Kersti Wain-Bantin CSCC 40 activity diagrams 6
action (operation in a class) get. First (Advert. Collection: : ) class that contains the operation University of Toronto at Scarborough © Kersti Wain-Bantin CSCC 40 activity diagrams 7
object flow state of object before activity state of object after activity can be broken down into sub-activities University of Toronto at Scarborough © Kersti Wain-Bantin CSCC 40 activity diagrams 8