Scribd
Upload
361 views6 pages

DB - A01 Group 13

1. The document outlines the specifications and design of a course registration database. It includes specifications for student course registration such as credit hour limits and approval requirements. 2. It describes normalization of the database from 1NF to 3NF. This separates the tables into student, course, dean, coordinator, and head program tables with foreign keys. 3. An entity-relationship diagram is designed using Crow's Foot notation to model the relationships between tables.

Uploaded by

SITI WARDINA SAFFIYYAH BI20110263
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
361 views6 pages

DB - A01 Group 13

1. The document outlines the specifications and design of a course registration database. It includes specifications for student course registration such as credit hour limits and approval requirements. 2. It describes normalization of the database from 1NF to 3NF. This separates the tables into student, course, dean, coordinator, and head program tables with foreign keys. 3. An entity-relationship diagram is designed using Crow's Foot notation to model the relationships between tables.

Uploaded by

SITI WARDINA SAFFIYYAH BI20110263
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

COURSE

KT24503 DATABASE

SECTION

SESSION

1-2021/2022

TITLE:

DB_A01 GROUP 13

STUDENT NAME MATRIC NO

MICHELLE MARIM JACKSON BI20110204

BIBIANA ARTECCA BINTI JAMES BI20110222

NADIA NATASHIA BINTI KAMARUDIN BI20110238

SITI WARDINA SAFFIYYAH BI20110263


1. Project Specification
1.1 Specifications
i. One course registration application form can only have one application type.
ii. One student can register (add or drop) to many courses. One course can be
registered (add or drop) by many students.
iii. One student can only register not more than twelve (12) credit hours and not
more than twenty-one (21) credit hour each semester.
iv. Students whom CPGA less than 2.30 must register less than fifteen (15)
credit hours unless approved by the dean.
v. Each application should be supported/completed by the head of the
program/academic advisor. If it is PPIB or KOKUM courses, then the
coordinator will be responsible.
vi. The application can only be processed if approved by the dean.
vii. Each application should have a status for closer monitoring.
1.2 Entities, Attributes, Relationships, and Constraints
2. Conceptual Database Design
2.1 Normalization Process (1NF to 3NF)
• Primary key
• Foreign key
• Composite key

REGISTRATION(studentID,studentName,status,cgpa,phone,facultyID,programID,progra
mName courseID,courseName,credithour, facultyName, semester,data,type, deanID,
deanName, coordinatorID,coordinatorName, headprogID,headprogName,
headprogApprov, coordinatorAprov, deanApprov)

First Normal Form (1NF)

REGISTRATION(studentID,studentName,cgpa,status,phone,facultyID,programID,fa
cultyName, programName,semester, data,type headprogApprov, coordinatorAprov,
deanApprov)

COURSE(courseID,courseName,credithour)

DEAN(deanID,deanName)

COORDINATOR(coordinatorID,coordinatorName)

HEADPROGRAM(headprogID,headprogName)
Second Normal Form (2NF)
REGISTRATION(studentID, studentName, cgpa, status , phone, semester, type ,
headprogApprov, coordinatorAprov, deanApprov)

COURSE(courseID,courseName,credithour)

DEAN(deanID,deanName)

COORDINATOR(coordinatorID,coordinatorName)

HEADPROGRAM(headprogID,headprogName)

FACULTY(facultyID,facultyName)

PROGRAM(programID,programName)

Third Normal Form (3NF)

REGISTRATION(status,data,type)
APPLICATION(applicationID, headprogApprov, coordinatorAprov ,deanApprov)

STUDENT(studentID,studentName,cgpa,phone,semester)

COURSE(courseID,courseName,credithour)

DEAN(deanID, deanName)

COORDINATOR(coordinatorID,coordinatorName)

HEADPROGRAM(headprogID,headprogName)

FACULTY(facultyID,facultyName)

PROGRAM(programID,programName)
2.2 Entity-Relationship Diagram (ERD) model using Crow’s Foot notation

You might also like