Topic: Relational Modelling Q1: Q2: Our work for EasyLife continues. They also run classes for their clients,

Topic: Relational Modelling

Q1:

Q2:  

Transcribed Image Text:

Our work for EasyLife continues. They also run classes for their clients, where groups of people with a similar injury do exercises together under the instruction of a physiotherapist. EasyLife need the data structures to store these classes and their participants. The participants are clients. Clients can have individual appointments - which we have already modelled - and classes or group sessions. The classes (or group sessions) have an instructor (physiotherapists Bruno or Deepika), a start time, an end time and a focus (spine, lower leg, elbow, etc. that determines the exercises). You have to create a model that enables several clients to take the same class and the same client to participate in several classes. Model the entities you think are necessary for the datastore to be able to store this scenario. Determine an appropriate primary key for all entities involved. You may use a natural or surrogate key. Comment about the assumptions for your primary key - e.g. can two spine classes run at the same time? Task: Develop a UML diagram with attributes that show which of the attributes are part of the primary key. Show the relationships between the entities you have identified. Mark the attributes which are part of the foreign key. Upload your solution. Our work for EasyLife continues. They also run classes for their clients, where groups of people with a similar injury do exercises together under the instruction of a physiotherapist. EasyLife need the data structures to store these classes and their participants. The participants are clients. Clients can have individual appointments - which we have already modelled - and classes or group sessions. The classes (or group sessions) have an instructor (physiotherapists Bruno or Deepika), a start time, an end time and a focus (spine, lower leg, elbow, etc. that determines the exercises). You have to create a model that enables several clients to take the same class and the same client to participate in several classes. Model the entities you think are necessary for the datastore to be able to store this scenario. Determine an appropriate primary key for all entities involved. You may use a natural or surrogate key. Comment about the assumptions for your primary key - e.g. can two spine classes run at the same time? Task: Develop a UML diagram with attributes that show which of the attributes are part of the primary key. Show the relationships between the entities you have identified. Mark the attributes which are part of the foreign key. Upload your solution.