Assessment

profileSolomon Kane
BackgroundDocument-Regal_SOWweek1assesment.docx

Subject: Designing and Implementing a Movie Database

From: Regal Theaters

To: DB Solutions

We look forward to your design and implementation of a Movie Database over the next 4 weeks. As we agreed to in our Statement of Work (SOW), the following four milestones shall be accomplished:

1. Week 1 – Design the Movie Database

2. Week 2 – Prototype Demonstration (using single table queries)

3. Week 3 – Taking Queries to the Next Level (using multiple table queries)

4. Week 4 – Contract Signoff Demonstration (using advanced query techniques)

In addition, your target Database Management System shall be Oracle Express Edition (XE).

The subsequent continuation of the Regal Theaters contract with DB Solutions is contingent upon the successful completion of all tasks.

Week 1 milestone requires that you complete an Entity Relationship Diagram (ERD) of our Movie Database (the start of which is contained in a PowerPoint file). Listed below are our requirements that you will use to complete the ERD.

Movie Database Requirements

1. For each movie Regal Theaters requires that the database keep track of:

a. An ID that uniquely identifies each movie

b. Title of the movie

c. Genre of the movie

d. MPAA rating of the movie

e. Release date of the movie

f. Length of the movie in minutes

2. For each director Regal Theaters requires that the database keep track of:

a. An ID that uniquely identifies each director

b. First name of the director

c. Last name of the director

3. For each star Regal Theaters requires that the database keep track of:

a. An ID that uniquely identifies each star

b. First name of the star

c. Last name of the star

4. Table relationship information

a. There is a one-to-many relationship between the DIRECTOR table and the MOVIE table. In other words, one director can direct many movies

b. There is a many-to-many relationship between the MOVIE table and the STAR table. In other words one movie has many stars and one star can appear in many movies. To accomplish this many-to-many relationship your ERD design includes a “join” table, titled MOVIE_STAR, which joins the MOVIE table to the STAR table.

Sincerely,

Amy E. Miles

Amy Miles, CEO Regal Entertainment Group

Subject:

Designing a

nd Implementing a Movie

Database

From:

Regal Theaters

To:

DB Solutions

We look forward to your design and implementation of a Movie Database over the next 4 weeks.

As we

agreed to in our Statement of Work

(SOW)

, the following four

milestones shall be accomplished:

1.

Week 1

Design the Movie Database

2.

Week 2

Prototype Demonstration

(using single table queries)

3.

Week 3

Taking Queries to the Next Level (using multiple table queries)

4.

Week 4

Contract Signoff Demonstration

(

using

advan

ced query techniques)

In addition, your target Database Management System shall be Oracle Express Edition (XE).

The

subsequent

continuation of the Regal Theaters contract with DB Solutions is contingent upon the

successful completion of all tasks.

Week 1

milestone

requires that you complete an Entity Relationship Diagram (ERD) of our Movie

Database

(the start of which is contained in a PowerPoint file)

. Listed below are our requirements that

you will use to complete the

ERD.

Movie Database

Requirements

1.

F

or each movie Regal Theaters requires that the database keep track of:

a.

An ID that uniquely identifies each movie

b.

Title of the movie

c.

Genre of the movie

d.

MPAA rating of the movie

e.

Release date of the movie

f.

Length of the movie in minutes

2.

For each director Rega

l Theaters requires that the database keep track of:

a.

An ID that uniquely identifies each director

b.

First name of the director

c.

Last name of the director

3.

For each star Regal Theaters requires that the database keep track of:

a.

An ID that uniquely identifies

each star

b.

First name of the star

c.

Last name of the star

4.

Table relationship information

a.

There is a one

-

to

-

many relationship between the DIRECTOR table and the MOVIE table. In

other words, one director can direct many movies

Subject: Designing and Implementing a Movie Database

From: Regal Theaters

To: DB Solutions

We look forward to your design and implementation of a Movie Database over the next 4 weeks. As we

agreed to in our Statement of Work (SOW), the following four milestones shall be accomplished:

1. Week 1 – Design the Movie Database

2. Week 2 – Prototype Demonstration (using single table queries)

3. Week 3 – Taking Queries to the Next Level (using multiple table queries)

4. Week 4 – Contract Signoff Demonstration (using advanced query techniques)

In addition, your target Database Management System shall be Oracle Express Edition (XE).

The subsequent continuation of the Regal Theaters contract with DB Solutions is contingent upon the

successful completion of all tasks.

Week 1 milestone requires that you complete an Entity Relationship Diagram (ERD) of our Movie

Database (the start of which is contained in a PowerPoint file). Listed below are our requirements that

you will use to complete the ERD.

Movie Database Requirements

1. For each movie Regal Theaters requires that the database keep track of:

a. An ID that uniquely identifies each movie

b. Title of the movie

c. Genre of the movie

d. MPAA rating of the movie

e. Release date of the movie

f. Length of the movie in minutes

2. For each director Regal Theaters requires that the database keep track of:

a. An ID that uniquely identifies each director

b. First name of the director

c. Last name of the director

3. For each star Regal Theaters requires that the database keep track of:

a. An ID that uniquely identifies each star

b. First name of the star

c. Last name of the star

4. Table relationship information

a. There is a one-to-many relationship between the DIRECTOR table and the MOVIE table. In

other words, one director can direct many movies