ITS332 SOFTWARE DESIGN

DESCRIPTION

Library Management System

GROUP MEMBERS:
1) Siti Sabariah binti Draman @ Hashim [2017872896]
2) Siti Aisyah Humairah Binti Che Mohd Yusri [2017241576]
3) Nur Aina Amirah Binti Mohd Yusof [2017693718]
4) Norhidayah Mohd Jaafar [2017294832]

5 MAY 2019
Table of Contents
1. Introduction 3
1.1 Document Purpose 3
1.2 Product Scope 3
1.3 References 3
2. System Overview 4
2.1 Context Diagram 4
2.2 Diagram 0 6
2.3 Functional Decomposition Diagram 8
2.4 Operating Environment 9
3. Data Dictionary 10
3.1 Documenting the Processes 10
3.2 Documenting the Entities 12
3.3 Documenting the Data Flows 13
1. Introduction
1.1 Document Purpose

Perpustakaan Cendekiawan in UiTM Kuala Terengganu has an inefficient system in keeping

data of borrowing and returning book by user. Other than that, the staff or the librarian has a
complicated task to search data of the book. This problem occurs because the current system does not
provide a system that can keep the data sequence. Hence, by letting this problem occurs, it will be
wasting their time in searching the data or status of the book. The current system required many staff
to manage it by doing the same task. For example, need a staff to handle accountability and also need
a staff to calculate the total fine manually. Therefore, our group decided to handle this problem by
implementing new system to take over the current system.

This system is developed to keep and store information of user, books, transaction and staff
in more efficient and effective way. Besides, this system can cut time taken for the librarian to access
specific data from one week to 10 minutes. By developing this system, the specific required will
automatically generate by the librarian in about 5 minutes only.

1.2 Product Scope

In this system, students and librarian are the users. They have their different specific task but
at some tasks, they have same process such as they have to login into the system. In different specific
task behalf on librarian, they have to search member, search and manage book and calculate fine of
the user. Then, behalf on students, they have to reserve and return the book, search book and pay the
fine of the book if they late submission.

1.3 References

● ITS332 Group Proposal Library Management

● ITS232 Group Proposal
● ITS232 Final Report
● System Analysis and Design Textbook 11th Edition by Scott Tilley and Harry Rosenblatt
● System Analysis and Design Supplement 11th Edition by Scott Tilley and Harry Rosenblatt
2. System Overview
2.1 Context Diagram

Figure 1: Context Diagram of LibraryManagementSystem

From the context diagram, LibraryManagementSystem involves two external entities, which
are MEMBER and LIBRARIAN. Both of them will input their ID and password and the system will
display to the user if the login is accepted or not.

For MEMBER entity, they can request to view their status and profile, and the system will
display the MEMBER’s profile and status to the MEMBER. MEMBER also can request to update
their profile, by input the phone number or email address, and the system will update the profile.
MEMBER also can request to search certain book by input data related to the book, and the system
will display all of related book to the MEMBER.
 Besides, MEMBER can request to reserve any book listed by the system, and the system
will send the confirmation of the reservation to them. If the MEMBER doing the checkout process,
the scanner of the book will input the checkout information such as book information, member ID,
and the date of the checkout to the system. The same process when the MEMBER want to return the
book. The system will generate fine detail right after the MEMBER return the book based in given
condition.

Meanwhile the LIBRARIAN can request the system to generate report by input the specific
data such as name of book and also can link with another data. The system will generate report
based on the data input, the linking and the condition given by the LIBRARIAN. The report can be
on archive list, member, transaction, or book list, depending on the data storage available.
2.2 Diagram 0

Figure 2: Diagram 0 of LibraryManagementSystem

1. Verify login: The user (students or staff) will input their ID and the password to the system
and the system will refer to data store named MEMBER which stores all information of
members including their ID and password. the system will compare the data inputted by the
user with the data available inside the storage. If the ID and the password match, the login
accepted and the user may continue to use the service.
2. View profile/status: The member request to check their status or profile to the system, and
the system will refer to the data storage MEMBER to display the member’s information.
3. Update profile: The member request to update profile and will input the the data they need
to change such as telephone number or email address to the system. the system will update
member’s information to the data storage MEMBER.
4. Search book: The member request to search book and will input the data of the book to the
system, the system will refer to data storage BOOK to display any related book to the
member.
5. Reserve book: After choosing certain book, the member will request to reserve the book to
the system and the system will get the book information from data storage BOOK and
member’s information from MEMBER data storage then will input both of the information
into data storage RESERVATION.
6. Check reservation status: This process will get the reservation details from storage
RESERVATION and will display the confirmation of reservation to the member.
7. Checkout and Return:
a. If the member borrows/checkout the book, the scanner will input the book
information to the system and the system will generate transaction detail and send
the borrow transaction info to the data storage TRANSACTION. The system will
display the checkout statement to the user.
b. If the member returns the book, the scanner will input the book information to the
system and the system will generate transaction detail and send the borrow
transaction info to the data storage TRANSACTION. The system will display the
return statement to the user.
8. Archive checkout list and member list: This process will get the transaction data from
data store TRANSACTION and the member info from data store MEMBER and send it the
the data storage ARCHIVE.
9. Calculate Fine: If the return transaction exceeds the due, the system will calculate the fine
by getting the transaction info from the data storage TRANSACTION and will send the fine
detail to the member.
10. Generate report: The librarian may request to generate reports on members, transactions,
books and archive to the system. To do this, this process will get the data from the data
storages MEMBER, TRANSACTION, BOOKS, and ARCHIVE, then this process will
generate the report based on the condition and the data input by the staff. report generated
will be send/display to the staff.
2.3 Functional Decomposition Diagram

Figure 3: Functional Decomposition Diagram

2.4 Operating Environment

For operating environment software, this system requires operating system which is windows
10 as it is the latest one from the Windows Company. For resolution, we will use 1920x1080. This
resolution is the basic for computer. While, in operating environment hardware, we will use Intel(R)
Celeron(R) CPU N3060 @ 1.60 GHz and contains 4GB RAM and we also need secondary memory
as our backup. For implementing this project, other software applications that we need is Adobe
Dreamweaver, HeidiSQL and its server which is either WAMPP or XAMPP.
3. Data Dictionary
3.1 Documenting the Processes

Process Number : 1
Process Name / Label : Verify Login
Process Description : To verify the ID and password given by member
and librarian

Process Number : 2
Process Name / Label : View profile and status
Process Description : To view profile and status to member

Process Number : 3
Process Name / Label : Update profile
Process Description : To update member profile and status

Process Number : 4
Process Name / Label : Search book
Process Description : To search book via online

Process Number : 5
Process Name / Label : Reserve book
Process Description : To reserve book that booked by member

Process Number : 6
Process Name / Label : Check reservation book
Process Description : To check reservation book by member

Process Number : 7
Process Name / Label : Checkout and Return
Process Description : To checkout and return book by member
Process Number : 8
Process Name / Label : Archive checkout list and member list
Process Description : To archive checkout list and member list from data
store MEMBER.

Process Number : 9
Process Name / Label : Calculate fine
Process Description : To calculate fine for each member

Process Number : 10
Process Name / Label : Generate report
Process Description : To generate report for librarian
3.2 Documenting the Entities

Entity Name : Member

Alternate Name :
Description : User which is including students and lecturer
Input Data Flows : ● ID and password
● Request to check status/profile
● Request to update
● Request to search book
● Request to reserve book
● Borrowing/Checkout information
● Return Information
Output Data Flows : ● Login accepted or rejected
● Profile status and details
● Updated profile details
● Searched book details
● Confirmation of reservation
● Fine details

Entity Name : Librarian

Alternate Name : Staff
Description : User which is staff in library
Input Data Flows : ● ID and password
● Login accepted or rejected
● Request to generate report
Output Data Flows : ● Generated report
3.3 Documenting the Data Flows

Data Flow Name / Label : ID and Password

Alternate Name : None
Description : An input from member to verify login
Origin : Member
Destination : Verify Login
Volume and Frequency : 100 per week

Data Flow Name / Label : Login accepted or rejected

Alternate Name : None
Description : An output to notify user either their ID and password
are rejected or accepted
Origin : Verify Login
Destination : Member
Volume and Frequency : 100 per week

Data Flow Name / Label : ID and password

Alternate Name : None
Description : An input from librarian to verify login
Origin : Librarian
Destination : Verify Login
Volume and Frequency : 100 per week

Data Flow Name / Label : Login accepted or rejected

Alternate Name : None
Description : Librarian accepted or rejected the password
Origin : Librarian
Destination : Verify Login
Volume and Frequency : 100 per week

Data Flow Name / Label : Member’s ID and Password

Alternate Name : None
Description : Member gives their ID and password
Origin : Member
Destination : Verify Login
Volume and Frequency : 100 per week
Data Flow Name / Label : Request to check status / profile
Alternate Name : None
Description : Member can request to check status or profile
Origin : Member
Destination : View profile / status
Volume and Frequency : 50 per week

Data Flow Name / Label : Profile status and details

Alternate Name : None
Description : View profile or status to member
Origin : View profile / status
Destination : Member
Volume and Frequency : 50 per week

Data Flow Name / Label : Member’s information and status

Alternate Name : None
Description : Member give information and status to view profile
or status
Origin : Member
Destination : View profile / status
Volume and Frequency : 50 per week

Data Flow Name / Label : Request to update profile

Alternate Name : None
Description : Member can request to update his/her profile
Origin : Member
Destination : Update profile
Volume and Frequency : 15 per week
Data Flow Name / Label : Updated profile details
Alternate Name : None
Description : Update profile will be updated and notify the
member
Origin : Update profile
Destination : Member
Volume and Frequency : 15 per week

Data Flow Name / Label : Request to search book

Alternate Name : None
Description : Member can request to search book in the process
Search Book
Origin : Member
Destination : Search Book
Volume and Frequency : 100 per week

Data Flow Name / Label : Searched book details

Alternate Name : None
Description : Search Book searched book details in Member
Origin : Search Book
Destination : Member
Volume and Frequency : 100 per week

Data Flow Name / Label : Book info

Alternate Name : None
Description : Search Book will search the book info in data store
Book
Origin : Search Book
Destination : Book
Volume and Frequency : 100 per week
Data Flow Name / Label : Searched book details
Alternate Name : None
Description : Search Book will search the book details in data
store Book
Origin : Search Book
Destination : Book
Volume and Frequency : 100 per week

Data Flow Name / Label : Request to Reserve book

Alternate Name :
Description : Member can request to reserve book
Origin : Member
Destination : Reserve book
Volume and Frequency : 35 per week

Data Flow Name / Label : Confirmation of Reservation

Alternate Name : None
Description : Reserve book gives confirmation of reservation to
member
Origin : Reserve book
Destination : Member
Volume and Frequency : 35 per week

Data Flow Name / Label : Reserved Book detail

Alternate Name : None
Description : Book reserved book detail in reserve book
Origin : Book
Destination : Reserve book
Volume and Frequency : 35 per week

Data Flow Name / Label : Borrowing / Checkout information

Alternate Name : None
Description : Member can check borrowing information in
checkout and return
Origin : Member
Destination : Checkout and Return
Volume and Frequency : 50 per week
Data Flow Name / Label : Return information
Alternate Name : None
Description : Member can check return information in checkout
and return
Origin : Member
Destination : Checkout and Return
Volume and Frequency : 35 per week

Data Flow Name / Label : Return transaction info

Alternate Name : None
Description : Transaction get return transaction info by checkout
and Return
Origin : Checkout and Return
Destination : Transaction
Volume and Frequency : 80 per week

Data Flow Name / Label : Borrow transaction info

Alternate Name : None
Description : Checkout and Return gives borrow transaction info
to transaction
Origin : Checkout and Return
Destination : Transaction
Volume and Frequency : 50 per week

Data Flow Name / Label : Checkout list

Alternate Name : None
Description : Transaction gives input checkout list to archive
checkout list and member
Origin : Transaction
Destination : Archive checkout list and member list
Volume and Frequency : 50 per week
Data Flow Name / Label : Member list
Alternate Name : None
Description : Member gives input member list to archive checkout
and member list
Origin : Member
Destination : Archive checkout list and member list
Volume and Frequency : 100 per week

Data Flow Name / Label : Archived checkout list

Alternate Name : None
Description : Archived checkout list save in Archive
Origin : Archive checkout list and member list
Destination : Archive
Volume and Frequency : 50 per week

Data Flow Name / Label : Archived member list

Alternate Name : None
Description : Archived member list save in Archive
Origin : Archive checkout list and member list
Destination : Archive
Volume and Frequency : 100 per list

Data Flow Name / Label : Fine details

Alternate Name : none
Description : Calculate fine will give fine details to Member
Origin : Calculate fine
Destination : Member
Volume and Frequency : 15 per week

Data Flow Name / Label : Exceed due transaction detail

Alternate Name : None
Description : Transaction exceed due transaction detail to
calculate fine
Origin : Transaction
Destination : Calculate fine
Volume and Frequency : 15 per week
Data Flow Name / Label : Book detail
Alternate Name : None
Description : Book gives book details to generate report
Origin : Book
Destination : Generate report
Volume and Frequency : 100 per week

Data Flow Name / Label : Request to generate report

Alternate Name : None
Description : Librarian request to generate report
Origin : Librarian
Destination : Generate report
Volume and Frequency : 25 per week

Data Flow Name / Label : Generated report

Alternate Name : None
Description : Generate report gives generated report to librarian
Origin : Generate report
Destination : Librarian
Volume and Frequency : 25 per week

Data Flow Name / Label : Member detail

Alternate Name : None
Description : Member gives member detail to generate report
Origin : Member
Destination : Generate report
Volume and Frequency : 25 per week

Data Flow Name / Label : Archive

Alternate Name : None
Description : Archive gives detail to generate report
Origin : Archive
Destination : Generate report
Volume and Frequency : 25 per week
Data Flow Name / Label : Transaction detail
Alternate Name : None
Description : Transaction gives transaction detail to generate
report
Origin : Transaction
Destination : Generate report
Volume and Frequency : 25 per week