[SOLVED] CSIS 325 – Lab 2 (ER Diagrams)

Author: Client Uploads

January 7th, 2022

Using this completed instance diagram fill in the cardinality symbols for the ERD below. You will probably need to use a basic drawing tool within Word to draw the cardinalities.
In the space provided below, draw an ER diagram containing Order and Customer entities connected by a 1-M relationship from Customer to Order. The relationship should be called “Places”. Define minimum cardinalities so that an order is optional for a customer and a customer is mandatory for an Order. For the Customer entity type, define attributes as follows: CustNo (primary key), CustName, CustBalance. For the Order entity type, define attributes as follows: OrdNo (primary key), OrderDate, OrdAddress.

Use ER Assistant to draw your diagram. Copy and paste the ERD from ER Assistant into the space provided below. [Note: To receive credit for this problem, you must use ER Assistant as your drawing tool.]

Struggling to find relevant content? Order a custom essay on

[SOLVED] CSIS 325 – Lab 2 (ER Diagrams)

Let our experts save you the hassle

Order Now

In the space provided below the following ERD, transform the following M-N relationship into an associative entity type and two identifying 1-M relationships.

In the space provided below, draw a self-referencing entity type for the Employee entity type for which an employee is supervised by a maximum of one other employee and doesn’t have to be supervised by any employee at all. Conversely, an employee can supervise zero or many other employees. The attributes of the Employee entity are as follows: EmpNo (primary key), EmpName, EmpAddress.

In the space provided below, draw a generalization hierarchy containing Employee, Administrator, and Faculty entities. The Employee entity is the supertype, and the Administrator and Faculty entities are the subtypes.

The Employee entity has attributes as follows: EmpNo (primary key), EmpName, and EmpAddress.

The Administrator entity has attributes as follows: AdmTitle, AdmContractLength

The Faculty entity has attributes as follows: FacTenure, FacRank

The generalization hierarchy should be disjoint but not complete.

In the space provided below, draw an ER diagram that includes entities for Clients, Contracts, and Contacts.

Clients have the following attributes: ClientID (primary key), ClientName, ClientAddress.

Contracts have the following attributes: ContractID (primary key), ContractType, LicenseFee.

Contacts have the following attributes: ContactID (primary key), ContactName, ContactAddress.

Draw a relationship between Clients and Contracts such that a Client can be assigned to many contracts, but it can also exist without having any contracts at all in the database. Conversely, a contract can be assigned to only one client but must be assigned to a client in order to exist. Name your relationship “Signs”.

Draw a relationship between Clients and Contacts such that a client must be assigned to one and only one contact. A contact can exist in the database without being assigned to a client, but a contact can be assigned to more than one client. Name your relationship “Has”.

Identify two problems with the ER diagram below:

_________________________________________________________________________

Use the following ERD to answer the next 2 questions:

What is the primary key of the WorkHours table?