Objectives:
After completion of this assignment, you will be able to:
- Map real world scenarios into ER diagrams
- Design ER diagrams and EER
- Produce relational schemas with constraints requirements
- Use specialization and generalization techniques
Problem I:
Consider a video game store. For each game, the database contains information about title, producing company name, designer(s) name(s), version of the game, type of the game and characters in the game. For each character in the game, it contains the character's name. The video games may be available at the store in different formats. Different formats may have different prices. Each game and format has a status indicating whether it is discontinued or not.
1. Draw the ER diagram for the database described above.
2. Create a relational database schema for this model assuming
a) Each video game in the database is available at the store in exactly one format.
b) Some video games in the database may not be available at the store and others may be present in more than one format.
Provide the name of the table, primary key, and other attributes for each table in your solution. Think intelligently between various choices available to map the E/R diagram to relations, to get best design for the problem in hand. Minimize the use of NULLs. Your representation will be evaluated based on correctness and succinctness.
Problem II:
You are to design a database for an insurance company. The data will include information about customers (name, address, phone number), information about insured cars (make, model, year, vehicle-ID#, license#, insurance rate), information about insured homes (address, insured value, insurance rate), and information about claims made on insured cars and homes (date of claim, date of settlement, amount of settlement). You may assume that all insured cars and homes are owned by a single customer, but you should allow a customer to own several cars and homes. Please state any additional assumptions you make about the real world in your design.
a) Specify an entity-relationship (E/R) diagram for your database. Don't forget to underline key attributes for entity sets and include arrowheads indicating the multiplicity of relationships (with rounded arrowheads for referential integrity). If there are weak entity sets or "isa" relationships, make sure to notate them appropriately.
Attachment:- Assignment.doc