Relationship type: 1:M
Explanation: business rules state, “A patient can schedule many appointments with one or more nutritionist at Vitality”. The PATIENT entity is on the “one” side of the relationship and the APPOINTMENT entity is on the “many” side of the relationship.
Relationship participation: mandatory on the “one” side of the relationship and optional on the “many” side of the relationship.
Explanation: The PATIENT entity is mandatory in the relationship because “A patient can schedule many appointments with one or more nutritionist at Vitality”. The APPOINTMENT entity is optional in the relationship because “A patient can schedule many appointments with one or more nutritionist at Vitality”, …show more content…
The primary key is APP_ID for the entity APPOINTMENT. The primary key for the parent entity PATIENT is PAT_ID. PAT_ID is considered a foreign key and not part of the primary key for APPOINTMENT.
Relationship: NUTRITIONIST “consults” APPOINTMENT
Relationship type: 1:M
Explanation: business rules state, “A nutritionist can accept appointments with many patients. Each appointment made with only 1 nutritionist”. The NUTRITIONIST entity is on the “one” side of the relationship and the APPOINTMENT entity is on the “many” side of the relationship.
Relationship participation: mandatory on the “one” side of the relationship and optional on the “many” side of the relationship.
Explanation: The NUTRITIONIST entity is mandatory in the relationship because “A nutritionist can accept appointments with many patients. Each appointment made with only 1 nutritionist”. The APPOINTMENT entity is optional in the relationship because “A nutritionist can accept appointments with many patients. Each appointment made with only 1 nutritionist”, so an appointment could not be accepted at all by a …show more content…
However each recommended nutrition plan is made with only one nutritionist for one patient at a time”. The PATIENT entity is on the “one” side of the relationship and the NUTRITION PLAN entity is on the “many” side of the relationship.
Relationship participation: mandatory on the “one” side of the relationship and optional on the “many” side of the relationship.
Explanation: The PATIENT entity is mandatory in the relationship because “The patient can receive many different nutrition plans. However each recommended nutrition plan is made with only one nutritionist for one patient at a time”. The NUTRITION PLAN entity is optional in the relationship because “However each recommended nutrition plan is made with only one nutritionist for one patient at a time”, which means an occurrence of a nutrition plan only happens if a nutritionist recommends one and if patient chooses to receive it. Cardinality: the cardinality of PATIENT is (1, 1) the cardinality of NUTRITION PLAN is (0, M)
Relationship strength: