DatabaseDesign-C2SE 24-V1 0

International School
Capstone Project 2
CMU-SE 451
Database Design Document

Version 1.0
Date: 12/03/2021
UNIVERSITY REVIEWS
Submitted by
Nguyen Van Minh Toi

Nguyen Huu Thien
Ho Xuan Sang
Huynh Thi Quy Thuong
Approved by
Proposal Review Panel Representative:
Name Signature Date
Capstone Project 2- Mentor:

_______________________
Name Signature Date

Dr.Ha Thi Nhu Hang
C1SE.04 Team Database Design Document
PROJECT INFORMATION
Project acronym URs

Project Title University reviews
Start Date March 01, 2021 End Date May 31, 2021
Lead Institution International School, Duy Tan University

Project Mentor & Dr. Ha Thi Nhu Hang
contact details Email: hatnhuhang@duytan.edu.vn
Tel: 0707121301
Product Owner Toi, Nguyen Van Minh
Email: minhtoi2799@gmail.com
Tel: 0902257132
Scrum Master Thien, Nguyen Huu
Email: huuthiennguyen1999@gmail.com
Tel: 0783533812
Name Email Tel
Toi, Nguyen Van Minh minhtoi2799@gmail.com 0902257132
huuthiennguyen1999@gmail.
Thien, Nguyen Huu 0783533812
com
Team members
Sang, Ho Xuan hsang19999@gmail.com 0362982905
Thuong, Huynh Thi
quythuong0405@gmail.com 0333633770
Quy
DOCUMENT NAME
Document Title Database Design Document
Author(s) C2SE.24 Team
Role Sang, Xuan Ho
Toi, Nguyen Van Minh
Date May 01, 2021 File Database Design v1.0
name:
URL
Access
2
REVISION HISTORY
Version Date Comments Author Approval
1.0 May 01, 2021 Initial Release Thuong, Huynh Thi
Quy
Document Approval
The following signatures are required for approval of this document
Signature:
Date:
Mentor Dr. Ha Thi Nhu Hang
Signature:
Date:
Signature:
Scrum Master Nguyen Huu Thien
Date:
Signature:
Nguyen Van Minh Toi
Date:
Signature:
Team
Huynh Thi Quy Thuong
Member(s) Date:
Signature:
Ho Xuan Sang
Date:
3
Table of contents
1. Introduction 5
1.1. Purpose 5
1.2 Target 5
2. Required hardware and software 5
3. Database design decision 5
3.1. Mapping rules 5
3.2. Additional object 6
3.3 Entity relationship chart: 6
4. Relational Models 8
5. Detail of the tables 9
4
1. Introduction
1.1. Purpose
● Provides a list of preferred features, containing brief descriptions of
all the desired functionality in the project.
● Contains a complete list of all requirements under consideration,
prioritization and other key features that facilitate planning and
prioritization.
1.2 Target
Developing a website for users to get more information about events in Duy
Tan University
2. Required hardware and software
This section provides an overview of the hardware and software architecture.
Below are descriptions of the technology components of the University
Review website
Technology components of the University Review website
Attribute Description
Database MySQL
Software Laravel, VueJS
Hardware Computer
3. Database design decision

3.1. Mapping rules
When mapping entities to tables, the following rules apply:
● Entities are mapped to tables in a one-to-one manner
● Properties are mapped to columns in a one-to-one manner
● One-to-many relationships are mapped to a foreign key
5
● For 1 - 1 association: sets the primary key, one of the two relations to
another to create a foreign key.
● With 1 - n association: set the primary key, one relationship into many
relationships that create a foreign key
● With n - n link: create a sub table, then set the primary key of the two
tables to create a foreign key of the sub table.
3.2. Additional object
The following table lists the database objects (tables or columns)

that are not derived from the entity, but have been added to the
database design for the purposes listed below. This includes
intersection tables used to map many-to-many relationships.
3.3 Entity relationship chart:
Figure 01: URs entity relationship chart
6
4. Relational Models
Figure 02: URs relational model
7
5. Detail of the tables
Table 01: Admin
ID Field Datatypes Constraint Description
01 id integer Primary This field is associated with the

key NEWS table.
02 full_name string Name of the admin
03 email string Email of the admin
04 phone numeric Phone number of the admin
05 password string Password for login with account

admin
06 sex integer Gender of admin
07 is_rule integer Permission of admin
08 is_block string Display state of admin
8
Table 02 : School
01 id string Primary This field is associated with

key the Event table.
02 name string Name of school
03 email string Email of school
04 phone numeric Phone number of school
05 password string Password for login with

account school
06 is_block string Display state of school
07 is_delete string Display state delete of school
9
Table 03: User
01 id integer Primary This field is associated with the

key Participants table, the Follow
table
02 full_name string Name of user
03 email sring Email of user
04 phone numeric Phone number of user
05 sex integer Gender of user
06 dateOfBirth dateTime Date of birth of user
07 address string Address of user
08 password string Password for login with account

user
09 is_block string Display state of user
10 is_delete string Display state delete of user
10
Table 04: Event
01 id integer Primary key This field is associated with

the participants table, the
Follow table.
02 title string Title of event
03 time_start dateTime Time start of event
04 time_end dateTime Time end of event
05 slug_title string Slug title of event
06 content string Content of event
07 address string Address of event
08 quantity number Number of participants
09 img_background string Image background of event
10 img_content string Image content of event
11 img_avatar string Image avatar of event
12 schedule_detail string Schedule of event
13 location_type integer Type location of event

(Domestic, International)
14 event_type integer Type event( activities,

conferences)
15 school_id integer Foreign key This field is linked to the

School table
16 is_donate integer This event has donation

function
11
17 is_block integer Display status of event
18 is_delete integer Display status delete event
Table 05: Participants
12
ID Field Data Types Constraint Description
01 id integer Primary
key
02 event_id integer Foreign This field is linked to the

key Event table
03 user_id integer Foreign This field is linked to the

key User table
05 donate integer
13
Table 06: Follow
01 id integer Primary key
02 event_id integer Foreign key This field is linked to the Event

table
03 user_id integer Foreign key This field is linked to the User

table
14
Table 07: News
01 id Integer Primary key This field is associated with

the DetailUni table
02 title String Title of NEWS
03 slug_title String Slug title of NEWS
04 img_content String Image content of NEWS
05 img_background String Image background of NEWS
06 is_block Integer Display status of NEWS
07 admin_id Integer Foreign key This field is linked to the

Admin table
08 created_at Datetime NEWS' creation date
15
16
17

DatabaseDesign-C2SE 24-V1 0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DatabaseDesign-C2SE 24-V1 0

Uploaded by

Copyright:

Available Formats

International School

Database Design Document

Nguyen Van Minh Toi

Name Signature Date

Capstone Project 2- Mentor:

Name Signature Date

Project acronym URs

Lead Institution International School, Duy Tan University

Technology components of the University Review website

Software Laravel, VueJS

3. Database design decision

When mapping entities to tables, the following rules apply:

● Entities are mapped to tables in a one-to-one manner

● Properties are mapped to columns in a one-to-one manner

● One-to-many relationships are mapped to a foreign key

3.2. Additional object

The following table lists the database objects (tables or columns)

Figure 01: URs entity relationship chart

Figure 02: URs relational model

5. Detail of the tables

Table 01: Admin

ID Field Datatypes Constraint Description

01 id integer Primary This field is associated with the

02 full_name string Name of the admin

03 email string Email of the admin

04 phone numeric Phone number of the admin

05 password string Password for login with account

06 sex integer Gender of admin

07 is_rule integer Permission of admin

08 is_block string Display state of admin

ID Field Datatypes Constraint Description

01 id string Primary This field is associated with

02 name string Name of school

03 email string Email of school

04 phone numeric Phone number of school

05 password string Password for login with

06 is_block string Display state of school

07 is_delete string Display state delete of school

Table 03: User

ID Field Datatypes Constraint Description

01 id integer Primary This field is associated with the

02 full_name string Name of user

03 email sring Email of user

04 phone numeric Phone number of user

05 sex integer Gender of user

06 dateOfBirth dateTime Date of birth of user

07 address string Address of user

08 password string Password for login with account

09 is_block string Display state of user

10 is_delete string Display state delete of user

Table 04: Event

ID Field Datatypes Constraint Description

01 id integer Primary key This field is associated with

02 title string Title of event

03 time_start dateTime Time start of event

04 time_end dateTime Time end of event

05 slug_title string Slug title of event

06 content string Content of event

07 address string Address of event

08 quantity number Number of participants

09 img_background string Image background of event

10 img_content string Image content of event

11 img_avatar string Image avatar of event