Polytechnic University of the Philippines

Biñan Campus

Prudente, Russel Jhon A. Prof. Mark John Paul Capistrano

DCET 3-1 Software Design

ACTIVITY: THE PUP LIBRARY MANAGEMENT SYSTEM 2

PUP LIBRARY MANAGEMENT SYSTEM PROPOSAL-TIMELINE FOR 1 YEAR

Considering my own library management design from the last activity, if I was given a chance to redo/improve the system, I will consider the
following;

❖ SYSTEM
Given that this was a library system, I will build a software that fully handles the housekeeping functions of a library. Library will rely on
its system by means of assessing, as well as the relationships of each users. Library management systems help libraries keep track of the
books and their checkouts, as well as members’ subscriptions and profiles.
I will also consider a library management system that involve maintaining the database for entering new books and recording books
that have been borrowed with their respective due dates.
Given that the library contains books, each book will have a unique identification number and other details including a rack number
which will help to physically locate the book. Each book and member card will have a unique barcode. The system will be able to read
barcodes from books and members’ library cards.
 The system should be able to retrieve information like who took a particular book or what are the books checked-out by a specific
library member. It should also be able to collect fines for books returned after the due date. The system should be able to send notifications
whenever the reserved books become available, as well as when the book is not returned within the due date.

❖ USERS
All of the members can search the book by catalog, as well as check-out, reserve, renew, and return a book.
The Librarian, mainly responsible for adding and modifying books, book items, and users. The Librarian can also issue, reserve, and
return book items.
The Director should facilitate all the members and asses those user students who has a bad record in the campus by cooperating in the
librarian.

WORK BREAKDOWN STRUCTURE (WBS)

PUP Library
Management
System

(Phase 2) (Phase 3)
(Phase 1) Design (Phase 4) Testing
System Database

Member
Search By
Library Member Profile User Interface Book Availabilty Identification Relationship My SQL-Server Dry Run
Categories
Assesment

Check In/ Check Unique

Bookshelves Faculty Student Search Bar Notification Bar Reserve/ Return Due Date WAMP XAMP Debugging
Out Barcoode

Books IT Admin Director Librarian Visitor Log-in/Log-Out

Add/Remove/Edi
t
 TIMEFRAME/GANNT CHART

PUP LIBRARY MANAGEMENT SYSTEM TIMEFRAME

PHASE START END DURATION
Phase 1(Design) JANUARY-MARCH
1.1 User Interface
Search Bar 29-Jan-21 5-Feb-21 7
Notification Bar 6-Feb-21 15-Feb-21 9
Log-in/ Log-out 16-Feb-21 20-Feb-21 4
1.2 Library
Bookshelves/Rack 21-Feb-21 28-Feb-21 7
Books 1-Mar-21 13-Mar-21 12 TASK START END DURATION
Add/Remove Edit 14-Mar-21 20-Mar-21 6 1.1 29-Jan-21 20-Feb-21 22
1.3Member Profile
Faculty 21-Mar-21 21-Mar-21 0
1.2 21-Feb-21 20-Mar-21 27
IT Admin 22-Mar-21 24-Mar-21 2 1.3 21-Mar-21 31-Mar-21 10
Director 25-Mar-21 26-Mar-21 1
Librarian 27-Mar-21 29-Mar-21 2
2.1 1-Apr-21 22-Apr-21 21
Student/Visitor 30-Mar-21 31-Mar-21 1 2.2 23-Apr-21 26-May-21 33
Phase 2(System) APRIL-JULY
2.3 27-May-21 17-Jun-21 21
2.1 Book Search By Categories 1-Apr-21 22-Apr-21 21
2.2 Availability 2.4 18-Jun-21 30-Jul-21 42
Check In/Check Out 23-Apr-21 30-Apr-21 7 3.1 1-Aug-21 31-Oct-21 91
Return/Reserve 1-May-21 18-May-21 17
Due Date 19-May-21 26-May-21 7 4.1 1-Nov-21 31-Dec-21 60
2.3 Identification
Unique Barcode(Books and Members) 27-May-21 17-Jun-21 21
2.4 Member Relationship Assesment
Faculty System 18-Jun-21 30-Jun-21 12
Records of Both Students/Visitors 1-Jul-21 15-Jul-21 14
Assesmennt of Bad Record of Students 16-Jul-21 30-Jul-21 14
Phase 3(Database) AUGUST-OCTOBER
3.1 My SQL Server(WAMP/XAMP) 1-Aug-21 31-Oct-21 91
Phase 4(Testing) NOVEMBER-DECEMBER
4.1 Run System/Debugging 1-Nov-21 31-Dec-21 60
 GANNT CHART
29-Jan-21 20-Mar-21 9-May-21 28-Jun-21 17-Aug-21 6-Oct-21 25-Nov-21 14-Jan-22

1.1
1.2
1.3
2.1
TASK

2.2
2.3
2.4
3.1
4.1

4.1 3.1 2.4 2.3 2.2 2.1 1.3 1.2 1.1

START 1-Nov-21 1-Aug-21 18-Jun-21 27-May-21 23-Apr-21 1-Apr-21 21-Mar-21 21-Feb-21 29-Jan-21
DURATION 60 91 42 21 33 21 10 27 22

To execute the timeline thoroughly, I create a Work Breakout Structure to define the model of the system one by one, from the designing (Phase 1),
making the system (Phase 2), creating a database for the system (Phase 3), and lastly, testing out the system by running and debugging (Phase 4).

Then I create a timeframe for each model. Given that the timeline is a year, I define each phase of the task’s critical path, from ease to hard. Based from
the frame and graphs. I assume that I can start with the uncritical one, designing the system therefore, I give it a minimal time however, an assurance
to reach its full features.

Next, making a system which I give this a further time given that this part is a little bit complicated and it need a little patience and time and courage
to make it fully responsive. And then, making a database which is complicated also.

And lastly, assuming that the software has already finished, we will test the whole system if this is responsive or not, and maybe, there are some errors
in the system so it may take for a while for the debugging until it reach its final glory.