This relates to Database Systems.
Problenm You got an assignment from SimpleFlix, a new online video rental company who are designing their databases. The company has data about movies, customers, rentals, reviewers, reviews. The database needs to store the following information. A movie has a unique movie id, title, year, genre, and duration. A customer has name, a unique email, and credit. Customers rent movies (either a DVD or a streaming video); customers may rent many movies, anda movie may be rented by many customers; each rental has a start date and a return date. For streaming rental, it also records how many times the movie can be watched (single watch or unlimited) A reviewer is a customer, and has a reputation attribute. A review has a rating, a date, and text (content). Each review is uniquely identified by the movie it is reviewing, and by the reviewer who wrote it. A reviewer may endorse another reviewer for a review that the latter wrote. Reviewer X can endorse reviewer Y many times, but only once for a given review of Y. The "star count" of each such endorsement is recorded. Customers may have family accounts. One customer may belong to at most one family account. The family accounts have a lead member, who uniquely identifies such an account. Some movies to be released soon are listed as "upcoming". Customers can book The time of bookmark is recorded. mark such movies. If you think some aspects of the above are unclear, feel free to make additional, reasonable assumptions, but state them clearly in your answer. Also, keep in mind that there is no single "correc" design; if you think you are making a non-obvious design decision, please explain it briefly (a) Design an E/R diagram for this database. Very briefly explain the intuitive meaning of any entity and relationship sets as needed. Do not forget to indicate keys and multiplicity of relationships, as well as ISA relationships and weak entity sets (if any), using appropriate notation. (b) Design a relational schema for this database. (You can start by translating the E/R design.) You may ignore attribute types, and you do not need to show any sample data. Indicate all keys and non-trivial functional dependencies in the schema. Check if the schema is in BCNF. If not, decompose the schema into BCNF BCNF - Bovce-Codd Normal Form Problenm You got an assignment from SimpleFlix, a new online video rental company who are designing their databases. The company has data about movies, customers, rentals, reviewers, reviews. The database needs to store the following information. A movie has a unique movie id, title, year, genre, and duration. A customer has name, a unique email, and credit. Customers rent movies (either a DVD or a streaming video); customers may rent many movies, anda movie may be rented by many customers; each rental has a start date and a return date. For streaming rental, it also records how many times the movie can be watched (single watch or unlimited) A reviewer is a customer, and has a reputation attribute. A review has a rating, a date, and text (content). Each review is uniquely identified by the movie it is reviewing, and by the reviewer who wrote it. A reviewer may endorse another reviewer for a review that the latter wrote. Reviewer X can endorse reviewer Y many times, but only once for a given review of Y. The "star count" of each such endorsement is recorded. Customers may have family accounts. One customer may belong to at most one family account. The family accounts have a lead member, who uniquely identifies such an account. Some movies to be released soon are listed as "upcoming". Customers can book The time of bookmark is recorded. mark such movies. If you think some aspects of the above are unclear, feel free to make additional, reasonable assumptions, but state them clearly in your answer. Also, keep in mind that there is no single "correc" design; if you think you are making a non-obvious design decision, please explain it briefly (a) Design an E/R diagram for this database. Very briefly explain the intuitive meaning of any entity and relationship sets as needed. Do not forget to indicate keys and multiplicity of relationships, as well as ISA relationships and weak entity sets (if any), using appropriate notation. (b) Design a relational schema for this database. (You can start by translating the E/R design.) You may ignore attribute types, and you do not need to show any sample data. Indicate all keys and non-trivial functional dependencies in the schema. Check if the schema is in BCNF. If not, decompose the schema into BCNF BCNF - Bovce-Codd Normal Form
