ERD Diagrams for Player Training Session Management System

Verified

Added on 2024/07/01

AI Summary

This document presents a series of Entity-Relationship Diagrams (ERDs) designed to model a player training session management system. The ERDs are developed based on specific business rules provided by Bruce, ensuring a robust and efficient database structure. The first ERD focuses on the requirement for each player to attend all 20 training sessions, while the second ERD addresses the minimum player registration requirement for each session. The third ERD represents the final database structure, incorporating the business rules and assumptions. The document also provides detailed explanations of the relationships between entities and the cardinality of those relationships.

Contribute Materials

Your contribution can guide someone’s learning journey. Share your documents today.

The ERD diagrams are listed below according to the business rules given by the Bruce:-
1. The first business rule can be defined as the following figure:
Each player is expected to attend all 20 training sessions.
Each player has a unique player id which is connected to the training session table via the
performance table to avoid the many-to-many relationship in ERD.
2. The second business rule is defined by following ERD:
For each training session to go ahead, six or more players must register to attend it.
Each training session must consist of six or more players and those players have to
register for the training sessions through a specific registration id.

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.

💎 Get Pro

3. When the case study is described as completed and the database is prepared according to
the requirements, the following ERD is developed:
4. The assumption of business rules:
 In Player table, there is an attribute training_sessions_attended. This justifies the
business rule that every player needs to attend at least 20 sessions.
 In Training_session, there is an attribute number_of_players. This justifies the
business rule that each session needs at least 6 players to take the session forward.
 The relationship from Player to Performance is one to many, cardinality being 1:
N. According to a business rule, one player can attend many training sessions and
they would be rated by their performance. The optionality is 1: n. This indicates
that one player can attend one or more sessions. The rating is provided in the
Performance table.
 The relationship from Taining_session to Performance is one to many, cardinality
being 1: N. According to a business rule, one training session can have many
players. The optionality is 1: n.

1 out of 2

+13062052269

info@desklib.com

ERD Diagrams for Player Training Session Management System

Contribute Materials

Secure Best Marks with AI Grader

Related Documents

Player Attendance and Training Session Management System

Database Normalization and Implementation for Desklib

Major Issues in Database Design and Implementation

Deep Understanding of Relevant Subject Matter

Entity Relationship Diagram

Traffic Demerit System Case Study 2022