Library System Development Project

This document provides an overview of the Library System Development Project, including project planning, requirement documentation for the Pay Fine scenario, use case diagram, textual description of use case, sequence diagram, class diagram, activity diagram, user interface, and test case.

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

12LIBRARY SYSTEM DEVELOPMENT PROJECT
Task 8: User interface

13LIBRARY SYSTEM DEVELOPMENT PROJECT

14LIBRARY SYSTEM DEVELOPMENT PROJECT
Task 9: Test case
Numbe
r
Test
name
Description Scenario Preconditio
n
Input Expected
output
1 User
credential
validatio
n
A borrower
must login
using correct
credentials in
order to use
the
functionalities
.
The user
want to
borrow
or place
hold on a
book
The
borrower is
the active
member and
does not
have
pending
fines for
previous
transactions
.
userID
and
Passwor
d
valid user id
and password
will lead the
user to get to
the
functionalitie
s to search,
borrow, or
place hold on
a book.
2 Search
of a book
A registered
member can
search a paper
or book from
the system.
The user
will find
the book
from
catalogu
e or they
can
search
the book
using
author or
Must be
logged in to
the system
using the
valid
credentials.
Author ,
subject
or name
of the
book.
For an
existing book
the system
will show
details and
availability of
the books
otherwise
some relevant
error

15LIBRARY SYSTEM DEVELOPMENT PROJECT
subject. message.