ER diagram -- 2
Budget: $10 – $30 USD
Case #1:
Create the ER diagram for the following requirements and map it to relational model. Consider the participation (total/partial):
Danube keeps track of products, invoices, customers and cashiers. Products have unique code, unique name, price and expire date. Danube stores for each customer a unique number, name and mobile number. For each cashier, Danube stores their SSN, name, salary, age and address. There is a unique code for invoices, issue date, customer name, cashier name and the products customer purchased with quantity purchased.
Case #2:
Create the ER diagram for the following requirements and map it to relational model. Consider the participation (total/partial):
A museum owns many works of art. Each work of art is described by an item code (identifier), title, type, and size; size is further composed of height, width, and weight. A work of art is developed by an artist, but the artist for some works is unknown. An artist is described by an artist ID (identifier), name, date of birth, and date of death (which is null for still living artists). Only data about artists for works currently owned by the museum are kept in the database. At any point in time, a work of art is either on display at the museum, held in storage, away from the museum as part of a traveling show, or on loan to another gallery. If on display at the museum, a work of art is also described by its location within the museum. A traveling show is described by a show ID (identifier), the city in which the show is currently appearing, and the start and end dates of the show. Many of the museum works may be part of a given show, and only active shows with at least one museum work of art need be represented in the database. Finally, another gallery is described by a gallery ID (identifier), name, and city. The museum wants to retain a complete history of loaning a work of art to other galleries, and each time a work is loaned, the museum wants to know the date the work was loaned and the date it was returned. As you develop the ERD for this problem, follow good data naming guidelines
i will upload an example
Create the ER diagram for the following requirements and map it to relational model. Consider the participation (total/partial):
Danube keeps track of products, invoices, customers and cashiers. Products have unique code, unique name, price and expire date. Danube stores for each customer a unique number, name and mobile number. For each cashier, Danube stores their SSN, name, salary, age and address. There is a unique code for invoices, issue date, customer name, cashier name and the products customer purchased with quantity purchased.
Case #2:
Create the ER diagram for the following requirements and map it to relational model. Consider the participation (total/partial):
A museum owns many works of art. Each work of art is described by an item code (identifier), title, type, and size; size is further composed of height, width, and weight. A work of art is developed by an artist, but the artist for some works is unknown. An artist is described by an artist ID (identifier), name, date of birth, and date of death (which is null for still living artists). Only data about artists for works currently owned by the museum are kept in the database. At any point in time, a work of art is either on display at the museum, held in storage, away from the museum as part of a traveling show, or on loan to another gallery. If on display at the museum, a work of art is also described by its location within the museum. A traveling show is described by a show ID (identifier), the city in which the show is currently appearing, and the start and end dates of the show. Many of the museum works may be part of a given show, and only active shows with at least one museum work of art need be represented in the database. Finally, another gallery is described by a gallery ID (identifier), name, and city. The museum wants to retain a complete history of loaning a work of art to other galleries, and each time a work is loaned, the museum wants to know the date the work was loaned and the date it was returned. As you develop the ERD for this problem, follow good data naming guidelines
i will upload an example
Related categories:
Database Programming
Database Development
Relational Databases
Database Design
Database Management