(b) END USER USER INTERFACE database Fig 1 Describe the role of every component in the diagram shown in Fig 1. (c) Create an entity relationship diagram and the relational diagram to show relationship between all the tables of a database in the below given business rules. Each table must have minimum 3 attributes. i) A STUDENT can take many MODULES (in a university). Each MODULE is taken by many STUDENTS. ii) Each MODULE is taught in many Classes. Each CLASS conducts a MODULE. ABMS

(b) END USER USER INTERFACE database Fig 1 Describe the role of every component in the diagram shown in Fig 1. (c) Create an entity relationship diagram and the relational diagram to show relationship between all the tables of a database in the below given business rules. Each table must have minimum 3 attributes. i) A STUDENT can take many MODULES (in a university). Each MODULE is taken by many STUDENTS. ii) Each MODULE is taught in many Classes. Each CLASS conducts a MODULE. ABMS

Database System Concepts

7th Edition

ISBN:9780078022159

Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Chapter1: Introduction

Section: Chapter Questions

Problem 1PE

See similar textbooks

Similar questions

Design an Entity-Relationship diagram for the below environment. determine 1-Total participation.2-Partial participation Consider a MAIL_ORDER database in which employees take orders for parts from customers. The data requirements are summarized as follows: o The mail order company has employees, each identified by a unique employee number, first and last name, and Zip Code. o Each customer of the company is identified by a unique customer num, first and last name, and Zip Code. o Each part is identified by a unique part number, a part name, price, and quantity. o Each order placed by a customer is taken by an employee and is given a unique order number. Each order contains specified quantities of one or more parts. Each order has a date of receipt as well as an expected ship date. The actual ship date is also recorded.
一. Draw the E/R diagram for following database Let us design an employee database, including information about employee and department. Information about entity emp includes their empno, ename, job and salary. Entity dept has deptno, dname and location. Each employee can work only for one department and each department can hire many employees.
(a) Explain carefully four ways in which the diagram fails to model the intended world. In each case make sure you contrast the actual meaning with the intended meaning. (b) Give an entity-relationship diagram, still using two entity types, which correctly models the intended world. (c) Give a database schema (including primary keys) for the ER diagram which you have given in the previous part. (d) Is there any part of the ER diagram which is not captured in the schema? How might this aspect be captured in the final database?
Produce an entity relationship diagram for a relational database that will be able to address the case study. It is your task to design a database that will adhere to good design principles.
LOGICAL DATABASE DESIGN The above EER-Diagram represents a University Library Membership (see Diagram 5). A member can borrow as many books from the library. Derive relations for logical model from the above EER-Diagram. Please identify any primary key or foreign key in the derive relations (if applicable).
The crow's foot in a diagram a.) is only used to show N:M relationships. b.) shows the relationship between three entities. c.) indicates that more than one of that entity type can be involved in that relationship. d.) shows the minimum number of entities that can be involved in a relationship. When translating an ER model into database tables a.) each relationship is defined by a normal form. b.) each entity is represented with a table. D.) each relationship is represented with a table.
When working with database entity relationship modeling, should the cardinality between entities be translated/ read from both ends of the notation? In other words, should a relationship between entities have the ability to understood if read forwards and backwards?
Should the cardinality between entities be translated/read from both ends of the notation when dealing with database entity relationship modelling? In other words, should a relationship between things be understandable when read both forwards and backwards?
Draw an EER diagram for AIRLINE relational database. According to model, the following requirements are satisfied:The AIRLINE relational database schema shown in the above figure describes a database for airlineflight information. Each FLIGHT is identified by a Flight_number, and consists of one or moreFLIGHT_LEGs with Leg_numbers 1, 2, 3, and so on. Each FLIGHT_LEG has scheduled arrival anddeparture times, airports, and one or more LEG_INSTANCEs—one for each Date on which the flighttravels. FAREs are kept for each FLIGHT. For each FLIGHT_LEG instance, SEAT_RESERVATIONs are kept,as are the AIRPLANE used on the leg and the actual arrival and departure times and airports. AnAIRPLANE is identified by an Airplane_id and is of a particular AIRPLANE_TYPE. CAN_LAND relatesAIRPLANE_TYPEs to the AIRPORTs at which they can land. An AIRPORT is identified by an Airport_code.
Design a relational database schema from the Car Sharing IS domain class diagram. Output should look like image number 2
Design a relational database that consists of the following stages:1- Database requirements and scenarios (bonus) 2- ER- and EER diagram (at least 5 entities), must contain specialization or generalization (superclass and subclass)3- Mapping EER to Relational Model diagram4- Normalization of the relation scheme (1NF, 2NF, 3NF, and BCNF) for at least one relation (main entities)5- SQL statements to create these relations and constraints with the insertion of sample data.6- Create indexes ( for at least one table) is a bonus.
1b)By using a scenario, explain program-data dependence issue found in previous database technologies such as file-oriented database before relational database model was introduced.