Office stestbiame deptCode lastName frstName tacid rank Department employs Credits Faculty sRated Major hasMajor chairs firstName Evaluation Student lastName studertid date rater rating enroll gade teaches N schedule N Class textUsed room N Textbook classNo author year section courseNo deptCode title publisher

Given the ER diagram above, answer the following questions: a. Name an entity type that has more than 2 relationships. b. Name one ket attribute and the entity type it belongs to. c. Name one one-to-one relationship and the entity types it relates. d. Name one many-to-many relationship and its entity types. e. Name one relationship attribute. f. What is the cardinality of relationship ‘employs’? g. What is the cardinality of relationship ‘textUsed’? h. Name one weak entity type i. Does it have a partial key? If yes, name it. ii. Name its identifying entity type iii. Name its identifying relationship Question 2 A bank provides services to customers. The banks is identified by its code and has a name and an address. The bank has several branches. A branch is identified by its code that is unique for a given bank. The branch name and address are also stored in the database. Customers deal with the bank through the bank branches. So, a customer belongs to a specific bank branch. Customers either open bank accounts (CURRENT, SAVINGS, etc.) or receive bank loans (DIRECT, INDIRECT, etc.) from the bank. The bank stores customer info namely: EID, name, phone, and address. The bank also keeps track of customers’ loans and accounts. Information stored about loans include loan no, amount, and type. Account information stored is account no, balance, and type. The address information stored for any entity includes street number, street name, PO Box, city, and emirate. Draw an ER diagram representing the needed database. Question 3 Consider the ER diagram below, which shows a simplified schema for an airline reservations system. Extract from the ER diagram the requirements and constraints that resulted in this schema. Try to be as precise as possible in your requirements and constraints specification.