Scribd
Upload
4 views5 pages

description

The document outlines the need for a robust database system for Amazon's movie and film inventory to improve data organization, user interaction, and transaction management. It highlights current challenges such as inconsistent metadata and tracking issues, while proposing a structured database to enhance data retrieval and analytics. Additionally, it details the logical scheme and attributes of various tables necessary for managing movies, formats, ratings, directors, actors, categories, and orders.

Uploaded by

darxan.1512
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
4 views5 pages

description

The document outlines the need for a robust database system for Amazon's movie and film inventory to improve data organization, user interaction, and transaction management. It highlights current challenges such as inconsistent metadata and tracking issues, while proposing a structured database to enhance data retrieval and analytics. Additionally, it details the logical scheme and attributes of various tables necessary for managing movies, formats, ratings, directors, actors, categories, and orders.

Uploaded by

darxan.1512
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Database Description

Amazon Movies and Films

This document contains privileged and/or confidential information and may not be
Legal Notice: disclosed, distributed or reproduced without the prior written permission of
EPAM®.
Amazon Movies and Films

CONTENTS
1 BUSINESS DESCRIPTION.................................................................................................... 3
1.1 Business background....................................................................................................... 3
1.2 Problems. Current Situation............................................................................................... 3
1.3 The benefits of implementing a database. Project Vision............................................................3
2 MODEL DESCRIPTION........................................................................................................ 4
2.1 Definitions & Acronyms................................................................................................... 4
2.2 Logical Scheme.............................................................................................................. 4
2.3 Objects........................................................................................................................ 5

Practice Task for ITPU “Database” Course 2


Amazon Movies and Films

1 BUSINESS DESCRIPTION
1.1 BUSINESS BACKGROUND
Amazon provides a vast collection of movies and films available for streaming and purchase.
To efficiently manage its movie inventory, user interactions, transactions, and reviews, a
robust database system is required. This database will store movie details, genres, ratings,
user reviews, purchase history, and watchlists. The system ensures smooth user experience
and data integrity across different business operations.

1.2 PROBLEMS. CURRENT SITUATION


Currently, managing movie-related data poses several challenges:
• Movie metadata, such as director information and genres, is scattered and
inconsistent.
• User reviews are difficult to track, leading to problems in analyzing customer
feedback.
• There is no structured way to store movie formats and ratings efficiently.
• The system does not adequately handle many-to-many relationships such as movies
and actors.
• There is a need for a seamless way to track purchases and watchlists.

1.3 THE BENEFITS OF IMPLEMENTING A DATABASE. PROJECT VISION


Implementing a well-structured database will:
• Improve data organization and retrieval for movies, users, and transactions.
• Allow easy tracking of customer reviews, purchases, and watchlists.
• Enhance relationships between entities such as movies, actors, and directors.
• Enable accurate data reporting and analytics for user behavior and movie popularity.
• Provide scalability to accommodate an expanding collection of movies and users.

2 MODEL DESCRIPTION
2.1 DEFINITIONS & ACRONYMS
• INT: Integer, a data type for whole numbers.
• VARCHAR: Variable-length character string.
• DECIMAL: Fixed-point numeric type for currency values.
• DATE: Stores date values in YYYY-MM-DD format.
• TEXT: Large variable-length string for descriptions and reviews.

2.2 LOGICAL SCHEME

Practice Task for ITPU “Database” Course 3


Amazon Movies and Films

2.3 OBJECTS
Table Descriptions and Attributes:

Movies Table Stores details about movies available in the system

• movie_id (INT, PK, AUTO_INCREMENT) - Unique identifier for each movie.


• title (VARCHAR(255), NOT NULL) - Title of the movie.
• release_year (INT, NOT NULL) - Year of release.
• format_id (INT, FK) - Reference to the movie format.
• rating_id (INT, FK) - Reference to the movie’s rating.
• director_id (INT, FK) - Reference to the movie’s director.
• price (DECIMAL(5,2)) - Price for purchasing or renting the movie.

Formats Table Stores the different formats in which movies are available.
• format_id (INT, PK, AUTO_INCREMENT) - Unique identifier for each format.
• format_name (VARCHAR(50), UNIQUE, NOT NULL) - Name of the format (e.g., Blu-ray,
Digital, DVD).

Ratings Table Stores user ratings and MPAA ratings for movies.
• rating_id (INT, PK, AUTO_INCREMENT) - Unique identifier for each rating.
• movie_rating (DECIMAL(2,1), NOT NULL) - Average user rating.
• no_of_ratings (INT, NOT NULL) - Total number of user ratings.

Practice Task for ITPU “Database” Course 4


Amazon Movies and Films

• mpaa_rating (VARCHAR(10)) - MPAA rating (e.g., PG, R, PG-13).

Directors Table Stores details about movie directors.


• director_id (INT, PK, AUTO_INCREMENT) - Unique identifier for each director.
• director_name (VARCHAR(255), UNIQUE, NOT NULL) - Name of the director.

Actors Table Stores details about actors.


• actor_id (INT, PK, AUTO_INCREMENT) - Unique identifier for each actor.
• actor_name (VARCHAR(255), UNIQUE, NOT NULL) - Name of the actor.

MovieActors Table Stores the many-to-many relationship between Movies and Actors.
• movie_id (INT, FK, ON DELETE CASCADE) - Reference to the movie.
• actor_id (INT, FK, ON DELETE CASCADE) - Reference to the actor.
• Primary Key: (movie_id, actor_id).

Categories Table Stores different movie categories.


• category_id (INT, PK, AUTO_INCREMENT) - Unique identifier for each category.
• category_name (VARCHAR(100), UNIQUE, NOT NULL) - Name of the category
(e.g., Action, Comedy).

MovieCategories Table Handles the many-to-many relationship between Movies and


Categories.
• movie_id (INT, FK, ON DELETE CASCADE) - Reference to the movie.
• category_id (INT, FK, ON DELETE CASCADE) - Reference to the category.
• Primary Key: (movie_id, category_id).

Orders Table Tracks purchases made by users.


• order_id (INT, PK, AUTO_INCREMENT) - Unique identifier for each order.
• order_date (DATETIME, DEFAULT CURRENT_TIMESTAMP) - Date of the order.

OrderDetails Table Handles the many-to-many relationship between Orders and Movies.
• order_id (INT, FK, ON DELETE CASCADE) - Reference to the order.
• movie_id (INT, FK, ON DELETE CASCADE) - Reference to the movie.
• Primary Key: (order_id, movie_id).

Relationships and Constraints


• Movies → Formats (each movie has one format).
• Movies → Ratings (each movie has one MPAA rating and user rating).
• Movies → Directors (each movie has one director).
• Movies ↔ Actors (via MovieActors table).
• Movies ↔ Categories (via MovieCategories table).
• Orders ↔ Movies (via OrderDetails table).

Practice Task for ITPU “Database” Course 5

You might also like