The document, authored by Dr. Bharat V. Chawda, provides an overview of use case diagrams in the context of software engineering, specifically for a book store management system. It discusses the significance of use case diagrams, their notations, and how they represent user interactions without revealing internal structures, helping to identify requirements and system functionality. The document also outlines various components of use case models and emphasizes their role in documentation and requirement specification.

1. Use Case Diagram
by:
Dr. Bharat V. Chawda
Computer Engineering Department,
BBIT, VVNagar, Gujarat, India
1

2. Overview
 Introduction
 Notations
 Example
 Use Case Model
 Why Use Case Diagram?
(As per GTU Curriculum – Diploma in Computer/IT Engineering)
Based on Book:
1. Fundamentals of Software Engineering – by Rajib Mall
2

3. Use case diagram: Example
3
Manage Books
Manage Customers
Manage Suppliers
Manage Employees
Manage Purchase
Manage Sales
Search Books
Book store Management System
Admin
Customer
Login

4. Concept
 Use Case
 Represents the way in which a system can be
used by users.
 Corresponds to high level functional req.
 Do not reveal internal structure of the system.
 Shows interactions between user & system.
4

5. Use case diagram: Notations
5
Stick Person Actor
Ellipse
Rectangle
Line
Use Case
System Boundary
Communication Relationship

6. Use case diagram: Example (i)
6
Manage Books
Manage Customers
Manage Suppliers
Manage Employees
Manage Purchase
Manage Sales
Search Books
Book store Management System
Admin
Customer
Login

7. Use case diagram: Example (ii)
7
Manage Books
Manage Customers
Manage Suppliers
Manage Employees
Manage Purchase
Manage Sales
Search Books
Book store Management System
Admin
Login
Sales
Manager
Purchase
Manager
Customer

8. Use Case Model
 Use case diagram + Text description
 Contact Persons
 Actors
 Pre-condition
 Post-condition
 Non-functional Requirements
 Exceptions, Error situations
 Sample Dialogs
 Specific User Interface Requirements
 Document References
8

9. Why Use case diagram?
 Helps to identify/analyze requirements
 Helps to identify actors
 Serves as a type of requirements
specification
 Useful in understanding exact functioning
of the system
 Specifies actor-functionality relationship :
Helps to implement security mechanism
 Useful in preparing docs: Users’ manual
9

10. Thank-U…!!!
10