The document discusses use case modeling and diagrams. It defines a use case as a sequence of actions a system performs that yields an observable result for an actor. Use case diagrams depict the interactions between actors and the services (use cases) provided by the system. They help identify the classes needed for the system and provide a starting point for requirements, analysis, design, testing, and documentation. The example models the use cases for a bank that offers savings, checking, fixed deposit accounts and ATM services.

1. Session 5 Object Model Development

7. Use Case Diagram-1 Actor System Boundary Actor Class <<Actor>> Actor Name

8. Use Case Diagram-2 USE CASE Name << >> Stereotypes Use Case

9. Use Case Diagram-3

10. Use Case Diagram

11. Relationship amongst Use cases-1 Extends

12. Relationship amongst Use cases-2 Extends

13. Relationship amongst Use cases-3 Use