A database system is a computer
based system, it consists of three main components. It has Front end
applications, BDMS, and the database. The database is a collection of data, has
graphs, tables and many different accessories to record information (when the
data is organized then data turns into information). In this case scenario I
will be creating a database that can handle rental transactions, recorded inventory,
and customer information. This database will use in a Video rental store.  Users without knowledge that want to
communicate with the database are known as Front-end-users. Since the databases
will be use in a daily basis by customers, Front end applications are necessary
so users can easily use the database. Back-End- users such as me and my fellow
employees, take care of the database, and connect directly with the database. They
have the right knowledge and expertise to do so.  All of these components are necessary to the video
rental database because it ensure the database is user friendly and
useable.   

The Video rental store is currently
using a paper database, everything that gets done in the store gets recorded on
paper. The store has a large number of movies, they have movies coming in and
out. The store lacks space to display every single one of them so customers
don’t get the full view of their inventory.  The store also has many old and new customers
coming in each week. The store gets new customers everyday so keeping a paper
record of every single one of them is complicated. This can create some trouble
because this paper database does not update until the end of the day, when the
store is closed. The database is going to replace does problems by providing a
computer based inventory and search system with the database. The store wants
customers to use a computer and search for their preferred movies. Since staff
members are not sure if movies are available, rented or just have been turned
in. This database is design to solve that problem because you can update tables
and records in seconds. Giving customers and employees always accurate
information.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

The database will have all previous
records of customers and can accept new records. The records will have
information of any customers that want to rent a video. It will assign them a
unique ID along with all their details. Therefore this database targets anyone
in the public. All the previous records that are transfer along with the movies
also will have a unique ID. Some key details that are incorporated in the
database that is used in the previous paper database base is:

·        
Movie Stock ID

·        
Previous Customer ID’s

·        
All previous transactions that was recorded in
paper

While creating the database 4
different tables where created to support customer, inventory and all the
rental transactions. Another table is created for the Employees, all of these
tables have a primary key. In lectures our professor said “unique keys should
have auto number so that the system generates a number for you”. All my graphs
have short text as the data type because while doing relationships, the data
types were acting up. So looking at the example database provided in the
lecture (Movie Database) I follow its example and relationships are working
fine. Then 10 queries were created, 3 were giving. One of three had to have the
following criteria: one calculate field, one sorted query, and a conditional
query. The remaining 7 were giving freedom to me, for all 7 I use two different
set of graphs. In order to view and Input user, inventory, and transactions
forms where created. One form for each tables, so in total 7 forms were
created. All of them are user friendly accepting new data and browsing the
users requested data. Also 2 Reports were created one using Customer table and
the other one show the Revenue of the movies in the database.

                All
of these components are necessary for the database to work properly. Having
these details will make sure the database is efficient, because I would be able
to hold old and many more new records. Staying up to date, using a paper
database didn’t mean quick updates in seconds, this database will fix the
problem. Responsiveness, since the rental shop lack space to show all their
movies. The database will show all of them when the user request. The design,
the database will be user and employee friendly. If customers want information
about a certain product they can find it, for employees they will have access
directly to the database is changes need to be made.  This can be changing the rental price or
adding a new movie.