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 Nguyen Chi Thanh Student ID BH00887

Class SE06205 Assessor name Nguyen Thanh Trieu

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 Thanh

Grading grid

P1 M1 D1

1|Page
2|Page
 ❒ Summative Feedback: ❒ Resubmission Feedback:

Grade: Assessor Signature: Date:

3|Page
 Signature & Date:

Contents

I. INTRODUCTION................................................................................................................................................................................4
II. DESIGN THE RALATIONAL DATABASE SYSTEM.....................................................................................................................5
1. Analyse the requirements and rules of the system............................................................................................................................5
2. Design entity relationship model......................................................................................................................................................7
III. Conclusion......................................................................................................................................................................................14
IV. References.......................................................................................................................................................................................14

Hình 1:diagrams...........................................................................................................................................................................................7
Hình 2:Users................................................................................................................................................................................................8
Hình 3:Roles................................................................................................................................................................................................9
Hình 4:Instructors......................................................................................................................................................................................10
Hình 5:Students.........................................................................................................................................................................................10
Hình 6:Courses..........................................................................................................................................................................................11
Hình 7:Classes...........................................................................................................................................................................................12
Hình 8:Grades............................................................................................................................................................................................12
Hình 9:Assignments...................................................................................................................................................................................13

4|Page
 I. INTRODUCTION
As a database developer working with large educational institutions like FPT schools, I'm currently engaged in the design and
development of a Content Management System (CMS). Given the continuous growth in the student population at FPT schools, the
need for a nimble and efficient system to manage and deliver services has become paramount in this expansive educational setting.

The primary objective of this project is to establish a comprehensive CMS tailored for students, teachers, and administrators. This
CMS aims to provide a user-friendly experience, enabling students to effortlessly discover and access the educational materials and
resources they require, while teachers can manage their resources and assignments efficiently. Additionally, it will facilitate the
registration and management of digital book borrowing, streamlining the process by utilizing online coupons.

In this endeavor, we will strategically employ a selection of tools, software, and programming languages to fulfill the outlined
requirements. The CMS will cater to three main user groups: administrators, teachers, and students. Our key challenge is to develop
an integrated database system that seamlessly connects these user segments while maintaining an optimal user experience. The end
goal is to deliver a fully operational system that adheres to industry standards and operational criteria, all while effectively managing
the wealth of digital resources and educational documents required in this dynamic educational environment..

II. DESIGN THE RALATIONAL DATABASE SYSTEM

1. Analyse the requirements and rules of the system

 User Roles and Permissions
o Requirement: Define and establish three distinct user roles within the CMS: Students, Teachers, and Administrators.
o Rule: Students should have access to content consumption and resource borrowing features. Teachers should be granted
content creation, editing, and assignment management capabilities. Administrators should have overall system control
and user management rights.
 Content Management:

5|Page
 o Requirement: Identify and categorize the various types of educational content to be managed, including textbooks,
articles, videos, and assignments.
o Rule: Each content item must include essential metadata, such as title, author, subject, grade level, publication date, and
keywords, to facilitate organized and efficient content discovery.
 User Registration and Authentication:
o Requirement: Implement a user registration system to enable students, teachers, and administrators to create accounts
securely.
o Rule: Strong and secure authentication methods must be in place to protect user data and system integrity. Optionally,
consider integrating Single Sign-On (SSO) for convenience and securi
 Content Creation and Editing:
o Requirement: Offer content creation and editing tools for teachers and administrators to update and manage educational
materials.
o Rule: Implement version control to track changes, edits, and revisions made to content. Ensure that only authorized users
(teachers and administrators) can edit and publish content.
 Search and Navigation:
o Requirement: Develop a powerful search functionality and intuitive navigation system to enable users to easily find and
access educational resources.
o Rule: The search function should be efficient, enabling users to search by various criteria (e.g., title, subject, author) and
display relevant results promptly. The navigation should provide a logical structure for users to explore content categories
and subcategories.
 Resource Borrowing:
o Requirement: Define a system for students to request and borrow books and resources.
o Rule: Implement a structured booking or checkout process for resource requests, ensuring that students can access
resources for a specified period. Notifications should be sent to users regarding due dates, renewals, or returns.
 Security and Privacy:
o Requirement: Implement robust security measures to protect user data and content.

6|Page
 o Rule: Security measures should include data encryption, user authentication, and authorization mechanisms. Ensure
compliance with data privacy regulations to safeguard user privacy and sensitive information.
 Backup and Recovery:
o Requirement: Establish a backup and disaster recovery plan to protect against data loss or system failures.
o Rule: Regularly back up system data and implement procedures for quick data recovery in case of unexpected incidents.
Testing the backup and recovery processes should be part of system maintenance.
 Documentation:
o Requirement: Create comprehensive documentation for users and administrators to assist in using the CMS.
o Rule: The documentation should be clear, accessible, and provide step-by-step instructions for users and administrators
to navigate and utilize the CMS effectively.

2. Design entity relationship model

a) Database Diagrams

7|Page
 Hình 1:diagrams

 This relationship diagram plays an extremely important role in designing CMS management system, with tables such as
Users, Students, Instructors, Classes, Roles,Courses,Grades,Assignments. This design table helps us analyze and build
relationships between attributes and between tables to manage user information.
b) Table
1) Users

8|Page
 Hình 2:Users

Column Data Type Description

UserID Bigint is the primary key that uniquely identifies
each record in the users table.
Username Varchar(50) This field stores the username logged into
the system CMS. This is information to
identify users and interact with the
system.
Password Varchar(50) This field stores the user's password
encrypted. Passwords are used to ensure
security and user authentication.
RoleID Bigint This field is a foreign key to the Roles
table, used to distinguish user roles.
Created_at Datetime This field stores the date and time of
creation of the user record in the system.
This information provides information
about the time the user was created.
Updated_at Datetime This field stores the last updated date and
time of the user record in the system.

9|Page
 This information provides information
about the last update to the user record
Deleted_at Datetime This field can be used to mark a deleted
user in the system.
 Users table to store information about users and maintain a list of user accounts in the system. The main function is to
identify users and manage their roles.
2) Roles

Hình 3:Roles

Column Data Type Description

RoleID Bigint Primary keys, representing different roles
in the system (e.g. lecturer, student).
RoleName Varchar(50) Name of the role
 Roles table to define roles in the system (e.g. lecturer, student). The main function is to manage the list of available roles.
3) Instructors

10 | P a g e
 Hình 4:Instructors

Column Data Type Description

InstructorID Bigint Primary key, unique for each instructor.
UserID Bigint Link to the Users table to identify the
instructor's user account.
InstructorName Varchar(50) Name of instructor
Email Varchar(50) Instructor's email address.
 Instructors table stores information about instructors, including information related to name, email, and user accounts. The
main function is to monitor and manage lecturers' information.
4) Students

11 | P a g e
 Hình 5:Students

Column Data Type Description

StudentID Bigint Primary key, unique for each student.
UserID Bigint Link to the Users table to identify student
user accounts.
StudentName Varchar(50) Name of student
Email Varchar(50) Student email address.
 Student table stores information about students, including names, emails, and user accounts. The main function is to track
and manage student information.
5) Courses

12 | P a g e
 Hình 6:Courses

Column Data Type Description

CourseID Bigint Primary key, unique for each course.
InstructorID Bigint Link to the Instructors table to identify
the instructor responsible for teaching
the course.
CourseName Varchar(50) Name of Courses
 Courses table store information about courses. The main function is to track and manage information about specific courses.
6) Classes

13 | P a g e
 Hình 7:Classes

Column Data Type Description

ClassID Bigint Primary key, unique for each class.
InstructorID Bigint Link to the Instructors table to identify
classroom management instructors.
CoursesID Bigint Link to the Courses table to identify the
course to which the class belongs.
ClassName Varchar(50) Name of Classes
 Classes table store information about classes in courses. The main function is to manage information about classes and link
them to courses and instructors.
7) Grades

14 | P a g e
 Hình 8:Grades

Column Data Type Description

GradeID Bigint Primary key, unique for each result
record.
StudentID Bigint Link to the Students table to identify the
students associated with the results.
ClassID Bigint Link to the Classes table to identify the
class associated with the result.
Grade Float Student scores or results in a particular
class.
 Grades table store information about student results in classes. The main function is to track and manage information about
student results.
8) Assignments

15 | P a g e
 Hình 9:Assignments

Column Data Type Description

AssignmentID Bigint Primary key, unique for each exercise.
ClassID Bigint Link to the Classes table to identify the
class associated with the assignment.
AssignmentName Varchar(50) Name of the exercise.
Description Text Detailed description of the exercise.
Duedate Date Assignment due date.
 Assignment table store information about assignments assigned to students in class. The main function is to track and
manage information about assignments and due dates.

III. Conclusion
During the process of designing the database for the CMS system, we took a series of important steps to ensure that the system was
built with consistency, reliability and efficiency. Here are some important points about the database design set:

Research and Analysis: Before starting design, we conducted a careful research and analysis process to understand the system
requirements and how the data would be used.

16 | P a g e
Relationship Management: We have designed the tables and relationships between them to ensure that information is logically
organized and easily accessible.

Efficiency and Security: Ensure that the database is designed for operational efficiency while protecting important and trusted data.

Maintain and Update: Recognize that a CMS system is never complete and will have to be maintained and updated regularly to meet
new requirements and fix bugs.

Flexibility: The database design needs to be flexible so that it can be expanded and adapted to the specific needs of the system and
users.

In short, the process of designing a database for a CMS system is an important part of building a powerful content management
system. Applying the principles of data normalization, relationship management, and ensuring database security and efficiency plays
an important role in creating a reliable and flexible CMS system.

IV. References

17 | P a g e