Database Design Project: Football Match Management

Desklib provides solved assignments and past papers to help students succeed.

Contents
ENTITY RELATIONSHIP DATABASE.......................................................................................2
References........................................................................................................................................4

ENTITY RELATIONSHIP DATABASE
The Entity Relationship diagram of the football match management system consists of the
different entities in order to manage the overall football match. This diagram states the
relationships among the different entities of the football match. The football match includes the
different entities and each of the entity must consist of the different attributes which are
necessary in the monitoring of the match. This system manages the overall entities which are
associated with the match in order to manage the overall football match of the different teams
this system has been designed. The ER diagram shows the different entities, their attributes and
their relationship with each other. Which is much more helpful in managing the overall football
match. These entities and their sub entities have been explained below.
 Player: the player is a unique entity who plays football in the field. The player is having
the different attributes also. These attributes are used to define the player. The player
entity consists of the different unique classes which are used to keep the record of the
player in the system who are playing the match like player name, mobile no., ID, Match
ID, Player’s date of birth and the position of the player in the team. These details are
necessary to keep the player record in the system.
 Match: another entity is the match the system might consists of each and every details of
the match in order to make the team ready for the match. The entity match consists of the
different details which are to be stored in the system they are venue of the match, date of

the match, opposition team, ID of the match and the name of the teams who are playing
the match. The entity player is totally dependent on the match.
 Match score: the match score entity is used to record the different scores which are being
achieved on time in order to maintain the score of the match timely. The match score is
used to declare the winner of the match also. This entity consists of different sub classes
they are match No., total yellow cards given to a particular team, total red cards given to
the team, total goals achieved by the team for maintaining the scorecard in order to
declare the winner. This entity is totally dependent on the match.
 Performance chart: this entity of the diagram consists of the performance records of the
different teams who are playing the match. The performance chart shows the
performance of the team in the match whether it is negative or positive. The performance
chart also helps the teams in improvising their performance in other matches by
analyzing. The entity consists of some attributes they are Goals which are scored by the
team during the match. Another attribute is ID of the match which is necessary to identify
the performance in the particular match. Another attribute consists of the rating of the
match and team according to their performance. This entity is totally dependent on the
match entity.

References
Al-Masree, H. K. (2015). Extracting Entity Relationship Diagram (ERD) from relational
database schema. International Journal of Database Theory and Application, 8(3), 15-26.
Zhang, F., Ma, Z. M., & Cheng, J. (2016). Enhanced entity-relationship modeling with
description logic. Knowledge-Based Systems, 93, 12-32.