ICT502

DATABASE ENGINEERING
GROUP PROJECT FINAL REPORT
NAME STUDENT ID
AHMAD SYAMI BIN ISMAHADI 2022745427
MUHAMMAD HANIF BIN ADNAN 2022912847

MUHAMMAD IZZAT DANIAL BIN JAFRI 2022981313

MUHAMMAD UZZAIR BIN MOHD NIZAM 2022793429

MUHAMMAD SHAZWAN BIN SHAIRULHYZAM 2022782763

GROUP : CS2303C

PROGRAM CODE : ICT502

FACULTY NAME : FACULTY OF COMPUTER SCIENCE AND

MATHEMATICS

PREPARED FOR : MISS NUR ANIS IDAYU BINTI MOHD NOR

 TABLE OF CONTENT

TITLE PAGE

INTRODUCTION OF COMPANY BACKGROUND 1-3

DESCRIPTION OF PROBLEM 4

4
OBJECTIVES

SYSTEM DESIGN (FLOW CHART) 5-6

SQL QUERIES SAMPLE 7-11

SYSTEM DEVELOPMENT SAMPLE SCREEN 12-13

CONCLUSION 14

APPENDICES 15-21
INTRODUCTION

1.0 COMPANY BACKGROUND

Figure 1.0 photo among teachers SMK Bukit Gading

Sekolah Menengah Bukit Gading or known as SMBG was established in 1965 with its
original name “Darjah Menengah Kuang”. At the beginning of its establishment, this school
has 74 students in form 1 & 2 with a teaching staff of 5 people. At the time, SMBG only
boarded the SRK Kuang building until 1976 and in 1977 SMBG got its own building located
at KM 26, Sungai Plong and changed its name to Kuang Secondary School. In 2003, Sekolah
Menengah Kebangsaan Bukit Gading has opened classes for form 6 students. Now the school
already 55 years old. In 2009, Sekolah Menengah Kebangsaan Bukit Gading had 938 male
students and 980 female students. It has a total of 139 teachers. Blok Saintis Muda (Blok C)
was built in 1979, and its name was changed again to Bukit Gading Secondary School. The
school office was renovated in 1984, and the Balai Budaya (School Hall) was also installed
along with the meeting room for teachers. The first school song was composed in 1984.

1
 Noraini Ali, who is an SMBG undergraduate, created it with Hamid (School Inspector).
To accommodate the increase in students, 2 two-storey blocks (Block D and Block E) were
built in 1986. Then, 2 lightning building blocks (Block F and Block G) were erected in 1995.
A 3-storey building, and a vault were constructed in 1998.

In 1987, the school administration successfully developed a surau worth RM 60,000 in

collaboration with PTA. To accommodate the rise in students and teachers who have reached
a total of 2500 people, this surau was later upgraded until the end of 1999. And so SMBG
continues to flourish in terms of curriculum and co-curriculum, driving development.

2
 ORGANIZATIONAL CHART

Figure 1.1 Organizational Chart of SMK Bukit Gading

3
2.0 PROBLEM STATEMENT

Before the system that we developed were used in Sekolah Menengah Kebangsaan
Bukit Gading, the processes of works to be done are varies. In current system that is being
used in Sekolah Menengah Kebangsaan Bukit Gading where the case study has been done,
all tasks are done manually. Basically, teacher need to fill up a form for inventory details
on paper such as item code, item name, quantity, date and no perolehan.
The current system issue faced by Sekolah Menengah Kebangsaan Bukit Gading is that
the record filled out by the teacher could be lacking details because it was manually
registered by the teacher. Another issue is lack of security. Normally, files will be placed
on regular shelves, so it is possible that important files, such as students' personal
information, will be seen and misused by inappropriate people. In addition, it also takes up
space. this is because this school has many students of all ages, the number of personal files
for students will increase. Therefore, this will cause the school to need a lot of space to
store the items.

3.0 SYSTEM OBJECTIVES

Some major objectives of this system are as follow:
1. To overcome problems and complexity that have been identified.
2. To assist teachers in recording items from suppliers.
3. To store details better and safer than storing them manually.
4. To prevent from loss of items.
5. To track where the item is being stored at
6. To facilitate the management of school inventory.

4
4.0 SYSTEM DESIGN
FLOW CHART

5
Figure 4.0 Inventory System Flowchart

6
5.0 SQL QUERIES SAMPLE
1. SELECT * FROM ITEM
WHERE STOREID= 'B2'

Figure 5.0 SQL query sample 1

2. SELECT FNAME || ' ' || AS FULLNAME, HIREYEAR

FROM STAFF
WHERE HIREYEAR <= 2000

Figure 5.1 SQL query sample 2

7
3. SELECT STOREID
FROM STORAGE ORDER
BY STOREID

Figure 5.2 SQL query sample 3

4. SELECT COUNT(STAFFID) AS "STAFF_TOTAL"

FROM STAFF

Figure 5.3 SQL query sample 4

8
5. SELECT ITEMNAME, ITEMCODE, QUANTITY
FROM ITEM
WHERE ITEMNAME LIKE "%k"

Figure 5.4 SQL query sample 5

6. SELECT ITEMCODE,ITEMNAME,ORDERID
FROM ITEM
WHERE RECEIVEDATE > 2022/01/01

Figure 5.5 SQL query sample 6

9
7. SELECT STORAGELOCATION AS " BILIK STOR"
FROM STORAGE

Figure 5.6 SQL query sample 7

8. SELECT PASSWORD
FROM ADMIN JOIN STAFF
USING (STAFFID)
WHERE FNAME = 'rosnah'

Figure 5.7 SQL query sample 8

10
9. SELECT FNAME,LNAME, FNAME || '' || LNAME AS FULLNAME
FROM STAFF

Figure 5.8 SQL query sample 9

10. SELECT MIN(QUANTITY)

AS SMALLQUANTITY
FROM ITEM

Figure 5.9 SQL query sample 10

11
6.0 SYSTEM DEVELOPMENT SAMPLE SCREEN
LOGIN PAGE
The user must insert username and password to login the system

Figure 6.0 Login page Interface

ADD ITEM PAGE

The user can add the item what they wanted such as item code, order id, item name, quantity
of the item, store id and date received.

Figure 6.1 Add Item page Interface

12
EDIT PAGE
If the user wants to make changes to the desired item, they can update the item in this page.

Figure 6.2 Edit Item page Interface

DISPLAY PAGE
This page will display a list of all items previously entered by the user.

Figure 6.3 Display page Interface

13
7.0 CONCLUSION
This project is designed to meet the requirements of the system which able to meet the
objectives to the satisfaction of the school management. School management system is an
internal web-based platform system. it simplifies the works for teachers, as well as improve the
business process between students and including among teachers themselves. This project aims
to solve the problems in the SMK Bukit Gading. By using this system, the staffs in the school
should be able to do their works more efficiently and time saving. By the end of the project,
good and new features implemented into the system will have solved some of their inventory
system problems.

14
8.0 APPENDIX

Figure 8.0 Main Page

15
8.1 ENTITY RELATIONSHIP DIAGRAM (ERD)

Figure 8.1 Entity relationship diagram (ERD)

RELATIONAL SCHEMA

STAFF (staffid, fName, lName, hireYear)

SUPPLIER (orderId, supplierName, phoneNo)
ITEM (itemCode, orderId*, itemName, quantity, receiveDate)
STORAGE (storeId, itemCode*, StorageLocation)
ADMIN (staffId*, password)

16
8.2 DATA DICTIONARY
ADMIN

Table 8.2.0 Admin Dataset

ITEM PAGE

Table 8.2.1 Item Dataset

17
STAFF PAGE

Table 8.2.2 Staff Dataset

STORAGE PAGE

Table 8.2.3 Storage Dataset

18
8.3 DATA DEFINITION LANGUAGE (DDL)
8.3.1 TABLE ADMIN
CREATE TABLE ADMIN (
STAFFID varchar(220),
PASSWORD int(11),
PRIMARY KEY (STAFFID),
FOREIGN KEY (STAFFID) REFERENCES STAFF(STAFFID)
);

Table 8.3.1 Admin

8.3.2 TABLE ITEM
CREATE TABLE ITEM (
ITEMCODE varchar(220),
ORDERID varchar(220),
ITEMNAME varchar(220),
QUANTITY int(11),
RECEIVEDATE date,
STOREID varchar(220),
PRIMARY KEY (ITEMCODE),
FOREIGN KEY (STOREID) REFERENCES STORAGE(STOREID));

Table 8.3.2 Item

19
8.3.3 TABLE STAFF
CREATE TABLE STAFF (
STAFFID varchar(220),
FNAME varchar(220),
LNAME varchar(220),
HIREYEAR year,
PRIMARY KEY (STAFFID)
);

Table 8.3.3 Staff

8.3.4 TABLE STORE
CREATE TABLE STORE (
STOREID varchar(220),
ITEMCODE varchar(220),
STORAGELOCATION varchar(220),
PRIMARY KEY (STOREID),
FOREIGN KEY (ITEMCODE) REFERENCES ITEM(ITEMCODE)
);

Table 8.3.4 Store

20
DATA MANIPULATION LANGUAGE (DML)
ITEM
Insert data into item tables
INSERT INTO ITEM
VALUES (‘ORD1’, ‘KERUSI’, ‘10’, ‘19/6/2021’);
INSERT INTO ITEM
VALUES (‘ORD2’, ‘MEJA, ‘15’, ‘19/6/2021’);
INSERT INTO ITEM
VALUES (‘ORD3’, ‘PAPAN PUTIH, ‘10’, ‘19/6/2021’);
INSERT INTO ITEM
VALUES (‘ORD4’, ‘KABINET’, ‘12’, ‘19/6/2021’);

Select Item
SELECT * FROM ITEM

Delete Item
DELETE FROM ITEM WHERE itemName LIKE ‘%MEJA%’;

Update Item
UPDATE ITEM SET QUANTITY = ’12’ WHERE itemName = ‘PAPAN PUTIH’

21
ADMIN
Insert
INSERT INTO ADMIN VALUES (‘admin1’,’123’);
INSERT INTO ADMIN VALUES (‘admin2’,’456’);

Select
SELECT * FROM ADMIN

Delete
DELETE FROM ADMIN WHERE staffID LIKE ‘%admin2%’;

Update
UPDATE ADMIN SET password = ‘123456’ WHERE staffID = ‘admin1’

22
STAFF
Insert
INSERT INTO STAFF VALUES (‘admin1’,’rosnah’,’kasim’,’2000’);
INSERT INTO STAFF VALUES (‘admin2’,’roslan’,’haniff’,’1992’);

Select
SELECT * FROM STAFF

Delete
DELETE FROM STAFF WHERE lName LIKE ‘%kasim%’;

Update
UPDATE STAFF SET staffID = ‘admin3’ WHERE fName = ‘roslan’;

23
STORE
Insert
INSERT INTO STORE VALUES (‘B1’,’BILIK 1’);
INSERT INTO STORE VALUES (‘B2,’BILIK 2’);

Select
SELECT * FROM STORE

Delete
DELETE FROM STORE WHERE storageLocation LIKE ‘%BILIK 2%’;

Update
UPDATE STORE SET storeID = ‘B20’ WHERE storageLocation = ‘BILIK 2’;

24