Database Design and Development Report for FPT University

This report presents a database design and development solution for the FPT University attendance system, addressing challenges related to student and staff management. The author, a database developer, analyzes the university's needs, focusing on the University of Greenwich Vietnam's attendance system as a case study. The report details the system's scope, objectives, and functional and non-functional requirements, including user roles (Admin, Teacher, Student), data validation, and constraints. An Entity-Relationship Diagram (ERD) is provided to illustrate the database structure, with explanations of entities, attributes, and relationships. Business rules, data validation rules, and examples for various entities such as Admin, Class, Parent, Session, Slot, Student, StudentAttendance, Subject, and Teacher are presented to demonstrate the system's functionality. The report also outlines tasks, timelines, and responsibilities for the project, concluding with a comprehensive overview of the proposed database solution designed to improve the efficiency and accuracy of the attendance system.

ASSIGNMENT 1 – Database Design and Development

Class: GCH0906
ASSIGNMENT 1 FRONT SHEET
Qualification TEC Level 5 HND Diploma in Computing
Unit number and title Unit 04: Database Design & Development
Submission date Date Received 1st submission
Re-submission Date Date Received 2nd submission
Student Name Truong Quoc Bao Student ID GCH200633
Class GCH0906 Assessor name Vuong Thi Nhung
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 Bao
Grading grid
P1 M1 D1

❒ Summative Feedback: ❒ Resubmission Feedback:
Grade: Assessor Signature: Date:
Signature & Date:

I. Introduction
The paper will describe the answer to an issue that the FPT university encountered. The author works for a big IT
consulting firm as a database developer. The FPT university has approached a firm that is expanding due to the
increase in student numbers. The university administration at FPT is currently having issues. The business was asked
by FPT University to fix the problem. Working with the university, determining current needs for the entire system,
analyzing, producing, and designing a fully functioning and technical database system based on an existing system
design that can address the FPT university's problem are the author's responsibilities.
1. Scenario of the chosen system
The University of Greenwich Vietnam is experiencing difficulties with their attendance system.
The schedule manager will organize the study schedule by subjects at the start of each semester. The timetable for each
class will be different. Due to unforeseen problems, the class schedule may be modified during the weekend. Teachers
will take attendance for their pupils in each class, and the teacher will provide the attendance list to the schedule
management staffs at the end of each class. Based on the overall number of class sessions and the total number of
absences. Student absences will be a significant factor in determining a student's success. If a student miss more than
20% of their classes, the academic department will call their parents and tell them of their children's academic
performance. If a student miss more than 25% of the total sessions, the student will no longer be graded and will have to
retake the test or the class. He (or she) can, however, nonetheless take part. This attendance system is operated by
hand.
Without a database, students will have a difficult time determining whether their attendance is valid and requesting that
their professors amend it. When teachers face unanticipated issues that force them to modify their teaching schedule, it is
extremely difficult for the university to tell students in a timely manner about the unexpected change. It was also difficult to
take attendance because all of the attendance procedures are done on paper. Deviation and data loss are unavoidable
when teachers (schedule managers) take attendance for a large number of pupils.
Greenwich University Vietnam has engaged database designers for its attendance system to address the aforementioned
issues. The database designer must figure out how many students are in the class. The designer must also identify each
student's specific details as well as the teacher's personal information. A list of classes available for the current semester,
as well as a list of students for each class, should be identified by the database designer. Each semester, the school
needs to know the teaching timetable. The teaching schedule can be changed; however, it must be communicated 12
hours prior to the scheduled session for that day) and an attendance record for each instructor will be generated. The

teacher takes attendance of their students during each session. Teachers will have two days after the start of the session
to modify attendance. If a student miss more than 25% of the total sessions in a topic, the system will automatically send
an email to their parents requesting proof that they have missed the permitted absences. Students can also rate the
quality of instruction by answering five questions with four alternatives each. When half of the modules have been
completed, these questions will be asked. The technology may compute each teacher's GPA based on the feedback
provided by the students. The first answer of each question is 4, the second is 3, the third one is 2 and the finally is 1.
The database must be able to accommodate a wide range of user categories. Different permissions are required to
access the system. Admin, Teacher, and Student are the three types of users that will be available. When it comes to the
admin, they have full access to the database's contents. This implies they can perform the majority of actions that users
with less rights cannot, such as updating, adding, and removing user information. The instructor, who can examine
information about themselves and their pupils, check their own schedule, and take attendance, is the second access
class. Finally, students can only view their own and instructors' information, as well as whether they are present or absent.
2. Scope of the system
- Time: 4-6 months
- Budget: 40000-45000 USD
- User: 10000 users included teachers/student/parents…
- Campus: Hanoi, Da Nang, HCM, Can Tho
3. Objectives
- Build a new system that meet requirements of high speed, can serve at least 5000 students and staffs
4. Task & Timelines
Task No Task Time Who responsible for
1 Requirement Collections 3 weeks Bao
2 Requirement Analysis 2 weeks Nam
3 ERD design 4 days Huy
4 Physical design 4 days Duong
5 Coding 2 months Chuc
6 Testing 2 weeks Khanh
7 Documentation 1 weeks Minh

8 Implementation 4 months IT staff
9 Maintenance 5 days Duc
II. SRS (System Requirement Specification)
1. Functional requirements
- The database enables decentralization for the system's many users.
- Admins have full access to the database and may do a variety of activities such as adding students, staffs, and
instructors; deleting students, staffs, and teachers; amending information, editing attendance, and so on.
- Teachers can alter each student's attendance, but they won't be able to do so after the first two days of class.
- The teacher has access to the student's information, but they are unable to modify it.
- The teacher has access to the student's personal GPA, which is determined based on their input.
- Only the student's schedule and attendance report are visible to them.
- Students can also provide feedback on the teaching quality.
2. Non-functional requirements
Software requirements:
- The program must have a user-friendly interface that students, instructors, and managers can use.
- Students' information must be kept private; students cannot see other students' information, but instructors and staff
may.
- Teachers do not have access to student comments; they only have access to the GPA.
- The program must run on Windows XP, Windows 7, Windows 8, Windows 10, MAC OS, Linux, and other versions of
these operating systems.
- It is necessary to use less workstation and server resources.
Hardware requirements:

- A hard disk with a minimum of 6GB of free space is required.
- The minimum RAM capacity is 4GB, and the CPU speed is 1.0GHz for x86 processors and 1.4GHz for x64 processors.
- Internet access is necessary.
Server requirements:
- Every two hours, all of the data in the system is backed up.
- At least 1000 people must be able to use the system at the same time.
- Simple to create and maintain.
- The data's integrity and security must be assured.
- Make sure that if the user does not respond after 10 minutes, the system logs them out automatically.
3. Database Design with explanations:
a. Business rules/constraint
- Admin creates class sessions
- Teachers view timetable
- Students view timetable
- Teachers take attendance on time
- Student attendance can be edited within 2 days
- Only the admin has the right to edit attendance after the teacher submits it 2 days before
- Parent can see the student's personal profile information

b. A picture of ERD

c. Explanation
- The provided ERD demonstrates that this ERD is appropriate for the system. This ERD supplied all of the essential
entities, characteristics, and relationships to eliminate the present attendance system's inconsistency and inconveniency.
It features powerful entities like Student, Teacher, and so on. Furthermore, the ERD contains weak entities such as
Feedback... These entities essentially handled the system's problems: student management, instructor management,
scheduling, attendance, and feedback. Attributes are also used to support the aims. Single value properties, multivalued
attributes like Room (a room may be utilized by many classes), basic attributes (StudentID), and composite attributes are
all included in this ERD (Slot includes 2 attributes StartTime and EndTime). ERD has demonstrated a two-way
relationship between entities, displaying both relationships and restrictions.
Relation 1 Relation 2 Type of Relationship Reason
Student Parent 1-1 A student has only one
parent
Teacher Session 1 - Many A teacher can teach many
session
Session Teacher Many - 1 A class can be taught by 1
teacher
Session Subject Many - 1 A class has only 1 subject
Subject Session 1 - Many A subject can be taught in
many session
Class Session 1 - Many A class has many sessions
Session Class Many - 1 A session belongs to a class
Question Answer Many - 1 A question belongs for 1
answer
Session StudentAttendance 1 - Many A session can have many
attendance
StudentAttendance Session Many - 1 An attendance belongs to a
session

Session Slot Many - 1 A session has only 1 slot
Slot Session 1 - Many A slot can illustrate for many
session
4. State that it meets 3rd Norm & Why
III. Data validation & Constraint
Validation:
- The users' IDs must be less than or equal to 10 characters in length.
- The user's name has a maximum length of 50 characters. It also supports Unicode characters.
- The phone number must be at least ten characters long, begin with a zero, and include only numbers.
- Users' email addresses must end in @fpt.edu.vn. Because an email only contains one @ character, the system will
reject emails like a@[e-mail].
- Each school of data for dates, such as StartDate, EndDate, Date, and so on, must be in the format YYYY-MM-DD.
- Text data types must be used for description entities such as Subject, Note, Answer, etc., as the description may be
rather extensive.
- The TotalSession type must be int, and it cannot be negative.
- The image must be in the.JPG or.PNG format.

Administrator:
Example:
- Admin ID: admin1
- Admin Name: Võ Hoài Linh
- Admin Email: [e-mail]
- Admin Phone: [phone]
- Admin DoB: 10/10/1969
- Admin Password: abcdef

Class:
Example:
- Class ID: GCH0906
- Teacher ID: nhungvt13
- Subject ID: 1622
- Room: R12
- StartDate: 2021-09-30

Parent:
Example:
- Student ID: GCH200633
- Parent’s Name: Nguyễn Thị Tình
- Parent’s Phone: [phone]
- Parent’s Email: [e-mail] (not required)

Session:
Example:
- Session ID: GCH09062021/10/10R12Slot1
- Session Date: 2021-09-30
- Class ID: GCH0906
- Slot: 1
- Room: R12

Slot:
Example:
- Slot: 1
- Start time: 7:30AM
- End time: 9:00AM

Student:
Example:
- Student ID: GCH200633
- Student Name: Trương Quốc Bảo
- Student Email: [e-mail] (not required)
- Student Class: GCH0906
- Student Phone: [phone]
- Student Image: 3x4 image

- Student Date of Birth: 2002-04-11
- Major: IT
- Student Password: abcde12345
StudentAttendance:
Example:
- Student ID: GCH200633
- Session ID: GCH09062021/10/10R12Slot1
- AttendStatus: Attend (Absent)

Subject:
Example:
- Subject ID: 1622
- Subject Name: Database
- Description: A database is a collection of information that is organized so that it can be easily
accessed, managed, and updated. Computer databases typically contain aggregations of data
records or files, containing information about sales transactions or interactions with specific
customers.
- Total Session: 40
- Unit code: B/616/1622
- Unit type: Core

- Unit level: 4
- Credit value: 15
Teacher:
Example:
- Teacher ID: nhungvt13
- Teacher Name: Vương Thị Nhung
- Teacher Phone: [phone]
- Teacher email: [e-mail]
- Teacher Password: abcde123456

IV. Conclusion
The author of this paper offered a solution, a database, and a user interface for the FPT university's full-featured
attendance system. He also discusses the relationships in the database he created in detail. As each entity reaches 3NF,
the ERD is built. However, the design proved inadequate. The writer learned a lot about databases, ERDs, and physical
design through the teachings... With this information, the author wishes to learn more about database design and
development in the future and to better himself.