IST365 - Project Deliverable #3
Create the corresponding relational data model by implementing the database for myFlicks.com within the course's mySQL site, linked on the course's homepage within Blackboard. Be sure to populate your tables with dummy data, providing me with the SQL scripts used to create the tables and insert the data into the actual database within a Word document. You need only to have enough data so that your queries (explained below) can be processed and not a complete product or customer inventory.
For this project, you will also create at a minimum 10 important SELECT queries that you need for the day to day management and maintenance of the operation of the site to turn raw data into useful information. In other words, these should all be SELECT statements that myFlicks.com administration or the site itself would actually process to present data to the user or management. Run the queries against your database to ensure the results are correct. Justify why each of the queries you created are important to the application in a written report. Be sure that you make the best use of the data that you can.
I will look for at least two major areas in your implementation. (a) First, I will check the structure of the tables - has entity and referential integrity been enforced and does the structure of your relational database match the ER diagram you submitted as deliverable #2 (b) most importantly, do you have queries that support the transactions associated with myFlicks.com. Remember that I will be looking for and grading 10 queries, but at the same time, I grade on a difficulty scale. Points will be awarded based on complexity, meaning I am looking for aggregate information, joins, etc. and not just statements such as select * from users, etc. As an example, you may have 10 queries, but if one is a very simple and not very useful query, it may get only 2 points (each is worth 7 with the other points given to the database's integrity structure). Also, make sure no query or report produces a null output. I must see data in the output for all queries/reports. Remember, and I reiterate, grading for the queries/reports will be based on the complexity of the queries. Simple queries are allowed, but are awarded very few points.
Creating database
4
Creating a database MyFlicks.com IST 365
December 1, 2014
The database will store information about a catalogue of movies. Information to be stored about each movie includes their titles, description, genre, artists and directors. Each artist and director may be involved in several movies. Movies will have a title and a running time (in minutes). Actors will have names associated with them and it should be possible to search the database by artist names. The same case will apply to directors and producers. Finally, in order to search the catalogue by title, each movie will have a number of keywords, which are the words in the title of the movie.Identifying Entities
The firs ...
Framing an Appropriate Research Question 6b9b26d93da94caf993c038d9efcdedb.pdf
IST365 - Project Deliverable #3Create the corresponding relation.docx
1. IST365 - Project Deliverable #3
Create the corresponding relational data model by implementing
the database for myFlicks.com within the course's mySQL site,
linked on the course's homepage within Blackboard. Be sure to
populate your tables with dummy data, providing me with the
SQL scripts used to create the tables and insert the data into the
actual database within a Word document. You need only to have
enough data so that your queries (explained below) can be
processed and not a complete product or customer inventory.
For this project, you will also create at a minimum 10 important
SELECT queries that you need for the day to day management
and maintenance of the operation of the site to turn raw data
into useful information. In other words, these should all be
SELECT statements that myFlicks.com administration or the
site itself would actually process to present data to the user or
management. Run the queries against your database to ensure
the results are correct. Justify why each of the queries you
created are important to the application in a written report. Be
sure that you make the best use of the data that you can.
I will look for at least two major areas in your implementation.
(a) First, I will check the structure of the tables - has entity and
referential integrity been enforced and does the structure of
your relational database match the ER diagram you submitted as
deliverable #2 (b) most importantly, do you have queries that
support the transactions associated with myFlicks.com.
Remember that I will be looking for and grading 10 queries, but
at the same time, I grade on a difficulty scale. Points will be
awarded based on complexity, meaning I am looking for
aggregate information, joins, etc. and not just statements such
as select * from users, etc. As an example, you may have 10
queries, but if one is a very simple and not very useful query, it
may get only 2 points (each is worth 7 with the other points
given to the database's integrity structure). Also, make sure no
query or report produces a null output. I must see data in the
2. output for all queries/reports. Remember, and I reiterate,
grading for the queries/reports will be based on the complexity
of the queries. Simple queries are allowed, but are awarded very
few points.
Creating database
4
Creating a database MyFlicks.com IST 365
December 1, 2014
The database will store information about a catalogue of
movies. Information to be stored about each movie includes
their titles, description, genre, artists and directors. Each artist
and director may be involved in several movies. Movies will
have a title and a running time (in minutes). Actors will have
names associated with them and it should be possible to search
the database by artist names. The same case will apply to
directors and producers. Finally, in order to search the
catalogue by title, each movie will have a number of keywords,
which are the words in the title of the movie.Identifying
Entities
The first step is to identify entities, attributes, and relationships
from the problem description. It is also necessary to identify the
cardinality ratios of the relationships found. For example,
Movie and Director are two entities from the description above.
Director has the attributes First Name and Last Name. There is
also a relationship between directors and movies in that
directors produce movies. This relationship is one-to-many (one
director directs many movies).
Drawing the ERD Diagram.
Having identified all the entities, it will be crucial to draw an
ERD diagram which will give a useful picture of the layout of
the database. The partial ERD below is based on the information
above on the different fields of the database.
3. Below is a list of the tables and their attributes that will be
present in the database
DATA DICTIONARY
TABLE NAME
ATTRIBUTE NAME
CONTENTS
TYPE
FORMAT
RANGE
REQUIRED
PK/FK
FK REFERENCED TABLE
MYFLICKS
USER
MOVIE_REVIEW
TVEPISODE_REVIEW
USER DETAILS
MOVIE DETAILS
TV EPISODE DETAILS
FK
FK
FK
USER ACCOUNT
MOVIE
TV EPISODE
4. USER ACCOUNT
USER_ID
USER_FIRSTNAME
USER_LASTNAME
USER_ID
USERS FIRST NAME
USERS LAST NAME
CHAR(5)
VCHAR(20)
VCHAR(20)
99999
XXXXXX
XXXXXX
10000-99999
Y
Y
Y
PK
MOVIE
MOVIE_ID
MOVIE_TITLE
MOVIE_DESCRIPTION
MOVIE_CATEGORY
MOVIE_RUNNING TIME
MOVIE_RELEASE DATE
MOVIE_DIRECTOR
MOVIE_PRODUCER
MOVIE ID
TITLE OF THE MOVIE
BRIEF DESCRIPTION OF MOVIE
CARTEGORY OF MOVIE
DURATION OF MOVIE
RELEASE DATE
MOVIE DIRECTOR
