Comprehensive Library System Project: Analysis, Design, and Testing

This project presents a comprehensive analysis and design of a library system. It begins with a Gantt chart for project management and then defines functional requirements, such as the 'Pay Fine' use case. The project includes a detailed use case diagram illustrating interactions within the library system, followed by a specific use case for borrowing items, complete with actors, pre-conditions, triggers, basic events, alternative paths, and post-conditions. Sequence and class diagrams are provided to visually represent system processes and structure. An activity diagram depicts a student searching for and placing a hold on a book. Furthermore, the project presents user interface designs for library administration, loans, member interfaces, and borrowable items. Finally, the project concludes with test cases based on the activity diagram, covering user authorization, book availability checks, loan status checks, and hold request completion.

Title Page
1

Table of Contents
Task 1..........................................................................................................................................................3
Task 2..........................................................................................................................................................3
Task 3..........................................................................................................................................................3
Task 4..........................................................................................................................................................4
Task 5..........................................................................................................................................................5
Task 6..........................................................................................................................................................5
Task 7..........................................................................................................................................................6
Task 8..........................................................................................................................................................8
Task 9........................................................................................................................................................10
References.................................................................................................................................................13
2

Task 1
1. The Gantt chart for the whole assignment project is,
2.
Task 2
The given scenario is ‘Pay Fine’.
It is assumed that a borrower has borrowed one or more books from the library and have not returned yet.
The fines have been accumulated for the borrower and it is more than $25. So, the borrower’s account has
been suspended until the fine is being cleared.
The ‘Pay Fine’ is a functional requirement for the system. So, the requirement description is,
A borrower needs to pay fine if the borrower has not returned borrowed items past the expected return
date. If the system finds that the items borrowed by a borrower has not been returned yet, it must calculate
the fine accumulated for the borrowed items. If the accumulated sum is more than $25, the borrower
account will be suspended and the borrower will not be able to borrow new items until the fine is cleared.
The borrower must give the fine manually to a librarian. The librarian will revoke the ‘active’ status of
the borrower account by marking due fines and cleared.
Task 3
The use case diagram for the Library system is given below.
3

Task 4
Name Borrow Item
Version 1.0
Goal It allows a borrower to borrow an item from the library.
Summary The use case represents the borrowing function. The library has books, study
materials and other electronic items to borrow. A Borrower borrows a book or
other items from the library. The librarian approves the loan and provides a
due date for returning the item. The user may return the item to the library
within the due date or may have to pay fine if the due date is crossed.
Actors Borrower is the primary actor. Librarian is the secondary actor.
Pre-conditions Borrower must have an active borrower account with the library system.
Triggers Borrower wants to borrow an item from the library.
Basic course of Events 1. Borrower asks for the approval of the librarian for borrowing a new
item.
2. System checks if the borrower is eligible to borrow an item or not.
3. Librarian receives the request and checks whether the item is on
reserve or not. If the item is available and the borrower has an active
status then the librarian approves the request and gives a due date to
return the item.
4

4. Borrower returns the item within the due date. It is represented by the
‘Return Item’ use case.
If the borrower does not return an item within the given due date,
then the borrower needs to pay fine. It is represented by the extended
use case, ‘Pay Fine’.
Alternative Paths From step 3. If the item is found to be marked as reserved item and it is not
possible to allocate the item to the borrower, then the librarian cancels the
request.
Post-Conditions The borrower will have a borrowed item with a due date to return.
Business Rules The library system must allow a borrower to borrow an item from the library
with the help of a librarian.
Notes NA.
Task 5
The sequence diagram is,
Task 6
The class diagram of the library system is,
5

Task 7
The activity diagram shows a scenario where a student searches for a book and places a hold on the item.
6

7

Task 8
User interface designs are presented below.
 Library Admin Pages
8

 Library Loans’ Interface
 Library member’s Interface
9

 Library borrowable items interface
Task 9
Test cases based on the activity diagram from Task 7 are presented in the following table.
Number Test name Description Scenario Precondition Input Expected
output
10

1 User
Authorization
It will check
whether the
user
authorization
process
works
properly or
not.
A student
provides
wrong login
details
The student
must be able
to access the
library
system.
Wrong
Login
Details
Login Fails
and it will
ask for right
login details.
2 Checking
availability of
a book
It will check
whether a
book is
available to
borrow or
not.
A student
searches for
a book and
tries to
borrow it.
The student
must be
logged in.
Name of a
book.
Show the
availability
status. If it is
not available,
then it must
inform the
user about
the
unavailability
of the book.
Else it must
produce a
detailed
search result
with the
available
books with
the same
name.
3 Checking
whether a
book is on
loan or not.
It will check
whether a
book is on
loan or not.
A student
wants to
borrow a
book and
want to
check
whether it is
on loan to
another
member or
not.
The student
must be
logged in and
the book must
be available
in the library.
Query to
check
whether the
selected
book is on
loan or not.
If it is not on
loan, then it
will show the
student that
the book is
not on loan
and the
student can
borrow it.
Otherwise, it
must inform
the student
that the book
is on loan by
another
student and
the tentative
return date of
the book.
4 On-hold
request
successfully
completed or
not.
It will check
whether the
request to
keep a book
on hold by a
A student
wants to
keep a hold
on a book
that is
The student
must be
logged in and
the book must
be available
A request to
put a hold on
a book.
If there is no
other
pending hold
request on
the book,
11

student is
successful or
not.
available and
not on loan.
in the library
and must not
be on hold or
on loan by
another
member.
then it must
inform the
student that
he/she is
successfully
holding the
book until a
due date. If
there is
pending hold
request then
it will inform
the student
that the
request has
been queued.
12

References
Dennis, A., Wixom, B. H. & Roth, R. M., 2014. Systems Analysis and Design. s.l.:John Wiley & Sons.
13