WORKSHEET-3

Student Name: Ayushi Sharma

UID:20CBS1079
Branch: Bachelors of Engineering in Computer Science with Business Systems
Section/Group: 20CBS1/ B
Semester: 4th Semester
Subject Name: Software Design with UML
Subject Code: 22E-20CSP-290
Date of Performance:22nd February,2022

1. AIM/OVERVIEW OF THE PRACTICAL:

Make use case diagram for your project.

2. TASK TO BE DONE:
Make the use case diagram of Library Management system.

3. WHAT ARE USE CASE DIAGRAMS AND ITS COMPONENTS:

In UML, a use case diagram summarizes the details of your system’s users (also known as actors)
and their interactions with the system. Use case diagrams are ideal for:

 Representing the goal of system user interactions

 Defining and organizing functional requirements in a system
 Specifying the context and requirements of the system
 Modelling the basic flows of events in a use case

Components of use case diagram:

  ACTOR: An actor is someone or something that must interact with the system under
development UML notation for actor is stickman.

 USE CASE: A use case is a pattern of behavior, the system exhibits. Each use case is a
sequence of related transactions performed by an actor and the system in dialogue. USE
CASE is dialogue between an actor and the system. Use cases are represented as:

 SYSTEM BOUNDARY: It is shown as a rectangle. It helps to identify what is an external

verse internal, and what the responsibilities of the system are. The external environment is
represented only by actors. System boundary is represented by a rectangle.
 RELATIONSHIP:
Relationship between use case and actor: Communicates
Relationship between two use cases: Extends, Uses
Notation used to show the relationships: << >>

 PACKAGES: A UML shape that allows you to put different elements into groups. Just as with
component diagrams, these groupings are represented as file folders .

3. USE CASE DIAGRAM FOR LIBRARY MANAGEMENT SYSTEM:

The Actors involved in the system are:

1. Librarian
2. Member

The corresponding use cases for these actors are:

1. Librarian: Inquiry for membership, request book, return, search book , pay fine
2. Member : Cancel membership, issue membership card, issue book, return book, update
details, maintain book records:- add , remove , update book.
4.LEARNING OUTCOMES:

 Learnt about UML diagrams

 Learnt to make Use Case Diagram
 Learnt to implement use case diagram for a software .