In this project you will be provided a set ofspecifications to create an entity-relationship diagram and designaccompanying table layout using sound relational modeling conceptsand practices. The relationships between the entities and theattributes for the entities will be identified and described. Thisdatabase will provide the foundation for the follow-on project. Thefollowing paragraphs provide the background and summary of thebusiness requirements. You are a database consultant with PremierSoftware, LLC and have been assigned to develop a database for theAcme video store in town. Acme has been keeping their records ofvideos and DVDs purchased from distributors and rented to customersin stacks of invoices and piles of rental forms for years. Theyhave finally decided to automate their record keeping with arelational database. You sit down with Acme to discuss theirbusiness, and watch their operation for about a week. You discoverquickly that a video and a DVD are both copies of a movie kept in aseparate plastic case that is rented out. They have several copiesof each movie they rent; therefore, there are several videos andDVDs for each movie title. You learn that in their inventory theyhave several thousand videos and DVDs, which they get wholesalefrom about a half dozen distributors. The video and DVD prices tothem are based on the quantity of their shipment and the pastbusiness they have done with each company. The price of a DVD for amovie might be different than the price of a video for the samemovie, even from the same distributor. Each distributor providesdifferent types of movies (e.g., suspense, horror, mystery, comedy,etc.). A single distributor may provide several different types ofmovies in both video and DVD format. It is possible to obtain thesame movie from multiple distributors, and at different wholesaleprices. Each video and DVD have a unique identification number thatAcme assigns in their inventory, in addition to the distributor'sserial number for the item. Each movie also has a uniqueidentification number Acme assigns in addition to the title, andany movie IDs the distributors use in their electronic catalogs.Distributors provide electronic catalogs to Acme and theinformation from these catalogs must be included in the database.Acme needs to record when a video or DVD is rented, when a video orDVD is returned, and all customer charges such as late and damagedfees, failure to rewind fees, and taxes. They need a report ofwhich videos are returned late because there are standard and latecharges. On occasion there are discount prices for certain moviesor types of movies. Customers want to rent movies based on actorsor actresses, running length, type of movie, rating, year released,the director, and the academy awards won (by the movie, the actors,the actresses and/or the directors). Customers also want to knowhow many videos they have rented in the last month, year, and soforth. Acme needs to keep only basic information on customers intheir database, such as name, address, telephone numbers, etc.There must be no limit to the number of video and/or DVD copies ofa movie that Acme can have in their inventory. Video/DVD IDnumbers, movie ID numbers, and distributor ID numbers for videos,DVDs, and movies are all different. Also, each movie must be ableto have an unlimited number of actors, actresses, directors, andacademy awards (i.e., Oscars). Other types of awards (e.g., GoldenGlobe, People's Choice, etc.) are not of interest for thisapplication. The rental of equipment, sale of videos, DVDs,popcorn, etc., is not to be kept in the database.

Using this information, you should:

1. Determine and list your entities. Then describe fullythe relationships between entities via pairs of sentences thatindicate the two components of the total relationship in bothdirections between the entities. Relationships may be unary,binary, or ternary with respect to entities. You should not haveany many-to-many relationships.

2. Begin the database logical design by identifying theentities, relationships between entities, and entities' attributesas we have done in this course. Use the same entity/relationshipdiagram (ERD) notation as used in class for entities, attributes,and relationships. Sketch your ERD by hand or a drawing program(e.g., Visio, PPT, SQL Modeler …) on one single 8-1/2\" x 11\" page(8-1/2\" x 14\" maximum), labeled \"Acme Video Store Database E/RDiagram.\" Your ERD should not have any many-to-many relationshipsbetween entities. Make sure that all relationships between entitiesare one-to-many to facilitate the construction of relationaldatabase tables.

3. Complete the logical database design and start thephysical database design by creating metadata (i.e. documentation)that describes the table(s) created from each entity and thecolumn(s) created from each attribute in the ERD. Attributes shouldbe self-describing. Particular attention will be given to theproper specification of all primary key (via \"PK\") and foreign key(via \"FK\") columns in the table layouts. These should match yourERD exactly. Begin these descriptions on a page labeled \"ProposedDatabase Tables and Columns based on E/R Diagram.\" All tables mustbe 3rd Normal Form. Indicate any and all assumptions that weremade.

PLEASE ANSWER THIS QUESTION: I WILL APPRECIATEIT