IST7000 Data Management Week 2 ERD Diagram Definition

Name: JS
The entity relationship diagram is crucial to the creation of a successfully implemented
application and database. A good understanding of how to identify the components that
define the Entity Relationship Diagram is needed. Select one of the following two
scenarios and design an entity relationship diagram with the following components:
READ THIS FIRST CAREFULLY:
Identify the entities that need to be modeled
Identify the attributes that each entity will include
Identify the relationships as required.
Identify the primary keys (identifier attributes)
Identify any business rules or assumptions that are associated with your data
model
Your design MUST be in normalized to 3rd normal form.
Remove the Scenario you are NOT doing the only thing that should be
submitting is your scenario description and your ERD.
Do not use any other template or file other than this one!
DO NOT put any spaces in your entity or attribute names.
Scenario 1 Local Gym
A local gym owner wants you to design a new database to manage customer
memberships, employee schedule, training activities and training activity schedule. Each
employee will be specialized in one or more training activities. An employee also cannot
be scheduled to work for more than 12 hours consecutively. A gym member must be 18
yrs. or older and could have one or more family member on their membership plan.

For the customer, you must track their full name (First, Middle and Last Name), date
of birth, gender, gym memberships, address, phone number and email.
For the employee, you must track their full name (First, Middle and Last Name), date
of birth, gender, training specialty and work schedule.
For the training activities, you must track the name of the training, the type of training
and the days that the training occurs.
Your design will need to be normalized to 3rd normal form.
Please identify any additional information that would be necessary to support the
database design

This template is for IST.7000.HYB.B1W05.FA2016

ENTITIES:
CUSTOMER
EMPLOYEE
ADDRESS_ID
TRAINING
SCHEDULE
MEMBERSHIP
FAMILY_DETAILS
o DAYS
o
o
o
o
o
o
o

ATTRIBUTES:
Entity 1: CUSTOMERS
Attributes: customer_id, membership_id, first_name, last_name, middle_name, dob,
gender, mobile_no, email_id, membership_id, address_id, training_id
Entity 2: EMPLOYEES
Attributes: employee_id, first_name, last_name, middle_name, dob, gender, mobile_no,
home_no, address_id
Entity 3: ADDRESS
Attributes: address_id, street_name, apt_suite_no, city, state, county, zipcode
Entity 4: TRAINING
Attributes: training_id, training_name, training_type, employee_id, schedule_id
Entity 5: SCHEDULE
Attributes: schedule_id, am_hours_5_to_9, am_hours_9_to_12, pm_hours_12_to_4,
pm_hours_4_to_9, total_hours, day_id
Entity 6: MEMBERSHIP
Attributes: membership_id, member_family_name, payment_due, next_payment_date,
membership_end_date, primary_customer_id
Entity 7: FAMILY_DETAILS
Attributes: family_id, total_members, customer_id_1, customer_id_2, customer_id_3,
customer_id_4, membership_id
Entity 8: DAYS
Attributes: day_id, weekdays, weekends

This template is for IST.7000.HYB.B1W05.FA2016

Entity Relationship Diagram

Lives In

Lives In

EMPLOYEE

CUSTOMERS
ADDRESS
customer_id(PK)
first_name
last_name
middle_name
dob
gender
mobile_no
email_id
membership_id(FK
)
training_id(FK)
address_id (FK)
Belongs to

employee_id(PK)
first_name
last_name
middle_name
dob
gender
mobile_no
home_no
address_id(FK)

address_id(PK)
street_name
apt_suite_no
city
state
county
zipcode
gives
TRAINING

training_id(PK)
training_name
MEMBERSHIP training_type
employee_id(FK)
membership_id(PK)
schedule_id(FK)
member_family_name
payment_due
next_payment_date
membership_end_date
primary_customer_id(FK)

Takes

Works with

SCHEDULE
Belongs to

FAMILY_DETAILS
family_id(PK)
total_members
Works with
customer_id_1
customer_id_2
DAYS
customer_id_3
customer_id_4
day_id(PK)
membership_id(FK)
This template is for IST.7000.HYB.B1W05.FA2016
weekdays
weekends

schedule_id(PK)
am_hours_5_to_9
am_hours_9_to_12
pm_hours_12_to_4
pm_hours_4_to_9
total_hours
day_id(FK)

BUSINESS RULES:
Business Rules are considered to be data driven.

This template is for IST.7000.HYB.B1W05.FA2016