Overview of business case:
Bruce is a volunteer football (soccer) coach at XYZ United. At this stage, to announce training sessions, Bruce sends an SMS to his players. While this system works for him, it does not help him with getting accurate numbers of those who are coming to training sessions, especially when there are last minute changes. To address this problem he decided to implement a web database system. Accordingly, he hired you to design a relational database to better track and record the operational data.
NOTE: The overview of business case is included here to provide context only. For the purpose of identifying entities, attributes and relationships between entities please read the business rules and instructions for creating your ERD below.
NOTE: For guidance on how to draw an ERD based on business rules, watch this YouTube video: [login to view URL]
The business rules and instructions for creating your ERD:
Each player is expected to attend all 20 training sessions. For each training session to go ahead, six or more players must register to attend it. Every training session is identified by a training session ID. The date, time and venue are also kept in the system for each training session. Each player is identified by a player ID. For each player, the player’s name, DOB and playing position are recorded in the system. An important training session’s detail is that the system also takes note of the players who attended each training session and the rating of the performance that each player gives at the end of each training session.
Create an ERD that represents the entities, attributes, the relationships between entities, and the cardinality and optionality of each relationship that are described by this business rule.
Use [login to view URL] to create your ERD
Use Crows Foot notations
Include the PKs where appropriate
Any M:N relationship is to be resolved to a 1:M relationship
Manually drawing the ERD is NOT acceptable.