Question $1($ER Model $-$ ER Diagram Design $($I$))$ Design two equivalent Entity$-$Relationship diagrams, one in Chen's notation and one in crow's foot notation,

that model a shared bicycle system and consider the requirements listed below. That means that you have to

identify and determine suitable entity sets, relationship sets, attributes, keys of entity sets $($if not specified$),$

and so on$.$ Further, add the cardinalities to the relationship sets and write down your assumptions regarding

the cardinalities if there could be a doubt.

The requirements are:

Each bicycle in the system is identified by a unique bicycle ID and includes details such as its type,

last maintenance date, and status.

Users of the system are identified by a unique user ID and include personal information such as name,

payment information, and phone number.

Stations where bicycles are docked are identified by a unique station ID and include information such

as location, capacity, and the number of available bikes.

A user can rent multiple bicycles over time

$[24$ points$]$

Design two equivalent Entity$-$Relationship diagrams, one in Chen's notation and one in crow's foot notation,

that model a hospital management system and consider the requirements listed below. That means that you

have to identify and determine suitable entity sets, relationship sets, attributes, keys of entity sets $($if not

specified$),$ and so on$.$ Further, add the cardinalities to the relationship sets and write down your assumptions

regarding the cardinalities if there could be a doubt.

The requirements are:

Each patient has a unique ID and is described by name, address, age, phone number, and date of birth.

Age is a derived attribute. A patient's address includes street, city, state, and zip code.

At least one medical record is recorded for each patient.

Doctors have their specialties, date of birth, age, and address, and treat multiple patients. Age is a

derived attribute. Their unique identifier is their name. A doctor's address includes street, city, state,

and zip code.

Nurses are also identified by their names, have specialties, and share personal details with doctors.

They provide care to various patients.

Medical records, which are distinctively identified by a record ID$,$ contain treatment details.

Appointments have a unique ID$,$ encompass date and time, and involve specific patients and doctors.

A patient can have multiple appointments.

While a doctor can attend multiple appointments, each appointment is managed by only one doctor

Nurses and doctors belong to a hospital department.

Hospital departments have by a unique ID$,$ names, functions, and a department head.

Each prescription is linked to a specific medical record. Prescriptions are detailed with medication

and dosage and have a unique ID$.$

NOTE: Use ERDPlus to draw both ER diagrams. This will help you become prepared for Exam $1$ where

we will use ERDPlus. ERDPlus allows one to export an ER diagram as an image file $($with the file ending

$.$png$)$ or as a text file in an ERDPlus specific ASCII format $($with the file ending $.$erdplus$).$ Create an

account on the ERDPlus web page to be able to store ER diagrams so that you can continue or modify them

later.

The main graphical notation supported in ERDPlus is the crow's foot notation that is a successor of

Chen's notation and has a number of syntactical $($but not semantic$)$ differences. The textbooks as well as

the instructor's special session about ERDPlus will help you understand and distinguish the two different

notations. ERDPlus also supports Chen's notation by using straight edges and labels attached to the edges.

But a first problem is that due to a conceptual error $($or an implementation error$)$ in ERDPlus, text boxes

containing labels cannot be minimized with the mouse in a manner so that they closely surround the label.

Their minimal size is relatively large so that they can superimpose other components of an ER diagram. A

way to solve this problem is to export your ER diagram into the ERDPlus specific ASCII format $($with the

file ending $.$erdplus$),$ use a text editor to change the height and width of each label that overlaps other

components of the ER diagram, delete the old file or rename the old file of the ER diagram in ERDPlus, and

import the modified file into ERDPlus. For labels such as $m,n,$ or $1,$ the value $15$ for height and width is

suitable. More precisely, for such labels, the string "width":$50,$"height":$50$ in the text file should be

replaced repeatedly by the string "width" : $15,$ "height":$15.$ A second problem is that ERDPlus is unable

to generate double lines for relationship sets since they are not needed in the crow's This statement should be distinguished from the statement

SELECT $*$