1. 1

2.  Modeling the context of a system  Modeling the requirements of a system 2

3.  Use case diagrams are central to modeling the behaviour of a system, a subsystem, or a class.  Important for visualizing, specifying, and documenting the behavior of an element. 3

4.  A box with small buttons  Being a developer, on should conceptually understand the system  With UML, apply use case diagrams to visualize the behavior of a system, subsystem, or class 4

5.  A box with small buttons – Cellular Phone 5 Place Phone Call > Receive Phone Call Use Scheduler Place Conference Phone Call Place Conference Phone Call Receive Additional Call Receive Additional Call > Cellular Network User Cellular Telephone

6.  What is use case diagram ? ? ? ?  A name and graphical contents that are a projection into a model.  Its content distinguishes from other kind of diagrams 6 Use Case Diagrams Use Cases = Actors +

7.  What does Use case diagram contain ? ? ? ?  Use cases  Actors  Dependency, generalization, and association relationships  Packages and instances of use cases 7

8.  Common uses  To model the context of a system  drawing a line around the whole system and asserting  which actors lie outside the system and interact with it  To model the requirements of a system  what that system should do  specify the desired behavior of the system 8

9.  Things will live inside the system, some things will live outside it.  credit card validation system  accounts, transactions, and fraud detection agents  credit card customers and retail institutions 9

10.  Identify the actors that surround the system  Organize actors – generalization/specialization  provide a stereotype to actor if needed  Provide communication path for actors and use case 10

11. 11 Customer Perform card transaction Process customer bill Reconcile transaction Manage customer account Individual Customer Corporate Customer Retail Institution Sponsoring financial institute Credit Card Validation System

12.  Establish the context of the system by identifying the actors that surround it.  For each actor, consider the behavior that each expects or requires the system to provide.  Name these common behaviors as use cases.  Factor common behavior into new use cases that are used by others; factor variant behavior into new use cases that extend more main line flows.  Model these use cases, actors, and their relationships in a use case diagram.  Adorn these use cases with notes or constraints that assert nonfunctional requirements; you may have to attach some of these to the whole system. 12

13. 13 Customer Perform card transaction Process Customer Bill Reconcile transactions Manage customer account Report on account status Detect card frauds Manage network outage Retail Institution Sponsoring financial institution

14. 14 Place Order Place Phone Call Restock Deliver Order Prepare order Server Order Take Order Customer Cook Delivery Boy > Stock Low > Waiter Restaurant

15.  Propose a use case diagram for an ATM machine for withdrawing cash. Make the use case simple yet informative; only include the major features.  Identify use cases and actors and their relationship. Your diagram should include  Customer operation over ATM machine.  Role of administrator in registration of ATM to bank maintaining records. 15

16. 16 Withdraw Transfer Funds Deposit Money Register ATM at bank Customer Read Log Admin Bank ATM System

17. 17