Database Design for Tennis Match: A Detailed Report

This report details the design and implementation of a database system for managing tennis match information. It begins with an introduction to database management systems, emphasizing their role in organizing and securing data. The report then delves into the specifics of the tennis match database, covering key aspects such as ER diagrams to illustrate relationships between entities like matches, players, organizers, and referees. It then details the normalization process, explaining 1NF, 2NF, and 3NF to ensure data integrity and reduce redundancy. The implementation section showcases the database tables for various entities including match, organizer, player, round, staff, student and team with their attributes. Finally, the report addresses several functional requirements, including queries to determine match winners, sort teams by score, generate referee reports, and provide player lists. The conclusion summarizes the successful design of an effective and efficient database system for managing tennis match data.

Introduction to database management
1

Contents
INTRODUCTION...........................................................................................................................................3
Part 1.......................................................................................................................................................3
Part 2.....................................................................................................................................................10
Part 3.....................................................................................................................................................16
CONCLUSION.............................................................................................................................................26
2

INTRODUCTION
Database management system is process for collecting the information and data of
particular organization as well as institutes. Database is a technique to update, delete, insert and
retrieve data in effective manner. It also stores information with full of security and privacy. This
report will describe the database of tennis match that collect all information regarding the
tournament and players those who is participating in the match.
Part 1
Design database applications
ER Diagrams:
Figure: 1
ER diagram is consisting of relationship between entities and attributes. This diagram should be
relationship among them. Entity relationship diagram is a graphical representation that allows to
design effective and efficient database system. According to figure: 1 , they have different
entities and attributes used in database implementations.
For Example-
Entity-
Match
3

Attributes-
match_id
match_date
match_time
match_score
match_refere
Entity-
Player
Attributes-
player_id
player_name
player_email
player_contact no
Entity-
organizer
Attributes-
org_id
org_name
org_email address
org_contact no
Entity-
Leader
Attributes-
4

Leader_id
Leader_name
Leader_contact no
Leader_email address
Entity-
Student
Attributes-
Student_id
Student_name
Student_contact no
Student_email address
Entity-
Staff
Attributes-
Staff_id
Staff_name
Staff_contact no
Staff_email
Entity-
Round
Attributes-
Round_id
Round_type
5

Entity-
Team
Attributes-
Team_id
Team_name
Entity-
Winner
Attributes
Team_id
Team_name
Entity – This is a real world object that performed different operations in database system
Attributes- attributes is representing the actual properties of particular entity in database system.
Normalization: - normalization is a technique which help for designing database tables and
organize into proper manner. This technique is also useful for reduce the data dependencies and reduce
redundancy data.
1NF(Normal Form) :
 Each and Every table contain single value in database tables.
 Each record need to be unique and specific.
6

s.
This table shows 1NF normal form because this database table contain all information of
staff and they contain unique and single value
2NF(Normal Form):
 Single column has primary key in tables.
 1 NF forms.
3NF(Normal Form):
 This normal form doesn’t have any transitive functional dependencies.
7


8


Both tables contain match_id, it means that could modify to shows only match, player
information in 3rd tables.
Match_id can be shown as a functional data dependency in the database tables.
9

Part 2
Database Implementations:
Match table
Figure 2.1
Figure: 2.2
10

Figure 2.3
11

Organizer table
Figure: 2.4
Player table
Figure: 2.5
12