SPORTS TOURNOMENT MANAGEMENT SYSTEM

Submitted to the

Department of Master of Computer Applications in

Partial fulfilment of the requirements
for the

Course: Object Oriented Modeling and Design Patterns

Course code: MCA51

by

SANJAY M
1MY19MCA15

Department of Master of Computer Applications

Ramaiah Institute of Technology
(Autonomous Institute, Affiliated to VTU)
Bangalore – 54
2022
 RAMAIAH INSTITUTE OF TECHNOLOGY
(Autonomous Institute, Affiliated to VTU)
Bangalore-54

DEPARTMENT OF
COMPUTER APPLICATIONS

CERTIFICATE
This is to certify that the project entitled ‘Sport Tournament Management System’ is carried out by

SANJAY M 1MY19MCA15
__________________________ _________________________

Student of 5th Semester, in partial fulfilment for the Course: Object Oriented Modeling and Design
Patterns Laboratory, Course code: MCA51, during the academic year 2022.

(Sign) (Sign)
Faculty In-charge Head of the Dept.
(Dr. Evangelin Geetha D) (Dr. S Seema)
1. Problem Description
The Sports Tournament Management System (SMS) objective is to provide which manages the
activity of many sports at a time. It also manages the selection activity of students to college and to
state level. The users will consume less amount of time when compared to manual paper work
through the automated system. The system will take care of all the servicing activity in a quick
manner. Data storing is easier. It will be able to check any report at any time

Purpose

This purpose of this request is to provide detail how this system manages the activity of much sport
at a time. It also deals with the selection of student at collages, university and even at state level. This
system will provide the serving activity in quick and easy manner. It will consume less amount of
time as it is based on automatic system

Scope

Sport Tournament management system is the application of project management to the creation and
development of festivals and Events.

Generally, most of the sport management system is having problems like offline registration, manage
single tournament, manage statistics and maintain log of players, Team and Tournament.
It is also difficult to manage multiple Tournament.
It is also difficult to remind player before the match in case player forget the match day.
So, our proposed system will allow different tournament registration,
automatic or manual match scheduling and provide notification to player via android application
Our project is the replacement of the ordinary sport tournament management system. In ordinary
tournament management system, there is no different tournament. In our proposed system, system
will allow creating multiple tournaments by tournament owners.
Player and tournament owner are the users of the system. In our system, match scheduling can be
done automatic or manual. It provides statistics of the match and also maintain player log. Player
can view their profile. Previous record and player log also can be managed. Player gets notification
before start of the match as a reminder in Android Application. Admin upload news and gallery.
Admin can manage news and gallery. This application is very useful for various sport organization
and sport clubs. It will also help to school and colleges for manage tournament at school and college.
So, our application provides them a single platform for all the details
and management of tournament.
2. Class Model
The class model shows all the classes present in the system. The class model shows the attributes
and the behaviour associated with the objects. The class diagram is used to show the class model.
The class diagram shows the class name followed by the attributes followed by the functions or
the methods that are associated with the object of the class. Goal in constructing class model is
to capture those concepts from the real world that are important to an application.

2.1. Class Diagram

Class diagram is a static diagram. The class diagrams are widely used in the modeling of
object-oriented systems because they are the only UML diagrams, which can be mapped
directly with object-oriented languages. Class diagram shows a collection of classes,
interfaces, associations, collaborations, and constraints.
2.2. Description
The Sports Tournament Management System class diagram consists of ten classes:
1. Admin
2. Notice
3. News
4. Main Schedule
6. Statistics
7. Cricket Score
8. Master Score
9. Player
10. Notification

1) Admin: It consists of four attributes and seven operations. The attributes are id, Name,
Contact_no, Address. The operations of this class are Create_Tournament(),
View_Static(),System_Registration(),View_Profile(),Update_schedule(),Upload_News(),Appro
ve_Registration()
2) Notice: It consists of three attributes and two operations. The attributes are Notice_Id,
Notice_Contain, Team_Id. The operations of this class are Notice (), Report ().
3) News: It consists of three attributes and two operations. The attributes are
News_Id, News_Contain, News_Status. The operations of this class are Notice (), Report ().
4) Main Schedule: It consists of five attributes and one operation. The attributes are Team_id,
Team2_id, Team3_id, Match_Date, Match_Time. The operations of this class are Manage
Schedule ().
6) Statistics: It consists of three attributes and one operation. The attributes are Team_id,
Match_id, Player_id. The operation of this class is Scoring ().
7) Cricket Score: It consist of seven attributes. The attributes are Player_Type, Balls, Runs,
Fours, Six, Wide, Wicket.
8) Master Score: It consist of one attribute. Attribute is Point.
9) Player: It consists of five attributes and six operations. The attributes are Id, Name,
Contact_no, Address, Player_Status. The operation of this class is View_Static (),
System_Registration (), View_Profile (), Authentication (), Team_Registration (),
View_Schedule ().
10)Notification: It consists of six attributes and one operation. The attributes are Team_id,
Player_id, date, Team1, Team2, Team3. The operation of this class is Notification ().
3. State Model
The state model describes the states and events in a system using a diagram or table. There are
many different types of state diagrams and tables. In an object-oriented approach a state model
is typically used to describe the lifecycle of a complex object.

3.1. State Diagram

A state diagram, sometimes known as a state machine diagram, is a type of behavioural diagram
in the Unified Modeling Language (UML) that shows transitions between various objects.
Player:
Tournament:
4. Interaction Model
Interaction models shows the interaction between the components of a system, or
between the system being developed and other systems (or users).
4.1. Use case Diagram
A use case diagram is used to represent the dynamic behaviour of a system. It encapsulates the
system's functionality by incorporating use cases, actors, and their relationships. It models the
tasks, services, and functions required by a system/subsystem of an application.
4.2. Actor Description
1. Player:
• Player can register in the tournament.
• Player can view their profile.
• Player get notification via android application.
• Player can view detail of different matches and different Tournament.
• Player can search Tournament after registration in the system.
• Player can view different match schedule.
• Use cases of Player are Register, Login, Tournament Registration, View
Profile/Detail, Payment, Get Notification, Logout.

2. Tournament Owner:
• Tournament Owner can register for new tournament.
• Tournament Owner can create new tournament.
• Tournament owner give the confirmation about tournament registration to
player.
• Tournament Owner can view all matches details.
• Tournament owner manage schedule.
• Use cases of Tournament Owner are Register, Login, create match, generate
match schedule, View Profile/Detail, Upload Statistics, Payment.
3. Admin:
• Admin can upload news.
• Admin can approve player and tournament.
• Admin manage all data
• Use cases of Admin are View Profile/Detail, Upload News/Notice, Get
Notification, Logout.
4.3. Use Case Description
This use case allows the tournament organizer to update the. Tournament information
such as name, logo, description, event date, Information. Most of the sport management
system is having problems like offline registration, manage single tournament, manage
statistics etc. To overcome all these
problems we are proposing the system STMS (Sport Tournament Management System)
with utilities like different tournament registration, automatic or manually match
scheduling, statistics for tournament, notification as reminder, maintaining log. In our
proposed system tournament owner will register in system and create new tournament.
Player can also register team member and player profile. Then System will schedule
the matches of the tournament. System will provide automatic or manual scheduling
Facility. System will provide a utility like notification as a reminder to the player before
match. It will avoid duplication of tournament for a player, team and game.

Tournament Registration:

In registration function, new tournament creates by tournament owner and

register their tournament.

Player registration:

In player registration, player can register for match.

Match schedule:

Match schedule can be done automatically or manually.

Statistics:

In this function it manages all player score and it manages Player record.

User characteristics:

User of website knows basic knowledge of operating a website and user must know to
navigate in a website.
4.4. Sequence Diagram
A Sequence Diagram simply depicts interaction between objects in a sequential order.
The purpose of a sequence diagram in UML is to visualize the sequence of a message
flow in the system. The sequence diagram shows the interaction between two lifelines as
a time-ordered sequence of events.
5. Activity Diagram
An activity diagram is a behavioural diagram i.e., it depicts the behaviour of a system. An activity
diagram portrays the control flow from a start point to a finish point showing the various decision
paths that exist while the activity is being executed.
Player:
Tournament: