Library Management System Project: Data Science Application

This project report details the development of a library management system. It begins with a Gantt chart outlining the project's timeline, followed by a description of the system's requirements, which includes tracking book circulation and managing student memberships. The project then employs various diagrams, such as use case diagrams, sequence diagrams, class diagrams, and activity diagrams, to visually represent the system's functionalities and workflows. The use case textual description elaborates on the actors and their interactions within the system. Additionally, the report includes user interface designs for login, logout, book issue, and registration pages. Finally, the project concludes with a test case generation section, defining scenarios and expected outcomes to ensure the system's reliability and efficiency. This project provides a comprehensive overview of the design, development, and testing of a library management system.

Library Management
system

TASK 1
Gantt chart
Task Name Duration Start Finish
Designing of project 3 days Tue
10/9/18
Thu
10/11/18
Determining IT requirements 5 days Fri
10/12/18
Thu
10/18/18
Develop Fri
10/19/18
Fri
10/19/18
installing software and
applications 8 days Mon
10/22/18
Wed
10/31/18
Conducting meeting 3 days Thu
11/1/18
Mon
11/5/18
Evaluate 6 days Tue
11/6/18
Tue
11/13/18
Monitoring and control of
system
Tue
10/9/18
Tue
10/9/18
Collecting data 5 days Wed
11/14/18
Tue
11/20/18
maintaining systems 4 days Wed
11/21/18
Mon
11/26/18
Closure 2 days Tue
11/27/18
Wed
11/28/18
1

2

Trello
TASK 2
Requirements documentation
The purpose of Library management System is to keep records of those students who
have either borrowed or issued a book. Library management tracks the records of inflow and
outflow of books or other readable novels. This system will save the data base of the students,
who have taken a book from library and date of resubmission is also mentioned. If students are
not able to submit the book on a due date then fine will be charged to that person for not
submitting the books of library on time. If the books are not submitted timely then students are
liable to pay penalty charges for late submission. If books are not submitted on a specific date
then students will have to compensate the amount of $10 per day after due date. Then librarian
will calculate the total penalty charged to a member.
The requirement will be accessed based on the following points, such as:
 it will trace the activities as type of books available in which quantity.
3

 This also maintains the dates of reissue or resubmission of books so it will systematically
provide a list of students who have to pay fine with late submission and it will also
provide a proper amount to be charged to particular person.
 It is required to calculate total pending amount of the students.
 In case of any penalty charged, amount is required to be submitted with total bill.
Student have to pay this amount at the time of reissuing or giving back the books to
librarian.
TASK 3
Use Case Diagram
TASK 4
Use Case Textual description
Use case elements Description
Name Library management system will provide membership of
4

students to issue book so use case diagram is named as
librarian.
Version Version of use cases may differ by its personnel
identification of problems and action which are taken
accordingly.
Goal Use case are mainly used to link the personnel with
different cases. Since it does not contain any design so it
describes the relation of users with multiple cases.
Summary This use case mainly consists of two entities namely
members and librarian. Here student will request for book
and librarian will check the availability by following if else
condition. if book is available then librarian issue that
requested book to member or else it will be displayed that
book is not available. Then if the student become the
member of the library then bill will be calculated and stus
will be updated that how many books are issued to a
student. Book status contains the description about the
book.
Actors Two primary actors which are commonly used in this use
case are librarian and members who issue books from
library management.
Pre-condition A predicted condition is as follows: library management
system contains the details of books available, issued and
date of resubmission. So member requests for a particular
book and the condition will be: Either member have
already reached a maximum limit to issue book.
Triggers The event is: Student enters in library and requests for a
particular book and proceed the transaction.
Basic course of events There are 9 steps involved to achieve the goal of library
5

management system.
Another paths which takes activities to final node are as
follows:
Book is not available.
Not validated member.
Alternative paths Maximum quota (students are not allowed to issue more
books)
Post-conditions Multiple post conditions are as follows: update status of
book and increase the number of books issued to students.
Business rules Business rule in library management system is students
who have not taken membership of library yet then they are
not allowed to issue books.
TASK 5
6

Sequence Diagram
TASK 6
Class Diagram
7

8

TASK 7
Activity diagram
TASK 8
User interface design
1. Login page and logout page
9

2. Book issue details
2. library loan details
10