Fall 2020 MSA 8040 Project 1

ERD and Database (Tables) Creation

Objectives:
1. Identify entities, attributes, and relationships
2. Transfer business rules into database design ERD
3. Based on the ERD, create the database accordingly using SQL
Rules:
1. You need to solve the assignment on your own. There will be a severe penalty for
submitting copied answers.
2. Your answer, including a word file of the ERD and a sql script to create a database,
should be submitted through iCollege.
3. This project is due on 11:59pm Wednesday, October 14, 2020.
4. Late submission policy: Each day an assignment is late, it is marked down 20%.

Background
Luxury-Oriented Scenic Tours (LOST) provides guided tours to groups of visitors to the
Washington D.C. area. In recent years, LOST has grown quickly and is having difficulty
keeping up with all of the various information needs of the company. Please help them to design
a well-structured database LOST, so they can easily monitor the company’s performance.
The company’s operations are as follows.
1. LOST offers many different tours. For each tour, the tour name, approximate length (in
hours), and fee charged is needed. Guides are identified by an employee ID, but the system
should also record a guide’s name, home address, and date of hire. Guides take a test to be
qualified to lead specific tours. It is important to know which guides are qualified to lead
which tours and the date that they completed the qualification test for each tour. A guide
may be qualified to lead many different tours. A tour can have many different qualified
guides. New guides may or may not be qualified to lead any tours, just as a new tour may or
may not have any qualified guides.
2. Every tour must be designed to visit at least three locations. For each location, a name, type,
and official description are kept. Some locations (such as the White House) are visited by
more than one tour, while others (such as Arlington Cemetery) are visited by a single tour.
All locations are visited by at least one tour. The order in which the tour visits each location
should be tracked as well.
3. When a tour is actually given, that is referred to as an “outing.” LOST schedules outings
well in advance so they can be advertised and so employees can understand their upcoming
work schedules. A tour can have many scheduled outings, although newly designed tours
may not have any outings scheduled. Each outing is for a single tour and is scheduled for a
particular date and time. All outings must be associated with a tour. All tours at LOST are
guided tours, so a guide must be assigned to each outing. Each outing has one and only one
guide. Guides are occasionally asked to lead an outing of a tour even if they are not
officially qualified to lead that tour. Newly hired guides may not have ever been scheduled
to lead any outings. Tourists, called “clients” by LOST, pay to join a scheduled outing. For
each client, the name and telephone number are recorded. Clients may sign up to join many
different outings, and each outing can have many clients. Information is kept only on clients
 who have signed up for at least one outing, although newly scheduled outings may not have
any clients signed up yet.

Tasks:
1. Please draw an appropriate (and fully labeled) Entity Relationship Diagram, and your
ERD should contain entities, relationships, connectivities and cardinalities.
2. Further, please crease a database named LOST based on the ERD you designed in Task
1.

Criterions (100 points)

1. Your ERD must at least have the following entities: tour, guide, location, client, and
outing (8 points)
2. Each entity must be specified some appropriate attributes (8 points)
3. Each entity must have a primary key (not null but unique) (11 points)
4. Each entity may have a foreign key (8 points)
5. Composite entity must be created if the relationship is M:N (9 points)
6. Each entity should be at least connected to one entity, with a 1:M or 1:1 relationship (In
many cases, there may only have 1:M). Also, indicates whether it’s a strong relationship
(solid line) or weak relationship (dash line). (16 points)
7. Each table in your database should be consistent with your ERD, meaning it should have
a correct primary key and a foreign key(s) if needed. (40 points)

Grading Rubrics:
1. Each missing entity (-1 point)
2. Each entity without attribute(s) (-1 point)
3. Each missing or incorrect primary key (-1 point)
4. Each missing or incorrect foreign key (-1 point)
5. Each missing composite entity (or M:N relationship) (-3 points)
6. Each missing relationship (-1 point)
7. Each incorrect strong or weak relationship indictor (-1 point)
8. Each incorrect table creation (-5 points)
a. Each missing primary key (-1 point)
b. Each missing foreign key (-1 point)
c. Each missing attributes or data type (-1 point)