final exam topic create a database to manage a game center

PROBLEM: A game center has 6 different game areas, including areas, each game area is cared for and managed by a staff member.. Each staff is responsible for selling game cards and check

VIETNAM NATIONAL UNIVERSITY

UNIVERSITY OF SOCIAL SCIENCES AND HUMANITIES

FINAL EXAM TOPIC: CREATE A DATAB ASE TO MANAGE A GAME CENTER

Lecturer: TS NGUYEN HOANG LONG

S tudent: Nguyen Thi Kim Ly

Student code: 20032748 Class: K65 Information Management

Email: kimlynguyen2312@gmail.com

Hanoi – 2023

VIETNAM NATIONAL UNIVERSITY

UNIVERSITY OF SOCIAL SCIENCES AND HUMANITIES

FINAL EXAM TOPIC: CREATE A DATAB ASE TO MANAGE A GAME CENTER

Lecturer: TS NGUYEN HOANG LONG

S tudent: Nguyen Thi Kim Ly

Student code: 20032748 Class: K65 Information Management

Email: kimlynguyen2312@gmail.com

Hanoi – 2023

PROBLEM: 4

Step 1: Analyze requirements 4

Step 2: ERD relational model 7

Step 3: Design the logic diagram 7

Step 4: Create Table/ Insert data/ Queries 10

PROBLEM:

A game center has 6 different game areas, including areas, each game area

is cared for and managed by a staff member

Each staff is responsible for selling game cards and checking customer cards

Customers need a card to enter the game area

Promotion of 50% off card price for customers who are students Card prices are only reduced when customers bring a valid student card when purchasing the card

Many game cards can have the same bill

One game card can be played in all 6 areas

The game areas are open from 9.am to 6.pm every day of the week, with no limit on how long a customer can play during the day and no limit on the number

of cards a customer can purchase in the event of a customer lost card Each game card can be used for a period of 3 months from the date of purchase

After 3 months from the date of card purchase, customers need to go to the gaming area to get another card and must pay a fee to get the card

Step 1: Analyze requirements

• Gaming_area: gaming_area_id, gaming_area_name, start_time, end_time

• Staff: staff_id, staff_name, phone_number, gaming_area_id

• Customer: customer_id, customer_name, phone_number,

student_card_id staff_, id

• Game_card: game_card_id , expiration_date, price, staff_id,

customer_id

• Bill: bill_id, customer_id, game_card_id, is_apply_voucher, total_price

• Each staff will belong to one gaming area

• Staffs will sell many game cards to many different customers

• A customer can purchase game cards multiple times

• One game card can be used in all 6 game areas in the center

Request v The center has 6 game areas

v An area maintained by 1 staff

v Staff is responsible for selling game cards to customers and give

a bill for customer (include check valid student_card_id if customer request a voucher for game card)

What types of events should the

system track?

Gaming area Customer Game card Bill

What do users want to know about

these things?

Gaming_area (gaming_area_id, gaming_area_name, start_time, end_time)

Customer (customer_id, customer_name, phone_number, student_card_id)

Game_card (game_card_id, expiration_date, price)

Bill (bill_id, total_price, is_apply_voucher)

What is the relationship between

different things?

Belong

Request v One game card can be played in 6

areas

v A customer can buy game cards multiple times (lose card)

v Customer receive bill when buy game card

v Many game cards can have the same bill

What types of events should the

system track?

Customer Game_card Bill

What do users want to know about

these things?

Customer (customer_id, customer_name, phone_number) Game_card (game_card_id, expiration_date)

Bill (bill_id, total_price, is_apply_voucher)

What is the relationship between

different things?

Buy

Step 2: ERD relational model

Step 3: Design the logic diagram

Gaming_area

Field name Data types Constraints Description

Gaming_area_name VARCHAR

(225)

Not null, Unique

The name of the area

‘8:00:00’

Area opening times

‘21:00:00’

Area closing times

Staff

Field name Data types Constraints Description

(225)

Not null The name of staff

Phone_number VARCHAR (20) Unique The phone

number of staff

Customer

Field name Data types Constraints Description

Customer_name VARCHAR

(225)

Not null The name of the

customer Phone_number VARCHAR (20) Unique The phone

number of the customer Student_card_id VARCHAR (30) Unique The student card

id of the customer

Game_card

Field name Data type Constraints Description

Experition_date DATE Not Null,

Check >

experition_date

Game card expiration date

Check > 0

Price of game card Game_card_name VARCHAR(225) Not null The name of

game card

Bill

Field name Data type Constraints Description

Is_apply_voucher BOOLEAN Check Indicates if a bill

is voucher- applied

Check > 0

Total game card price

Step 4: Create Table/ Insert data/ Queries

• Create Table

• Insert Data

• Queries