FACULTY OF INFORMATION MANAGEMENT

UNIVERSITI TEKNOLOGI MARA

KAMPUS PUNCAK PERDANA
SHAH ALAM

IMS 506- DATABASE APPLICATION FOR INFORMATION MANAGEMENT

GROUP PROJECT:

BORROWING BOOK SYSTEM

PREPARED BY:

GROUP:

IM2453 ST4

PREPARED FOR:

DR MOHD RIDWAN BIN KAMARULZAMAN

DATE OF SUBMISSION: 9 DECEMBER 2019

 ACKNOWLEDGEMENT

In performing this group project, we take guideline from people that we respected to.
We feel so relieved because we can finish this database project. Thank you to Dr Mohd
Ridwan Bin Kamarulzaman, IMS 506- database application for information management
course Lecturer, University Teknologi MARA (UiTM) for the guideline in this group project.
Furthermore, thank you to those people that help us in this database. We would like to thank
all those who helped us throughout the process of this group project.

1|Page
 TABLE OF CONTENTS

NO CONTENT PAGE
1 INTRODUCTION 3
2 PROJECT MEMBERS
a) PROJECT TEAM MEMBERS 4
b) PROJECT TEAM ROLES AND RESPONSIBILITIES 5
3 DATABASE INITIAL STUDY
a) ORGANIZATION AND BUSINESS ACTIVITIES 6
b) PROBLEMS AND CONSTRAINT 6
c) OBJECTIVES OF DATABASE DEVELOPMENT 7
4 DATABASE CONCEPTUAL DESIGN
a) END-USER VIEWS, OUTPUTS AND TRANSACTION 8-9
REQUIREMENTS
b) BUSINESS RULES 10
c) ENTITY RELATIONSHIP DIAGRAM (ERD) 11-12
d) CONCEPTUAL ERD 12
e) NORMALIZATION 13
f) RELATIONAL DATABASE 14-16
g) DATA DICTIONARY 17-18
5 DATABASE LOGICAL DESIGN
a) TABLE CREATION 19-20
b) DATA INSERTION 20-21
c) SQL STATEMENT 21-22
6 CONCLUSION 23
7 LIMITATION & FUTURE ENHANCEMENT 24
8 REFERENCES 25

1. INTRODUCTION

Nowadays, everything is rapidity to make their work while people need technology to
help them in order to achieve target in short term. In technology era, people produce

2|Page
computer and internet to help people in making their job. We as a student try to use this
technology to help Perpustakaan Tun Abdul Razak (PTAR) UiTM Puncak Perdana to make
their work easier and faster. We choose library in UiTM Puncak Perdana in making this
borrowing book system or called as BBS.

BBS is a system that provide database for students of UiTM Puncak Perdana to borrow
book by registering book id with reservation log. It is because PTARPP does not have a
database for borrowing books properly. We, as a student must go to the PTARPP to borrow
the books. BBS is a reservation of books that can make by entering the data only. The staff
will search the book from the rack and student can just take it at PTAR. This system will
make it easier for the students to borrow books.

2. PROJECT MEMBERS

a) PROJECT TEAM MEMBERS

3|Page
 NURIN A’QILAH BINTI MOHD
SAIDJUDDIN

(PROJECT MANAGER)

ARNIESHELA SAIMIN

(ANALYST PROGRAMMER)

b) PROJECT TEAM ROLES AND RESPONSIBILITIES

Project Manager

4|Page
  The person responsible for managing the project.
 The person responsible for accomplishing the project objectives within the
constraints of the project. She is responsible for the outcome (success or
failure) of the project.
 Involved with the planning, controlling and monitoring, and managing and
directing the assigned project resources to best meet project objectives.
 Controls and monitors “triple constraints”—project scope, time and cost
(quality also)—in managing competing project requirements.
 Examines the organizational culture and determine whether project
management is recognized as a valid role with accountability and authority for
managing the project.
 Collects metrics data (such as author, books, staff and students).
 Responsible for identifying, monitoring, and responding to risk.
 Responsible to the project stakeholders for delivering a project’s objectives.
 The reporting structure of Project Manager changes depends on
organizational structure.

Analyst Programmer

 Programming - Programmer analysts use code to create new systems,

improve legacy systems and automate user tasks. Some tasks that a
programmer analyst may automate include those that are repetitive, such as
data entry of the books. The programmer analyst may also devise systems to
improve accuracy and control.
 System Analysis - Programmer analysts interpret user needs and
determine the most efficient computer systems that will accomplish the users'
goals.
 Database Maintenance and Development - Programmer analysts may
maintain and develop databases; however, the programmer analyst's role
with databases goes beyond the borrowing and storing of the reservation's
data.
 Documentation - Programmer analysts use change control tools to
document everything that impacts the system, such as changes to functional
and operational scope. An undocumented system can be a nightmare for
system users and for programmer analysts who must maintain the system.
3. DATABASE INITIAL STUDY

5|Page
a) ORGANIZATION AND BUSINESS ACTIVITIES

Our organization is conducted by two persons only which are Nurin A’qilah as
a Project Manager and Arnieshela as an Analyst Programmer. Nurin A’qilah
responsible for managing this BBS and accomplishing the project objectives
within the constraints of the project. Arnieshela responsible to interpret user
needs and determine the most efficient computer systems which is BBS that
will accomplish the user’s goal.

Our database is about student, book and reservation. Student can

borrow books from PTARPP by entering data in Borrowing Book System
(BBS). Staff will search out and pick up from the rack for the students.

BBS’s activities include mission planning, strategic planning, business

process and information management that include performance management
and portfolio management.

b) PROBLEMS AND CONSTRAINT

 There is no borrowing books system in Perpustakaan Tun Abdul

Razak UiTM Puncak Perdana for students.

 Books in the PTARPP are not arranged properly, staff cannot sort the
records by the date, author or others. For the books, they do not
arrange according to the year and types of the book.

 This BBS can help the user which is student to get the books by make
a reservation of the books through online.

 This BBS also help the responsible staff to manage the records of
books easier and properly by using automated system which will
provide the form in automated and up to date which one items are still
available.

6|Page
c) OBJECTIVES OF DATABASE DEVELOPMENT

1. To reserve the book at PTARPP.

o This objective wants to help students to reserve the books
through online without going to the PTAR just to choose the
books.

2. To increase the effectiveness in processing the records of books.

o This objective will improve the effectiveness in processing
the records which will make sure the flow of lifecycle of
records can run smoothly. Therefore, the PTARPP can
manage their records properly by using this system.

7|Page
4. DATABASE CONCEPTUAL DESIGN

a) END-USER VIEWS, OUTPUTS AND TRANSACTION REQUIREMENTS

8|Page
9|Page
 b) BUSINESS RULES

A business rules derived from a detailed description of an organization’s operations that

help to create and enforce actions within the organization’s environment. It defines
entities, attributes, relationships and constraints. To develop an accurate data model, the
database designer understanding of the organization’s data required. The business rules are
very important to the designer because they enable the designer to fully understand how
the business works and what role is played by data within company operations. The
following are the business rules for this database.

One student borrow one book (1:1)

One student borrow many book (1:M)
Many students borrow one book (M:1)

Many students borrow many book (M:N)

One author produce one book (1:1)

One author produce many book (1:M)

One author produce many book (1:M)

One staff input one book (1:1)

One staff input many book (1:M)
Many staff input many book (M:1)

Many staff input many book (M:N)

10 | P a g e
 c) ENTITY RELATIONSHIP DIAGRAM (ERD)

ERD 1

BOOK
STUDENT
PK Book_id
PK Stud_id
borrow Book_isbn
Stud_firstname
Book_title
Stud_lastname
Book_year
Stud_programm
Stud_phone

STUDENT RESERVATION BOOK

PK Stud_id PK Reserv_log PK Book_id

Stud_firstname FK Stud_id Book_isbn

Stud_lastname FK Book_id Book_title

Stud_programm Book_year

Stud_phone

ERD 2

AUTHOR BOOK
PK Aut_id PK Book_id
Aut_firstnam Book_isbn
Aut_lastname Book_title
Aut_address Book_year
Aut_country
Aut_city
Aut_state
Aut_postcode

11 | P a g e
ERD 3

STAFF RESERVATION BOOK

PK Staff_id PK Reserv_log PK Book_id
Staff_firstname FK Staff_id Book_isbn
Staff_lastname FK Book_id Book_title
Staff_phone Book_year

d) CONCEPTUAL ERD

12 | P a g e
 e) NORMALIZATION

1 NF (Normal Forms)

Stud_id Stud_firstname Stud_lastname Stud_programme Stud_phone

Staff_firstname Staff_lastname Staff_phone Book_title Book_isbn

Book_year Author_id

2 NF (Second Normal Forms)

Stud_id Stud_firstname Stud_lastname Stud_programme Stud_phone

Staff_firstname Staff_lastname Staff_phone Book_title Book_isbn

Book_year Author_id

Staff_id Staff_firstname Staff_lastname Staff_phone Book_title Book_isbn

Book_year Author_id

3 NF (Third Normal Forms)

Stud_id Stud_firstname Stud_lastname Stud_programme Stud_phone

Staff_id Staff_firstname Staff_lastname Staff_phone

Book_id Book_title Book_isbn Book_year Author_id

Primary Key Partial Dependency Transitive Dependency

f) RELATIONAL DATABASE

Our BSS contain 5 tables which is:

13 | P a g e
 Student

Staff

Book

14 | P a g e
Author

Reservation

15 | P a g e
g) DATA DICTIONARY

16 | P a g e
 Data Dictionary for Borrowing Book System

Table Name: Author

No Field Name Data Type Field Properties

.
1. Author_id Int (4) Primary Key
Field size = 4
2. Author_firstname Varchar (225) Field size = 225
3. Author_lastname Varchar (225) Field size = 225
4. Author_address Varchar (225) Field size = 255
5. Author_country Varchar (225) Field size = 225
6. Author_state Varchar (225) Field size = 225
7. Author_city Varchar (225) Field size = 225
8. Author_postcode Int (5) Field size = 5
9. Book_id Int (5) Field size = 5

Table Name: Book

No Field Name Data Type Field Properties

.
1. Book_id Int (5) Primary Key
Field size = 5
2. Book_title Varchar (225) Field size = 225
3. Book_isbn Int (20) Field size = 20
4. Book_year Int (4) Field size = 4
5. Author_id Int (4) Field size = 4

Table Name: Reservation

No Field Name Data Type Field Properties

.
1. Reser_log Int (6) Primary Key
Field size = 6
2. Stud_id Int (10) Field size = 10
3. Book_id Int (5) Field size = 5
4. Staff_id Int (10) Field size = 10

Table Name: Staff

No Field Name Data Type Field Properties

.
1. Staff_id Int (10) Primary Key

17 | P a g e
 Field size = 10
2. Staff_firstname Varchar (225) Field size = 225
3. Staff_lastname Varchar (225) Field size = 225
4. Staff_phone Int (10) Field size = 10

Table Name: Student

No Field Name Data Type Field Properties

.
1. Stud_id Int (10) Primary Key
Field size = 10
2. Stud_firstname Varchar (225) Field size = 50
3. Stud_lastname Varchar (225) Field size = 50
4. Stud_programme Varchar (5) Field size = 5
5. Stud_phone Int (11) Field size = 11

5. DATABASE LOGICAL DESIGN

a) TABLE CREATION

18 | P a g e
CREATE TABLE Publisher (
id INT(6) UNSIGNED AUTO_INCREMENT PRIMARY KEY,
name VARCHAR(30) NOT NULL,
address VARCHAR(225) NOT NULL,
city VARCHAR(50),
year TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
)

19 | P a g e
b) DATA INSERTION

INSERT INTO student (stud_id, stud_firstname, stud_lastname,

stud_programme, stud_phone)
VALUES (‘2017654321’, ‘Mohd’, ‘Ikmal’, ‘IM247’, ‘0187690879’)

20 | P a g e
 c) SQL STATEMENT

SELECT * FROM student WHERE stud_firstname = 'Mohd';

SELECT * FROM author WHERE author_firstname = 'Linda J.';

21 | P a g e
6. CONCLUSION

22 | P a g e
 We created a database that staff can use for keeping track the reservation of the books
by the student. In our case we have created the database according to the problem and
constraint that faced by PTAR UiTM Puncak Perdana. By creating database staff can
use database easily rather than track it by manual on reservation log book. Although we
have created this database according to the requirements in PTAR UiTM Puncak
Perdana. We hope that our database that we develop for PTAR Uitm Puncak Perdana
can help them to improve the quality of the system in tracking student reservation data.
The database structure is quite simple, which makes it easy for users to understand it.

During our database management course, we have learned about the basics of
database design. This project gave us the opportunity to try our new skills in practice.
While doing this project we also gained deeper understanding on database design and
how it can be implemented in real life situations. We believe that we can use our
database designing skills also in other assignments projects.

7. LIMITATION & FUTURE ENHANCEMENT

23 | P a g e
There are not many limitations of this database project but there are certain limitations
that affect the whole system. First limitation that BBS has is student can only borrow one
book in one day. Second limitation is staff cannot book issue in advance if book is
unavailable.

Our future enhancement is the student can borrow more book in one day. We also
want to provide one book that have multiple so the staff can key in the data easily.
Besides, create a well maintenance of storing data of management. Moreover, the
programmer should be the future imaging on the needs of the users.

Last but not least, we want to make the development of the data administration
strategy which is closely related to the borrowing book system (BBS)’s objectives.

24 | P a g e
REFERENCES

Aida Bakhri. (2017). Padamu jua hatiku berteduh. Selangor: Majujaya Indah Sdn. Bhd

Aii Fariza. (2016). Makmum yang paling aku cinta. Kuala Lumpur: Lovenovel Enterprise.

Amany. (2016). Re: Kau Ilhamku. Selangor: Majujaya Indah Sdn. Bhd.

Blake, M. (2016). Writing the comedy movie. New York: Bloomsburry Publishing Plc.

Bylton, Guid. (2016). The flyaway money. Great Britain: Peter Wilks

Cowgill, L. J. (2005). Writing Short Films. New York: Watson-Guptill Publications.

Fenner, A. (2004). Managing Digital Resources in Libraries. New York: The Haworth
Information Press.

Groom, Kevin. (2017). Network and data security for Non-Engineers. London:Taylor &
Francis Group, LLC

Gumelar, M. S. (2004). Memproduksi Animasi TV. Jakarta: PT Gramedia.

Hayward, Philip. (2013). Music in science fiction television. UK: Routledge

Kenrick, J. (2017). Musical Theatre. London: Bloomsburry Publishing Plc.

Kinsella, Sophie. (2012). I’ve got your number. Great Britain: Clays Ltd, St Ives plc.

Lankes, R. D. (2015). The library innovation toolkit. Chicago: American Library Association.

Lazarinis, F. (2015). Cataloguing and Classification. USA: Chandos Publishing.

Mcmahan, Alison. (2005). The films of Tim Burton. London: Contiuum International
Publishing Group Inc

Mir Hazil Azran Ramli. (2008). Aura Personaliti Warna. Kuala Lumpur: Percetakan Zafar
Sdn. Bhd.

Normaslina Masri. (2013). Jurutera Hati Saya. Selangor: Jemari Seni Sdn. Bhd.

Paling, Stephen. (1999). A Hardware & Software Primer for Librarian. Maryland: ScareCrow
Press, Inc.

Shanti Balraj Baboo. (2015). Makyung. Kuala Lumpur: Writers 2015

Solehah Ishak. (2012). Professorial Lecture Uitm. Uitm: Uitm Press

Umi Kalsom. (2012). Kampung Girl. Selangor: Penerbitan Karya Seni Sdn. Bhd.

Wallach, J. J. (2013). How America Eats. New York: Rowman & Littlefied.

25 | P a g e