[Exercise 3] 1 marks Create a Crow's Foot ERD for one database to be used by...

 

Transcribed Image Text:

[Exercise 3] 1 marks Create a Crow's Foot ERD for one database to be used by one regional association of junior sport teams, using the following business rules. - - - - A Team may or may not have a Player A Player must belong to a Team A Team may have many Players A Player has only one Team A Team may or may not have a Coach A Coach must have a Team A Team may have many Coaches A Coach has only one Team A Player must have a Parent A Parent must have a Player A Player may have up to 2 Parents A Parent may have many Players Note for Exercise 3 You must notice that you will be able to decide optionality (optional or mandatory) or cardinality (1:1, 1:M, or M:N) for each relationship easily, because business rules provided here are clear enough to make decision of your design choice. This means you do not need to make your own assumptions to make decision on all of relationships which will be included in your ERD. About attributes to be included for each entity, the business rules provided here may not give you clear ideas enough to decide. However, try to include at least two (reasonable and meaningful) attributes in each entity in addition to the essential attributes like PK or FKs. [Exercise 3] 1 marks Create a Crow's Foot ERD for one database to be used by one regional association of junior sport teams, using the following business rules. - - - - A Team may or may not have a Player A Player must belong to a Team A Team may have many Players A Player has only one Team A Team may or may not have a Coach A Coach must have a Team A Team may have many Coaches A Coach has only one Team A Player must have a Parent A Parent must have a Player A Player may have up to 2 Parents A Parent may have many Players Note for Exercise 3 You must notice that you will be able to decide optionality (optional or mandatory) or cardinality (1:1, 1:M, or M:N) for each relationship easily, because business rules provided here are clear enough to make decision of your design choice. This means you do not need to make your own assumptions to make decision on all of relationships which will be included in your ERD. About attributes to be included for each entity, the business rules provided here may not give you clear ideas enough to decide. However, try to include at least two (reasonable and meaningful) attributes in each entity in addition to the essential attributes like PK or FKs.