Use Case Document

Online library management system

CSCI 4497 & CSCI 6628

Date
9/7/2016

Author(s)
Name
Roja

Sections completed

Table of Contents

1.0
2.1
2.2
2.3
2.4
2.5
2.6
2.7

Introduction
Use case Registration
Use Case Search
Use Case Transactions
Use Case Add/Remove book
Use Case Report
Use Case Login
Use Case View/edit

REVISION HISTORY
Date
Name

3
3-4
4-5
5-6
6-7
7-8
8-9
9-10

Changes

USE CASES
1.0 Introduction: The purpose of the system is to allow for storing details of a
large number of books and allow for add, search, borrow, return facilities
separately to administrator, staff and students. Different privileges are
given to different types of users. Using the OOSE (Object Oriented
Software Engineering) we try to express the requirements as use cases
consisting of actors and how they interact with the system. We define the
objects and use cases as system objects. We define the functions and
attributes within these system objects
This document will outline the Use Cases for the Online library management
System Application, utilizing the following structure format.
Use Case Name
Description
Actor
Pre-Conditions
Main Flow
Alternate Flows
Exception Flows
Post Conditions
Actors: 1. Administrator (Category User)
2. Staff (Category User)
3. Students (Category User)
4. Library Account (Category System)
5. Book (Category System)
6. Transaction (Category System)
7. Report (Category System)
8. Search (Category System)
9. Registration (Category System) .

2.1
Use Case: Registration.
2.1.1 Description: This use case describes how to register a user.
Actors: Administrator, Staff
2.1.2 Pre-Conditions: The student should have a valid college membership
document which contains his name, date_of_birth, course, Rollno to obtain
library membership. The same criteria apply for registration of library and other
staff members including the administrator
2.1.3 Main Flow:
The use case begins when the administrator selects the Register button from the
main screen.
1. To register a student the administrator or staff has to first login.
2. After login the administrator or staff searches for the existing students.
3.If the student is already registered there is no need to register him.
3

4. If the student is not already registered then his name, roll_no is to be

entered for registration.
5. A student_id for library membership is generated and provided to the
Student.
6. To register a staff member the administrator has to first login.
7. After successful login he searches among the existing staff members.
8. If the staff member is already registered there is no need to register
him. 9. If the staff member is not already registered then his name,
designation is Entered.
10. After successful registration the staff member is provided with a unique
id
2.1.4 Alternate Flows: There are multiple alternate flows depending on user
selection from the main flow that will follow the same path as the main
flow.
1. The administrator or staff fails to login.
2. Administrator or staff can search for his id among existing members.
3. if he is already a member and unable to login he should contact the
administrator otherwise he should get re-registered.
2.1.5 Exception Flows: System to generate error message and prompt if any
of the users input paths are incorrect, incorrect user ID or insufficient
administrative privileges
2.1.6 Post Conditions: All required Setup data has been input. User logged off
and system goes back at login prompt

2.2
Use Case: Search
2.2.1 Description: this use case will help us to search the required books.
Actors: Administrator, Staff, Students.
2.2.2 Pre-Conditions: The book or student to be searched should have been
registered in the database of the library management system.
2.2.3 Main Flow:
1. The student or staff or administrator logins to the system.
4

2. If the login is successful. student or staff or administrator enters the

book name or ISBN or author name and presses search
3. If the search is successful then that book is displayed on the screen.
4. To search for a student the administrator or staff logins to the system. 5.
If the login is successful then it is possible to search for any student by
entering his id.
6. To search for a staff member the administrator enters his login id.
7. If successful he can search for any of the staff members
2.2.4 Alternate Flows:
1. The login fails.
2. The student or staff or administrator can re-register themselves
3. If the search is unsuccessful then the administrator should add that
members.
4. If the book search is unsuccessful then that book should be added.
2.2.5 Exception Flows: System to generate error message if the member/book
does not exist.
2.2.6 Post Conditions: All required Setup data has been input.

2.3
Use Case: Transaction
2.3.1 Description: Returning/borrowing of a book.
Actors: Administrator, Staff
2.3.2 Pre-Conditions: To return or borrow any book it is important that the
student or staff member is registered with the library and the book to be
borrowed is available with the library. To return the book the pre-condition is that
the student and the staff member is registered and that book data is available
with the library.
5

2.3.3 Main Flow:

1. If a student wants to borrow or return a book the staff or administrator
should login to the system.
2. If login is successful the staff or administrator should enter the student
id to be searched.
3. If student search is successful the staff or administrator should enter the
book id.
4. If the book is available it can be borrowed.
5. If the book is available the staff and administrator should check The
report data for any pending fine.
6. If no fine is pending the book can be returned
2.3.4 Alternate Flows:
1. If the login fails the staff or administrator should re-register Themselves.
2. If the student search is unsuccessful and no data is found then the
administrator should re-register the student.
3. If the book search is unsuccessful and book data is not found then
administrator must enter the book in requisition report.
.
2.3.5 Exception Flows: Errors generated if the book is not available.
2.3.6 Post Conditions: All required Setup data has been input about the
books available and not available.

2.4
Use Case: Book (Add/Remove)
2.4.1 Description: Adding/removing of a book.
Actors: Administrator.
2.4.2 Pre-Conditions: To add any book that book should be part of the
requisition list and to delete the book the book must be part of the library
6

2.4.3 Main Flow:

1. The staff or administrator login to the system.
2. If login is successful then to add a book the staff or administrator must
search for the book.
3. If the book is not found then it is checked in the requisition list.
4. If the book is not currently available and is part of the requisition list it
can be added to the book database.
5. To remove a book it is again searched in the library system.
6. If it is found it should be checked in borrower_list.
7. If it is not in the borrowed list it can be removed.
2.4.4 Alternate Flows:
1. If the login is unsuccessful then staff should re-register themselves.
2. If a book is to be added and on search it is already found it should not
added again.
3. If book is to be removed and on search it is not found and is also not
part of borrowers_list then there is any need to remove it.
.
2.4.5 Exception Flows: Errors generated if the book is not available.
2.4.6 Post Conditions: All required Setup data has been input about the books
available and not available

2.5
Use Case: Report
2.5.1 Description: Generating reports for a book or student.
Actors: Administrator, staff.

2.5.2 Pre-Conditions: To generate any report the staff or administrator should

be registered with the library and to generate report on any book or student they
should be part of the library system.
2.5.3 Main Flow:
1. The staff or administrator logins to the system
2. To generate report on defaulters the staff or administrator should first
search for that student.
3. If the student is found then he can be checked in the defaulters list.
4. To generate report on borrowed books the staff or administrator must
search for that book.
5. If found that book can be checked in the borrowed books list.
6. To generate report on requisition list of book the he staff or administrator
should first search for that book.
7. If book is not found then it should be checked in the requisition list.
2.5.4 Alternate Flows:
1. If the login is not successful then staff or administrator should go to the
registration page.
2. If student is not found after search he should be re-registered.
3. If book is not found then that book should be added again before
checking it in the borrowers list.
2.5.5 Exception Flows: Errors generated if the books/student is not available.
2.5.6 Post Conditions: All required Setup data has been input about the books
available and not available.

2.6
Use Case: Login
2.6.1 Description: Generating reports for a book or student.
Actors: Administrator, Staff, Student.
8

2.6.2 Pre-Conditions: If the student or staff or administrator wants to login then

he should have been first registered.
2.6.3 Main Flow:
1. To login the student or staff or administrator should first open the Login
page.
2. They should then enter their ids and passwords.
3. Once the id and password are verified they are moved to the options
page where they can search, view and perform other operations.
2.6.4 Alternate Flows:
1. The login fails after entering login and password.
2. It is the responsibility of the administrator to see that all staff and
students are properly registered and can login to the system
2.6.5 Exception Flows: Errors generated if the books/student is not available.
2.6.6 Post Conditions: All required Setup data has been input about the books
available and not available.

.
2.7
Use Case: View/Edit
2.7.1 Description: Viewing or editing book details.
Actors: Administrator, Staff.
2.7.2 Pre-Conditions: To view the details of any book or edit book details that
book should be part of the library database. To view or edit student or staff details
that student or staff should be part of the library database. Whoever is viewing or
editing should be registered with the library.
2.7.3 Main Flow:
1. To view details or edit details of any book the administrator or staff
should first login to the library system.

2. If login successfully they must search for that book by putting book id or
title or isbn.
3. If the book is found they should enter book id to view the details and
also edit it.
4. To view details or edit details of any student or staff the administrator or
staff should first login to the library system.
5. If login successfully they must search for that student or staff by putting
student id or staff id.
6. If the student or staff is found they should enter student id or staff id to
view the details and also edit it..
2.7.4 Alternate Flows:
1. If login fails the administrator should re-register that staff
2. If book search is unsuccessful then that book cannot be viewed or
edited.
3. If staff search is unsuccessful then that staff member cannot be viewed
or edited.
2.7.5 Exception Flows: Errors generated if the books/student is not available.
2.7.6 Post Conditions: All required Setup data has been input about the books
available and not available.

10