ASSIGNMENT 1 FRONT SHEET

Qualification TEC Level 5 HND Diploma in Computing

Unit number and

Unit 04: Database Design & Development
title

Date Received 1st

Submission date 3/3/2021
submission

Date Received 2nd

Re-submission Date
submission

Student Name Nguyen Duc Anh Student ID GCH190714

Class GCH0901 Assessor name HAN MINH PHUONG

Student declaration

I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I
understand that making a false declaration is a form of malpractice.

Student’s signature Anh

Grading grid

P1 M1 D1

1
❒ Summative Feedback: ❒ Resubmission Feedback:

Grade: Assessor Signature: Date:

Signature & Date:

2
Contents
Introduce..................................................................................................................................................................................................................... 5
I. Database Design.................................................................................................................................................................................................. 5
1. Scenario of the chosen system........................................................................................................................................................................ 5
2. Database requirements................................................................................................................................................................................... 5
3. Logical design (ERD)........................................................................................................................................................................................ 7
4. Explaination..................................................................................................................................................................................................... 8
5. Physical Design.............................................................................................................................................................................................. 10
II, DESIGN EVALUATION............................................................................................................................................................................................ 14
1. Advantages.................................................................................................................................................................................................... 14
2. Disavantages................................................................................................................................................................................................. 14
Conclusion................................................................................................................................................................................................................. 15

3
Introduce
I am working in a large IT company as a database specialist. Currently, FPT University is cooperating with my company
to create a system that makes it easier to manage students who go to school or take leave. They commissioned me to develop
this system. The system will have additional functions such as: displaying student attendance so parents can monitor whether
their child is in school and allowing students to check their attendance.

I. Database Design.
1. Scenario of the chosen system.
- Students can view class schedules and see if classes have been taken. For classes that are missing attendance,
students can contact the subject teacher to contact and mention the make-up attendance.
- For teachers who can register or reschedule for private reasons, the teacher also has the right to take
attendance of students in the class.
- Parents can access and view the schedule with student attendance on the system to keep track of their child's
situation.
2. Database requirements.
This system is based on the AP system of UoG.
- Student:
o Allows students to view class schedules.
o Allows students to see attendance.
o Allows students to view the teacher's contact information

4
 - Teacher:
o Allows teachers to take attendance for students.
o Allows teachers to view and register teaching schedules.
o Allow teacher to edit student attendance in 48 hours.

- Parents:
o Allows parents of the students to view their child's attendance.

 User requirements.
- Student:
o Login to the system.
o Check their own attendance.
o Can view the teacher's contact information.
- Teacher:
o Login to the system.
o View and register to the teaching schedule.
o Implement and edit student attendance.
- Parents:
o Login to the system.
o Check their children's attendance.
 System requirements
o Store, retrieve and update data
o Support for authorization to access and update data
o The database recovery facility should be corrupted

5
3. Logical design (ERD)

6
4. Explaination.

Entity1 Entity2 Relationship Explain

Login Teacher One to one A teacher has only one account to log in with and they
are provided by the university
Login Student One to one A student has only one account to log in with and they
are provided by the university
Login Parents One to one Each user will have only one account provided by the
university.
Student Course Many to A student can take many courses and vice versa, each
many course can have many students so the relationship
between them is many to many through the
StudentCourse entity.
Teacher Course Many to Each teacher can teach multiple courses and each
many course can be taught by multiple teachers, so the
relationship of these two entities is multiple for multiple
entities, linked through the linking entity is
TeacherCourse.
Course Attendance One to many There can be many lessons in a course so the
relationship between these two entities is one to many.
Student Attendance One to many Each student can be attendance multiple times in a
course so the relationship of these two entities is one to
many.
Parents Student One to many Parents can have more than 1 child and a student can
have only 1 parent.
AbsenceReaso Attendance One to many One reason can apply for multiple absence and a
n absence can have only one reason

Descriptive property for the entities:

7
 o Account: Username(pk), Password.
o Student: StudentID(pk), StudentUsername(fk), StudentName, StudentEmail, StudentPhone, Parents_parentsID
o Teacher: TeacherID(pk), TeacherUsername(fk), TeacherName, TeacherEmail, TeacherPhone.
o StudentCourse: CourseID(pk, fk), StudentID(pk,fk).
o Course: CourseID(pk), CourseName, StudyTime.
o TeacherCourse: CourseID(pk, fk), TeacherID(pk,fk).
o Attendance: StudentID(pk, fk), CourseID(pk, fk), StudentStatus, Absence_AbsenceReason.
o Parents: ParentsID(pk), ParentsUsername(fk), ParentsName, ParentsPhone, ParentsEmail.
o Absence: AbsenceReason.

Explain: The ERD indicated that this ERD meets the system's specifications. This ERD includes all of the entities, properties, and
connections that are necessary to construct a full database. The current manual timekeeping method is no longer incongruent
and awkward. It has domain entities including Student, Teacher, Parents, Course, and so on. Additionally, the ERD comprises
weak entities such as AbsenceReason, and so on. Multiple relations have related bodies. CourseID, StudentID are only a few
examples. These institutions effectively solved the system's challenges, which included student management, instructor
management, class preparation, student attendance and reviews, report submission, lesson cancellation, and so on. Each
entity's goals are augmented by attributes. Single value properties, multivalued properties like AbsenceReason, and basic
properties are all included in this ERD (StudentID) The ERD has demonstrated a two-way relationship between individuals,
displaying relationships as well as constraints through primary and foreign keys.

5. Physical Design

8
9
Login:

Student:

10
Teacher:

Parents:

StudentCourse:

11
TeacherCourse:

Course:

Attendance:

12
Absence Reason:

II, DESIGN EVALUATION

1. Advantages
First and foremost, when it comes to the administrator, the database must allow him or her to add new students to the
time and attendance system upon request. Additionally, they have the power to erase, edit, and monitor student
records, as well as instructor information, lesson schedules, and student engagement in courses. According to the
designer, his design has solved the problem. Only the administrator has access to the account management interface,
where he or she can add, delete, and edit information for instructor and student accounts, and only the database
manager has direct access to build accounts for high-level managers. As soon as the database is established, you can
start interfering with it.

Finally, students can access their own calendars, and if there is a mistake, they can alert the instructor directly so that it
can be corrected. After each attendance session, the student attendance rate is automatically determined. It also assists
parents in maintaining track of their children's classroom attendance.
2. Disavantages

Specifications and limitations are minimal. Knowledge quality loss: In the ER model, any knowledge can be missing or
concealed. Restricted relationship representation: As opposed to other data structures such as the relational model, the
ER model only reflects limited relationships. Data manipulation is difficult to demonstrate in an ER model since there is
no representation of it. Popular for high-level design: The ER model is commonly used for high-level design.
13
Conclusion
The author has included the solution and database in this article, but did not put in the user interface for the fully featured
attendance framework of FPT University. The relationships in the database designed by him are also clarified in the paper.
Build an individual ERD that has crossed the 3NF threshold. However, the architecture is not good enough, not convincing and
without the interface. The staff have learned a lot about spreadsheets, ERDs, physical architecture, and the shortcomings and
errors of reporting resulting from the lessons. With this experience, the author intends to learn more about database design
and development to be able to perform better projects in the future. In total, my system has satisfied a lot of FPT University
demands, but there are still certain functions that I am unable to introduce. According to the study, there are still a number of
areas that aren't especially appealing.

14