Lecture 2.5 ER Diagram and practice in DB.pptx
- 2. Activity 1: Draw an entity relationship diagram for the given senario. Mention keys, cardinality ratios and participation with proper notation. State assumption if any. Please note that after solving this activity there is going to be a class participation activity. Please pay attention and solve this activity with me step by step for good practice .
- 3. Departmental store database A store wants to keep track of all its musical albums. 1. Musical album have a title, price , a unique identifier as albumId 2. There are artists who create albums. We save artists name and CNIC for our record. 3. One artist can create multiple albums. But one album can only belong to a single artist. 4. One album can be of a single genre. 5. Genre has genereID , name, description. 6. Multiple albums can have a same genre.
- 4. Step 1: find all entities and their attributes. 1. Musical album have a title, price , a unique identifier as albumId 2. There are artists who create albums. We save artists name and CNIC for our record. 3. One artist can create multiple albums. But one album can only belong to a single artist. 4. One album can be of a single genre. 5. Genre has genereID , name, description. 6. Multiple albums can have a same genre.
- 5. Step 1: find all entities and their attributes. 1. Musical album have a title, price , a unique identifier as albumId 2. There are artists who create albums. We save artists name and CNIC for our record. 3. One artist can create multiple albums. But one album can only belong to a single artist. 4. One album can be of a single genre. 5. Genre has genereID , name, description. 6. Multiple albums can have a same genre. Album albumid Title Price
- 6. Step 1: find all entities and their attributes. 1. Musical album have a title, price , a unique identifier as albumId 2. There are artists who create albums. We save artists name and CNIC for our record. 3. One artist can create multiple albums. But one album can only belong to a single artist. 4. One album can be of a single genre. 5. Genre has genereID , name, description. 6. Multiple albums can have a same genre.
- 7. Step 1: find all entities and their attributes. 1. Musical album have a title, price , a unique identifier as albumId 2. There are artists who create albums. We save artists name and CNIC for our record. 3. One artist can create multiple albums. But one album can only belong to a single artist. 4. One album can be of a single genre. 5. Genre has genereID , name, description. 6. Multiple albums can have a same genre. Album albumid Title Price Artists CNIC Nam e
- 8. Step 2: find all entities and their attributes. + relationship 1. Musical album have a title, price , a unique identifier as albumId 2. There are artists who create albums. We save artists name and CNIC for our record. 3. One artist can create multiple albums. But one album can only belong to a single artist. 4. One album can be of a single genre. 5. Genre has genereID , name, description. 6. Multiple albums can have a same genre. Album albumid Title Price Artists CNIC Nam e Creat es
- 9. Step 2: find all entities and their attributes. + relationship 1. Musical album have a title, price , a unique identifier as albumId 2. There are artists who create albums. We save artists name and CNIC for our record. 3. One artist can create multiple albums. But one album can only belong to a single artist. 4. One album can be of a single genre. 5. Genre has genereID , name, description. 6. Multiple albums can have a same genre. Album albumid Title Price Artists CNIC Nam e Creat es
- 10. Step 2: find all entities and their attributes. + relationship 1. Musical album have a title, price , a unique identifier as albumId 2. There are artists who create albums. We save artists name and CNIC for our record. 3. One artist can create multiple albums. But one album can only belong to a single artist. 4. One album can be of a single genre. 5. Genre has genereID , name, description. 6. Multiple albums can have a same genre. Album albumid Title Price Artists CNIC Nam e Creat es 1 M
- 11. Step 2: find all entities and their attributes. + Relationship 1. Musical album have a title, price , a unique identifier as albumId 2. There are artists who create albums. We save artists name and CNIC for our record. 3. One artist can create multiple albums. But one album can only belong to a single artist. 4. One album can be of a single genre. 5. Genre has genereID , name, description. 6. Multiple albums can have a same genre. Album albumid Title Price Artists CNIC Nam e Creat es 1 M
- 12. Step 2: find all entities and their attributes. + relationship 1. Musical album have a title, price , a unique identifier as albumId 2. There are artists who create albums. We save artists name and CNIC for our record. 3. One artist can create multiple albums. But one album can only belong to a single artist. 4. One album can be of a single genre. 5. Genre has genereID , name, description. 6. Multiple albums can have a same genre. Album albumid Title Price Artists CNIC Nam e Creat es 1 M Genre genreid nam e descriptio n Has 1 M
- 13. Step 3: find all entities and their attributes. + relationship + participation 1. Musical album have a title, price , a unique identifier as albumId 2. There are artists who create albums. We save artists name and CNIC for our record. 3. One artist can create multiple albums. But one album can only belong to a single artist. 4. One album can be of a single genre. 5. Genre has genereID , name, description. 6. Multiple albums can have a same genre. Assumption1 : album cannot be created without artist. But artist can exist without launching an album. Assumption 2: album will have genre but there is possibility that genre exists but there is not album on that genre. Album albumid Title Price Artists CNIC Nam e Creat es 1 M Genre genreid nam e descriptio n Has 1 M
- 14. Activity # 2
- 15. Activity # 2
- 22. Activity # 2 Draw an entity relationship diagram for the given senario. Mention keys, cardinality ratios and participation with proper notation. State assumption if any. . Consider a MOVIEdatabase in which data is recorded about the movie industry.The data requirements are summarized as follows: Each movie is identified by title and year of release. Each movie has a length in minutes. Each has a production company, and each is classified under one or more genres (such as horror, action, drama, and so forth). Each movie has one or more directors and one or more actors appear in it.Each movie also has a plot outline.Finally,each movie has zero or more quotable quotes, each of which is spoken by a particular actor appearing in the movie. Actors are identified by name and date of birth and appear in one or more movies.Each actor has a role in the movie. Directors are also identified by name and date of birth and direct one or more movies.It is possible for a director to act in a movie (including one that he or she may also direct). Production companies are identified by name and each has an address.A production company produces one or more movies.
- 23. Activity # 3 Company database The company is organized into departments. Each department has a unique name, a unique number, and a particular employee who manages the department. We keep track of the start date when that employee began managing the department. A department may have several locations. A department controls a number of projects, each of which has a unique name, a unique number, and a single location. We store each employee’s name, Social Security number,2 address, salary, gender , and birth date. An employee is assigned to one department, but may work on several projects, which are not necessarily controlled by the same department. We keep track of the current number of hours per week that an employee works on each project. We also keep track of the direct supervisor of each employee (who is another employee). We want to keep track of the dependents of each employee for insurance purposes. We keep each dependent’s first name, gender, birth date, and relationship to the employee. We only need the data of dependent till employee will work for us.
- 25. Exercise # 4 A manufacturing company produces products. The following product information is stored: product name, product ID and quantity on hand. These products are made up of many components. Each component can be supplied by one or more suppliers. The following component information is kept: component ID, name, description, suppliers who supply them, and products in which they are used. Use Figure B.1 for this exercise. Create an ERD to show how you would track this information. Show entity names, primary keys, attributes for each entity, relationships between the entities and cardinality. Assumptions • A supplier can exist without providing components. • A component does not have to be associated with a supplier. • A component does not have to be associated with a product. Not all components are used in products. • A product cannot exist without components.