UNIVERSITI TEKNOLOGI MARA (UiTM) CAWANGAN MELAKA

KAMPUS JASIN

SEMESTER 1 SESSION 2021/2022

MAC. 2022 – AUG. 2022

ICT450
DATABASE DESIGN AND DEVELOPMENT

CLASS: M3CS2531A
GROUP: 5

PREPARED BY:

NO STUDENT NAME STUDENT ID

1 HEDZWEEN BINTI MOHD PUAD 2022977615

2 MUHAMMAD HARITH IKHWAN BIN ROSMAEINI 2022753195

3 NUR ‘ARIF BIN JOHAN 2022753317

4 WAN MUHAMMAD SYAFIQ BIN WAN SHAARI 2022793471

PREPARED FOR: SIR MOHD SHUKOR ABD RAHMAN

TABLE OF CONTENT

CONTENT PAGE

ACKNOWLEDGEMENT 2

1.0 COMPANY BACKGROUND ……………………………………………..………. 2-3

2.0 PROBLEM STATEMENT……………………………………………….…………... 3

3.0 OBJECTIVES………………………………………………………………………… 3

4.0 ENTITY RELATIONSHIP DIAGRAM…………………………………….………… 4

5.0 NORMALIZATION……………………………………………………….………….. 5-7

5.1 FIRST NORMAL FORM…………………………………………………….………. 5

5.2 SECOND NORMAL FORM……………………………………………….………… 6

5.3 THIRD NORMAL FORM……………………………………………….……………. 7

6.0 TABLES WITH DATA INTEGRITY……………………………..………………… 8-9

7.0 DATA DICTIONARY……………………………………………………………….. 10-11

8.0 DATA DEFINITION LANGUAGE …………………………………..……………. 12-13

9.0 SCREENSHOTS OF APPLICATION………………………………….…………. 14-23

10.0 10 SQL QUERIES…………………………………………………………………. 23-28

11.0 CONCLUSION……………………………………………………….……………… 29
ACKNOWLEDGEMENT

We are grateful to our lecturer, Sir Muhd Shukor who gave us the opportunity to work on this
project. We were able to complete this assignment on time with the guidance and support from
our lecturer which aided us a lot in completing this assignment. We would also need to give
recognition to each member of the team for their teamwork and participation while finishing this
assignment. Furthermore ,we would like to thank everyone who is involved in the project directly
or indirectly. Above all, we would like to express our gratitude to Great Almighty for always have
His blessing on us.

1.0 Company Background

Sekolah Menengah Kebangsaan Sultan Ismail Johor was established in 1960 and was launched
by Almarhum Sultan Ismail Ibni Almarhum Sultan Ibrahim on Thursday, 30th March 1967 coincide
with 18th Zulhijjah 1386. The school name is derived from the name of His Majesty the late Sultan
Ismail Ibni Almarhum Sultan Ibrahim, taken in conjunction with his services to the people of Johor
and his interest in the development of national students. Students at the beginning of the
establishment had to board at several other schools in Johor Bahru. Among them is Maktab
Sultan Abu Bakar (MSAB) which accommodates a Malay form 1 class before the male student
moved to Sekolah Menengah Dato 'Jaafar (SDJ) while the female student moved to Sekolah
Menengah Perempuan Sultan Ibrahim (SIGS). Female students moved back to MSAB in 1963.

The Malay classes got their own building in Jalan Abdul Samad and were named Sekolah
Menengah Kebangsaan Sultan Ismail in March 1964. Form 1 to 5 classes started since then and
the first principal was Encil Ali bin Ismail. Form 6 classes were opened in 1969 for other districts in
the state of Johor. SSI converted to Upper Secondary School (forms 4 -6 only) in 1972. SSI was
restored to full secondary school status (transition to T6) in 1975. The SSI teaching staff has
increased from 18 people to 60 people in 1968 and increased to 100 people in 1983. The Parents
and Teachers Association (PIBG) was established in 1974. Its 1st President is Encik Abdul
Rahman bin Ariffin.

SMK Sultan Ismail reciprocated the kindness of accommodating in other schools by accepting
812 students and 32 teachers from SM Tasek Utara (1970-1974), Kolej Putri Tunku Ampuan
Mariam Johor Bahru (1985), Felda students from other districts, Yayasan Sabah students ( 1971-
2002). The students were given the facility to live in the Pusat Puteri Hostel and the Pusat Putera
Johor Bahru Hostel.

2 Special Religious Program (KAA) classes for girls for each lower secondary level were started in
1991.

Business Rule

1. In a school system, the school needs to collect the students’ information such as student id,
student name, student ic, parent id, register date, sexuality, address, city, state and birth date to
enroll in a class while a class must have class id and class name to generate timetables.

2. Teacher information such as teacher id, teacher name, class id, subject code, HOD id and
teacher’s religion must be recorded into the system to simplify the process of assigning the
 teacher for each class. Each teacher can only teach one subject at a time but each subject
can be taught by many teachers.

3. Every parent(s) information must have parent id, parent name, parent ic and occupation
that need to be documented to enroll their children to study in the school as a student. Parents
can have one or many children but a student can only have one parent.

4. Every class information must have class id and class name must be recorded into the
system to simplify the process of assigning class for each student. Each class can have many
students at the same time but each student can enter one class at once.

5. Students need to enroll in the school. The enrollment must consist of enroll id, class id,
student id and registration date to ease the registration process for every student. The
process of enrollment can help to divide the students into classes.

6. For the timetable information must have timetable id, class id, subject code, class day and
class time must be recorded into the system to simplify the process of assigning timetables for
each class. A timetable can be used by many classes and on the other hand, a class can only
use one timetable at the same time.

7. Each timetable must consist of subjects for the teacher to teach each class. Subject needs
the information such as subject code and subject name. Each teacher can teach a subject and
each timetable consists of a subject.

8. The teacher information has teacher id, teacher name, class id, subject code, hod id and
teacher religion. Teacher manages other teachers based on their hod id.

2.0 PROBLEM STATEMENT

● SMKSSI uses a manual file system for any operations.

● It causes inconvenience towards the school clerk to manage the data manually.
● Difficulties were made upon up to date data queries for new and old students.
● There is no complete view of the data and information regarding the teachers, students
and parents.
● Thus, it may disturb the quality of services provided by the school.

3.0 OBJECTIVE
The purpose of this allocation is to design and develop an exceptional database for the school,
SSI. The school offers many benefits when a database is implemented and used by using the
database to store and manipulate data and information.

4.0 ERD

5.0 NORMALIZATION

5.1 FIRST NORMAL FORM

The normalization phase of a relational database with iteration groups and attributes removed
by placing each in a separate table linked by a primary key-foreign key relationship.

1NF
SMK SULTAN ISMAIL (STUDENT_ID, STUDENT_NAME, STUDENT_IC, REG_DATE, SEX,
BIRTH_DATE, ADDRESS, CITY, STATE PARENT_ID, PARENT_NAME, PARENT_IC,
OCCUPATION, CLASS_ID, CLASS_NAME, CLASS_DATE, CLASS_TIME, SUBJECT_CODE,
SUBJECT_NAME, TEACHER_ID, TEACHER_NAME, HOD_ID, TEACHER_RELIGION, DATE_REG)
PARTIAL DEPENDENCIES

(STUDENT_ID -> STUDENT_NAME, STUDENT_IC, REG_DATE, SEX, BIRTH_DATE,

ADRESS, CITY, STATE)
(PARENT_ID -> PARENT_NAME, PARENT_IC, OCCUPATION)
(SUBJECT_CODE -> SUBJECT_NAME)
(TEACHER_ID -> TEACHER_NAME, TEACHER_RELIGION)

TRANSITIVE DEPENDENCY
(CLASS_ID -> CLASS_NAME)

5.2 SECOND NORMAL FORM

Second Normal Form (2NF) is the same as 1NF but without partial dependencies.
2NF

STUDENT (STUDENT_ID, STUDENT_NAME, STUDENT_IC, REG_DATE, BIRTH_DATE, SEX,

❑
PARENT_ID¿ , ADDRESS, CITY, STATE)
PARENT (PARENT_ID, PARENT_NAME, PARENT_IC, OCCUPATION)
ENROLLMENT (ENROLL_ID, CLASS_ID*, STUDENT_ID*, DATE_REG)
SUBJECT (SUBJECT_CODE, SUBJECT_NAME)
TEACHER (TEACHER_ID, TEACHER_NAME, SUBJECT_CODE*, TEACHER_RELIGION)
TIMETABLE (TIMETABLE_ID, CLASS_ID*,SUBJECT_CODE*, CLASS_DATE, CLASS_TIME)

TRANSITIVE DEPENDENCY
(CLASS_ID -> CLASS_NAME)

5.3 THIRD NORMAL FORM

3NF

STUDENT (STUDENT_ID, STUDENT_NAME, STUDENT_IC, REG_DATE, BIRTH_DATE, SEX,

ADDRESS, CITY, STATE, PARENT_ID)
PARENT (PARENT_ID, PARENT_NAME, PARENT_IC, OCCUPATION)
ENROLLMENT (ENROLL_ID, DATE_REG, CLASS_ID, STUDENT_ID)
CLASS (CLASS_ID, CLASS_NAME)
SUBJECT (SUBJECT_CODE, SUBJECT_NAME)
TIMETABLE (TIMETABLE_ID, CLASS_ID*, SUBJECT_CODE*, CLASS_DATE, CLASS_TIME,
CLASS_ID, SUBJECT_CODE)
TEACHER (TEACHER_ID, TEACHER_NAME, CLASS_ID, SUBJECT_CODE, HOD_ID,
TEACHER_RELIGION*)

6.0 TABLE WITH DATA INTEGRITY

These are our tables, namely Table CLASS, Table ENROLLMENT, Table PARENT, Table
STUDENT, Table SUBJECT, Table TEACHER and Table TIMETABLE.

6.1 Data in Table CLASS

6.2 Data in Table ENROLLMENT

6.3 Data in Table PARENT
6.4 Data in Table STUDENT

6.5 Data in Table SUBJECT

6.6 Data in Table TEACHER
6.7 Data in Table TIMETABLE
7.0 DATA DICTIONARY
7.1 Data dictionary for CLASS

7.2 Data dictionary for ENROLLMENT

7.3 Data dictionary for PARENT

7.4 Data dictionary for STUDENT

7.5 Data dictionary for SUBJECT

7.6 Data dictionary for TEACHER

7.7 Data dictionary for TIMETABLE

8.0 DATA DEFINITION LANGUAGE

8.0.1 Creating TABLE STUDENT (

STUDENT_ID INTEGER PRIMARY KEY,
STUDENT_NAME VARCHAR(255),
STUDENT_IC INTEGER,,
REG_DATE DATE,
SEX VARCHAR(255),
BIRTH_DATE DATE,
ADDRESS VARCHAR(255)
CITY VARCHAR(255)
STATE VARCHAR(255)
FOREIGN KEY(PARENT_ID) REFERENCE PARENT );

8.0.2 Creating TABLE CLASS (

CLASS_ID INTEGER PRIMARY KEY,
CLASS_NAME VARCHAR(255) );

8.0.3 Creating TABLE TEACHER (

TEACHER_ID INTEGER PRIMARY KEY,
TEACHER_NAME VARCHAR(255),
CLASS_ID INTEGER,
TEACHER_RELIGION VARCHAR(255)
FOREIGN KEY(SUBJECT_CODE) REFERENCE SUBJECT );

8.0.4 Creating TABLE PARENT (

PARENT_ID INTEGER PRIMARY KEY,
PARENT_NAME VARCHAR(255),
PARENT_IC INTEGER,
OCCUPATION VARCHAR(255) );
8.0.5 Creating TABLE SUBJECT (
SUBJECT_CODE INTEGER PRIMARY KEY,
SUBJECT_NAME VARCHAR(255) );

8.0.6 Creating TABLE ENROLLMENT (

ENROLL_ID INTEGER PRIMARY KEY,
DATE_REG DATE,
FOREIGN KEY(CLASS_ID) REFERENCE CLASS
FOREIGN KEY(STUDENT_ID) REFERENCE STUDENT );

8.0.7 Creating TABLE TIME TABLE (

TIMETABLE_ID INTEGER PRIMARY KEY,
CLASS_DATE DATE,
CLASS_TIME TIME,
FOREIGN KEY(CLASS_ID) REFERENCE CLASS(CLASS_ID),
FOREIGN KEY(SUBJECT_CODE) REFERENCE SUBJECT(SUBJECT_CODE) );

9.0 SQL QUERIES

1. Number of student in each class
 2. Number of teacher for each subject

3. Number of subject

10.0 CONCLUSION

In conclusion, we believe that the data management for SMKSI in the aspect of personal details,
classes and others can be improved significantly by using the database. With the addition of this
database, we really hope that SMKSI will be able to manage their data more efficiently and neatly
arranged for easier usage in the future.