1) Provided the following business scenario, generate a Crow’s Foot ERD utilizing a specialization hierarchy if suitable.

Tiny Hospital keeps the information on patients and the hospital rooms. The system allocates each patient a patient ID number. Additionally, the patient’s name and date of birth are stored. Some patients are resident patients (they spend at least one night in hospital) and others are outpatients (they are treated and released). Resident patients are allocated a room. Every room is recognized by a room number. The system also records the room type (private or semiprivate), and room fee. Over time, every room will have several patients that stay in it. Every resident patient will stay in only one room. Each room should have had a patient, and each resident patient should have a room.

Note that within this scenario, a specialization hierarchy is not suitable. While resident patients are an recognizable kind or type of the patient instance, there are not additional attributes which are unique to only that kind or type of the patient. Participation in a relationship which is unique to a particular kind or type of the instance is not suf?cient. Provide justi?cation for a specialization hierarchy. Indicating that only some instances will participate in the relationship is addressed by the optional participation designation. In this scenario, all the resident patients should have a room; however, not all the patients are resident patients so ROOM is optional to patient. If students ask regarding the need for an attribute to distinguish between the outpatients and resident patients, remind them that in this limited scenario the only distinction between the outpatients and resident patients is whether or not they are linked with a room. Thus, they may consider the Room_Num foreign key in PATIENT table may serve in that capacity.