Library System Development Project: Analysis and Design (Backend)

This document presents a comprehensive library system development project, focusing on backend functionality. The project encompasses detailed planning, including a project schedule with tasks like project initiation, requirements analysis, and design stages. The requirements documentation outlines the 'Pay Fine' scenario, detailing borrower accounts, fine calculations, and payment processes. Use case, sequence, class, and activity diagrams visually represent the system's interactions and structure. Test cases are designed to validate user credentials, search functionalities, and overall system behavior. The user interface is also designed to provide a clear and intuitive experience. The project adheres to the provided scope, ensuring all system functions and data are included, such as borrowing items, accessing both physical and electronic items, renewing loans, viewing a borrower’s account (including overdue items and fines), searching catalogues for various items, renewing loans, login, and asking a librarian. This project serves as a complete documentation of the library system's backend operations, design, and testing procedures.

Running head: LIBRARY SYSTEM DEVELOPMENT PROJECT
Library system Development project
Name of the Student
Name of the University
Authors note

1LIBRARY SYSTEM DEVELOPMENT PROJECT
Task 1: Project Panning for the development of the Information System
Schedule of the Project
Task Name Duration Start Finish Predecessors
Library
information
System Backend
Project
20 days Mon
07/01/19
Fri
01/02/19
Initiation
and Scope of
Project
2 days Mon
07/01/19
Tue
08/01/19
Determina
tion of project
scope
2 days Mon
07/01/19
Tue
08/01/19
Requireme
nts analysis
8 days Wed
09/01/19
Fri
18/01/19
Analysis of
the present system
functionalities
2 days Wed
09/01/19
Thu
10/01/19
3
Creating a
draft of functional
requirements
2 days Fri
11/01/19
Mon
14/01/19
5
Requireme
nt Elicitation
4 days Tue
15/01/19
Fri
18/01/19
6

2LIBRARY SYSTEM DEVELOPMENT PROJECT
Use case
Design stage
7 days Fri
11/01/19
Mon
21/01/19
Determini
ng the classes and
designing class
diagram
5 days Fri
11/01/19
Thu
17/01/19
5
Designing
Interface for the
application
2 days Fri
18/01/19
Mon
21/01/19
6,9
Use case
Textual
Description
2 days Tue
22/01/19
Wed
23/01/19
Developme
nt of description
for the Pay fine Use
Case
2 days Tue
22/01/19
Wed
23/01/19
10
Class
diagram design
stage
3 days Thu
24/01/19
Mon
28/01/19
determinin
g the classes
3 days Thu
24/01/19
Mon
28/01/19
12
Developme
nt of the Class
Diagram
Sequence
diagram design
2 days Tue
29/01/19
Wed
30/01/19

3LIBRARY SYSTEM DEVELOPMENT PROJECT
Stage
Determini
ng the sequence
2 days Tue
29/01/19
Wed
30/01/19
14
Designing
the Sequence
Diagram
Generatin
g Test case stage
2 days Thu
31/01/19
Fri
01/02/19
Generatio
n of test cases for
the system
2 days Thu
31/01/19
Fri
01/02/19
17
Gantt chart for the project
Trello Board Snapshots for the Project

4LIBRARY SYSTEM DEVELOPMENT PROJECT

5LIBRARY SYSTEM DEVELOPMENT PROJECT
Task 2: Requirement Documentation for Pay Fine Scenario
The student or borrower member of the library have to be an active member in the
library along with the details like name, membership type, enrolment ID, expiry date in the
library.
Administrative staffs as well as library staff will be able to view/ track the borrowers
and their status of borrowed books from the library system.
In case the borrower is not able to return the book to the library in the stipulated time
the system will consequently add fines to the borrower account in an automated manner to
the related borrower account.
After the fine is paid and received by the library staff only after that staff will make
the update in the system about the paid fine.
The staff will be able to produce a receipt using the information system
acknowledging receipt of the fine from the borrower.

6LIBRARY SYSTEM DEVELOPMENT PROJECT
Task 3: Use case Diagram for Pay Fine Scenario

7LIBRARY SYSTEM DEVELOPMENT PROJECT
Task 4: Textual Description of use case
Name Search and borrow a book using the information system.
Version U401
Goal Checking the availability of a book or publication and
borrow the book by requesting through the Information system.
Summary This use case will represent all the actors and actions of
those actors for achieving the goal of borrowing a book if it is
available it.
Actors Student/borrowers, library staff administrator of the
library system.
Pre-conditions The borrower already has active account in the
information system and the intended book is in stock.
Triggers Borrower /student requests through the system to borrow
the book after searching and confirming the availability of the
book.
Basic Course of
Events
The book is searched by the name of the author/subject/
year or publication by the student or borrower. After this the
borrower requests to the staff. The librarian checks the borrower
account information of the and after confirmation of no due scan

8LIBRARY SYSTEM DEVELOPMENT PROJECT
through the scanning of the barcodes of the books the book is
assigned.
Post-Conditions The book is issued for finite number of days and the
return date for the book is also entered in the system.
Business Rules The Student must have an account in the library
information system.
If any pending fine is remaining against the account, then
no book will be allowed to be borrowed.
The dates of return must be later than the borrow date so
that the track of the fine amount can be easily managed and
tracked.

9LIBRARY SYSTEM DEVELOPMENT PROJECT
Task 5: Sequence diagram

10LIBRARY SYSTEM DEVELOPMENT PROJECT
Task 6: Class diagram

11LIBRARY SYSTEM DEVELOPMENT PROJECT
Task 7: Activity diagram