SPORT TOURNAMENT MANAGMENT SYSTEM (STMS)

A PROJECT REPORT
on
“SPORT TOURNAMENT MANAGMENT SYSTEM”
Submitted by
AMRANI RAHUL A. (120840131023)
MAISURIYA VINOD M. (120840131032)
PATIDAR NIKHIL N. (130843131015)
PRAJAPATI DILIP J. (130843131016)
In fulfillment for the award of the degree
of
BACHELOR OF ENGINEERING
in
Computer Science and Engineering
Faculty of Engineering Technology & Research,
Isroli - Bardoli
Gujarat Technological University,
Ahmedabad
MAY-JUNE 2016

Faculty of Engineering Technology & Research
Department of Computer Engineering
Academic Year 2015-16
CERTIFICATE
Date: / / 2016
This is to certify that the Project entitled “Sport Tournament Management System” has
been presented by Amrani Rahul Ashokbhai (120840131023), Maisuriya Vinod
Manharbhai. (120840131032), Patidar Nikhil Narayanbhai (130843131015), Prajapati
Dilip Joitaram (130843131016) in fulfillment of the degree of Bachelor of Engineering in
Computer Science and Engineering (8th
Semester) of Gujarat Technological University,
Ahmedabad during the academic year 2015-16.
Date: / / 2016
Place: FETR, Isroli- Bardoli.
Internal Examiner External Examiner
Prof. Nikunj Y. Kansara Prof. Dhaval J. Rana
(Project Guide) (Project Coordinator)
Prof. Bhavini R. BHATT Dr. Latesh B. Chaudhari
(Head of Department) (Principal)

GUJARAT TECHNOLOGICAL UNIVERSITY
CERTIFICATE FOR COMPLETION OF ALL ACTIVITIES AT ONLINE PROJECT PORTAL
B.E. SEMESTER VIII, ACADEMIC YEAR 2015-2016
Date of certificate generation : 29 May 2016 (10:53:29)
This is to certify that, Amrani Rahul Ashokbhai ( Enrolment Number -
120840131023 ) working on project entitled with Sport Tournament
Management System from Computer Science & Engineering department of
Faculty Of Engineering ,Technology And Research. Bardoli, Surat had
submitted following details at online project portal.
Periodic Progress Reports (PPR) Completed
Business Model Canvas (Image) Completed
Business Model Canvas (Report) Completed
Patent Drafting Exercise (PDE) Completed
Final Plagiarism Report Completed
Final Project Report Completed
Name of Student : Amrani Rahul Ashokbhai Name of Guide : Mr. Nikunj Yogeshbhai Kansara
Signature of Student : _____________ *Signature of Guide : ________________
Disclaimer :
This is a computer generated copy and does not indicate that your data has been evaluated. This is the receipt that GTU
has received a copy of the data that you have uploaded and submitted as your project work.
*Guide has to sign the certificate, Only if all above activities has been Completed.

This is to certify that, Maisuriya Vinodkumar Manharbhai ( Enrolment Number
- 120840131032 ) working on project entitled with Sport Tournament
Name of Student : Maisuriya Vinodkumar
Manharbhai
Name of Guide : Mr. Nikunj Yogeshbhai Kansara
Disclaimer :

This is to certify that, Patidar Nikhilkumar Narayanbhai ( Enrolment Number -
Name of Student : Patidar Nikhilkumar
Narayanbhai
Name of Guide : Mr. Nikunj Yogeshbhai Kansara
Disclaimer :

This is to certify that, Prajapati Dilip Joitaram ( Enrolment Number -
Name of Student : Prajapati Dilip Joitaram Name of Guide : Mr. Nikunj Yogeshbhai Kansara
Disclaimer :

Gujarat Technological University
Project Feedback Certificate
This is to certify that the Bachelor of Engineering Project Work Report entitled
“Sport Tournament Management System”
Submitted By:
Enrollment No. Name of Students
(1) 120840131023 Amrani Rahul A.
(2) 120840131032 Maisuriya Vinod M.
(3) 130843131015 Patidar Nikhil N.
(4) 130843131016 Prajapati Dilip J.
as the record of the work carried out by them, is accepted as the B.E. IV Project
Work Report submission in partial fulfillment of the requirements for the award
of degree of Bachelor of Engineering in Computer Science & Engineering of
Faculty of Engineering Technology & Research, Bardoli.
Name and Signature of Guide
Prof. Nikunj Y. Kansara

Faculty of Engineering Technology & Research
Department of Computer Science and Engineering
Academic Year 2015-16
CERTIFICATE
Date: / / 2016
This is to certify that the Project entitled “Sport Tournament Management System” has been
presented by Amrani Rahul A. (120840131023), Maisuriya Vinod M. (120840131032), Patidar
Nikhil N. (130843131015), Prajapati Dilip J. (130843131016) in fulfillment of the degree of
Bachelor of Engineering in Computer Science and Engineering (8th
Semester) of Gujarat
Technological University, Ahmedabad during the academic year 2015-16.
Date: / / 2016
Place: FETR, Isroli-Bardoli.
Signature and Name of Examiners:
1.
2.

SELF-DECLARATION (by a student/ team of students) of each IDP/UDP
(This has to be attached along with IDP/UDP report while submitting to the departments in hard copy)
SELF-DECLARATION (by a student/ team of students)
I/We
Amrani Rahul A. ,Maisuriya Vinod M. , Patidar Nikhil N. , Prajapati Dilip J. , the student(s) of
Computer Science and Engineering Branch /enroll number 120840131023,120840131032,130843131015,
130843131016 enrolled at Faculty of Engineering Technology & Research (college name) hereby certify and
declare the following:
• We have defined our project based on inputs at
Faculty of Engineering Technology & Research ( users name / industry/any other user like
faculties or any other organizations) and each of us will make significant efforts to make
attempt to solve the challenges .I/We will attempt the project work at my college or at any
location under the direct and consistent monitoring of Prof. Nikunj Y. Kansara
We shall adopt all ethical practices to share credit amongst all the contributors based on their
contributions during the project work. (We will work on the project work under the direct and
consistent monitoring of Industry mentors and Faculty Guides)
• I/We have not purchased the solutions developed by any 3rd
party directly and the efforts are
made by me/us under the guidance of guides.
The project work is not copied from any previously done projects directly. (The same problem
can be attempted done in new ways.)
• The project work submitted by me/us is prepared by me/us and I/we fully understand the
contents. We will make best efforts to solve the problems given by the user/ industry. If the
project is in relay model (kho-kho) we will share credits with the initial contributors.
• NIL (Name of industry) to the best of my knowledge is a genuine industry ,
engaged in the professional service/social organizations I/we understand and accept that the
above declaration if found to be untrue, it can result in punishment/cancellation of project
definition to me/we including failure in the subject of project work.
Name/Names: Amrani Rahul A., Maisuriya Vinod M., Patidar Nikhil N., Prajapati Dilip J.
Contact number/numbers: 9638690892,8460333609,9033587469,9429730066
Date: Sign:/signs
Place:

UDP Project Statement Form
(This is a sample format and departments can modify it if they need as per required scenario and sector)
TITLEOF PROBLEM/PROJECT
SPORT TOURNAMENT MANAGEMENT SYSTEM
DICIPLINARY | INTER-DICIPLINARY DICIPLINARY
DISCIPLINE/S Bachelor of Engineering
STUDENT PARTICULARS
NAME MOBILE NO EMAIL ID
1. Amrani Rahul A. 9638690892 amrani_rahul@yahoo.com
2. Maisuriya Vinod M. 8460333609 vinodmm143@gmail.com
3. Patidar Nikhil N. 9033587469 patidar.nikhil48@gmail.com
4. Prajapati Dilip J. 9429730066 dilipprajapati94@gmail.com
COLLEGE NAME Faculty of Engineering Technology & Research
COLLEGE CODE 84
BRANCH Computer Science and Engineering
SEMESTER Eight (8th
) YEAR 2015-16
TEAM CODE ( to be given by
the institute )
45252
SIGNATURE OF STUDENTS
(TEAM MEMBERS)
INDUSTRY PARTICULARS/USER’S DETAIL
INDUSTRY DETAILS
NAME NIL
ADDRESS NIL
CONTACT NO. OFFICE NIL MOBILE NIL
NAME OF INDUSTRIAL ESTATE NIL
COMPANY LOGO
( optional)
NIL
INDUSTRY GUIDE DETAILS
NAME NIL
MOBILE NO. NIL
EMAIL ID NIL

PLAGIARISM UNDERTAKING
We hereby certify that we are the sole authors of this IDP/UDP project report and that neither
any part of this IDP/UDP project report nor the whole of the IDP/UDP Project report has
been submitted for a degree by other student(s) to any other University or Institution.
We certify that, to the best of our knowledge, the current IDP/UDP Project report does not
infringe upon anyone’s copyright nor violate any proprietary rights and that any ideas,
techniques, quotations or any other material from the work of other people included in our
IDP/UDP Project report, published or otherwise, are fully acknowledged in accordance with
thestandard referencing practices. Furthermore, to the extent that we have included
copyrighted material that surpasses the boundary of fair dealing within the meaning of the
Indian Copyright (Amendment) Act 2012, we certify that we have obtained a written
permission from the copyright owner(s) to include such material(s) in the current IDP/UDP
Project report and have included copies of such copyright clearances to our appendix.
We have checked the write up of the present IDP/UDP Project report using anti-plagiarism
database and it is in the allowable limit. In case of any complaints pertaining to plagiarism,
we certify that we shall be solely responsible for the same and we understand that as per
norms, University can even revoke BE degree conferred upon the student(s) submitting this
IDP/UDP Project report, in case it is found to be plagiarized.
Team: 45252
Enrollment No Name Signature
120840131023 Amrani Rahul A.
120840131032 Maisuriya Vinod M.
130843131015 Patidar Nikhil N.
130843131016 Prajapati Dilip J.
Place:FETR, Isroli-Bardoli
Date: / / 2016
Prof. Nikunj Y. Kansara
[Project Guide]

I
Acknowledgement
The acknowledgement is just a drop of sense of gratitude within our hearts for
the people who helped us out of the most embarrassing part of life when we are
standing on the last & most difficult step towards our life.
The entire session of our phase I completion was a great experience providing
us with the insight & invocation into learning various software engineering concepts &
benefits of team work. Likewise, every member has burnt fuel, day & night for
completing project. We would like to take this opportunity to express our sincere
thanks to all those people without whose support and co-operation, it would have been
difficult to complete this project.
Primarily, we are very much thankful to our project guide Prof. Nikunj Y.
Kansara for his leading guidance and sincere efforts throughout project work. He took
deep interest in simplifying the difficulties. Also he has been consistent source of
inspiration for us.
We also express thanks to Prof. Dhaval J. Rana project coordinator for his
personal involvement, constructive suggestion and thoughtful idea for betterment the
project.
We are grateful to our H.O.D. Prof. Bhavini R. Bhatt and our beloved Principal
Dr. Latesh B. Chaudhari for providing us deep knowledge and all necessary resources.
We are also thankful to our Friends and Non-teaching Staff for their valuable
time & help for completion project.
Once again we are grateful to all those without whom this work would not
have been successful.
Project Associates
Amrani Rahul A.
Maisuriya Vinod M.
Patidar Nikhil N.
Prajapati Dilip J.

II
ABSTRACT
Nowadays, 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.

III
LIST OF FIGURES
FIGURE NO FIGURE DESCRIPTION PAGE NO
1.8 Project Plan 4
2.1.1.1 Screen shots of Cricket graph (homepage) 5
2.1.1.2 Screen shots of Cricket graph (player profile) 6
2.1.2.1 Screen shots of Victo club (homepage) 7
2.1.2.2 Screen shots of Victo club (team list) 8
4.1.1 System flow for Tournament 14
4.1.2 System flow for Player 15
4.2.1 Usecase Diagram of STMS 16
4.2.2 Class Diagram of STMS 17
4.2.3 Sequence Diagram of the STMS 18
4.2.4.1 Activity Diagram for player 19
4.2.4.2 Activity Diagram for Tournament 20
4.2.5.1 State chart Diagram for player 21
4.2.5.2 State chart Diagram for Tournament 22
4.2.6 Collaboration Diagram of STMS 23
4.2.7 Component Diagram of STMS 24
4.3.1 E-R Diagram of STMS 25
4.3.3.1 Level 0 of STMS 31
4.3.3.2 Level 1 of Admin 32
4.3.3.3 Level 2 of Tournament 32
4.3.3.4 Level 3 of player 33
4.3.3.5 Level 4 of Team Leader 33
4.4.1 AEIOU Summary 34
4.4.2 Empathy Canvas 35
4.4.3 Ideation Canvas 36
4.4.4 Product Development Canvas 37
4.4.5 Business Model Canvas 38
5.1 Home Page 39
5.2 Player Registration 40

IV
LIST OF FIGURES
FIGURE NO FIGURE DESCRIPTION PAGE NO
5.3 Tournament Registration 40
5.4 Team Registration 41
5.5 Player Detail 41
5.6 Tournament Detail 42
5.7 Player Login 42
5.8 Tournament Login 43
5.9 Login Player Detail 43
5.10 Player Edit Profile 44
5.11 Player Change Profile Picture 44
5.12 Tournament Detail 45
5.13 Match Schedule 45
5.14 Automatic Match Schedule 46
5.15 Player Score Input 46
5.16 Team Scoreboard 47
5.17 Tournament Edit Profile 47
5.18 Tournament Change Logo 48
5.19 Team Detail 48
5.20 Add Player 49
5.21 View Requested Player 49
5.22 View Team Player 50
5.23 Contact Us 50
5.24 Login for player 51
5.25 Player home page 51
5.26 Player detail 52
5.27 Player Notification 52

V
LIST OF TABLES
TABLE NO TABLE DESCRIPTION PAGE NO
2.2 Comparative statement of survey 8
2.4 PSAR Summary 9
4.3.2.1 Player Registration 26
4.3.2.2 block 26
4.3.2.3 Admin 27
4.3.2.4 team 27
4.3.2.5 District 27
4.3.2.6 State 28
4.3.2.7 tona 28
4.3.2.8 gtype 29
4.3.2.9 tona_match 29
4.3.2.10 t_player 29
4.3.2.11 News 29
4.3.2.12 Notice 30
4.3.2.13 Notification 30
6.1.1.1 Testing of Admin Login 53
6.1.1.2 Testing of Player Login 54
6.1.1.3 Testing of Tournament Login 55
6.1.1.4 Testing of player 56
6.1.1.5 Testing of tournament 57
6.1.1.6 Testing of Team 58
6.1.1.7 Testing of Functionality 59
6.1.2 Result Analysis 60

VI
LIST OF ABBERVIATIONS
NO Symbol Name Abbreviations
1 STMS Sport Tournament Management System
2 GUI Graphical User Interface
3 UML Unified Modelling Language
4 Admin Administrator
5 DFD Data Flow Diagram
6 SQL Structure Query Language
7 ER Entity Relationship
8 PHP Hypertext Pre-Processor

TABLE OF CONTENTS
CHAPTERS PAGE NO.
ACKNOWLEDGEMENT I
ABSTRACT II
LIST OF FIGURES III
LIST OF TABLES V
LIST OF ABBERVIATIONS VI
TABLE OF CONTENTS VII
CHAPTER 1 INTRODUCTION OF PROJECT 1
1.1 Phase-I Summary 1
1.2 Phase-II Summary 1
1.3 Introduction of Problem 2
1.4 Problem Statement and explanation 2
1.4.1 Problem Statement 2
1.4.2 Project Description 2
1.5 Project Useful to society 3
1.6 Technologies Requirement 3
1.7 Background Theory 3
1.8 Project Plan 4
CHAPTER 2 LITERATURE REVIEW 5
2.1 Existing Systems 5
2.1.1 Website for Cricketgraph 5
2.1.2 Website for Victroclub 7
2.2 Comparative statements from survey 8
2.3 Motivation from survey 9
2.4 PSAR Summary 9
CHAPTER 3 System Analysis 10
3.1 Introduction 10
3.1.1 Purpose 10
3.1.2 Scope 10
VII

3.1.3 Document Convention 10
3.2 Overall Description 10
3.2.1 Product Perspective 10
3.2.1 Product function 11
3.2.1 Constraint, Assumption and dependencies 11
3.3 Special Requirement 11
3.3.1 User Interface 11
3.3.2 Hardware Interface 11
3.3.3 Software Interface 11
3.3.4 Communication Interface 12
3.4 Functional Requirement 12
3.5 Other Non-Functional Requirement 13
3.5.1 Error Handling 13
3.5.2 Authentication Requirement 13
3.5.3 Security Requirement 13
CHAPTER 4 System Design 14
4.1 System Flow chart 14
4.1.1 Tournament Flow 14
4.1.2 Player Flow 15
4.2 UML Diagram 16
4.2.1 Use case Diagram 16
4.2.2 Class Diagram 17
4.2.3 Sequence Diagram 18
4.2.4 Activity Diagram 19
4.2.5 State Chart Diagram 21
4.2.6 Collaboration Diagram 23
4.2.7 Component Diagram 24
4.3 Database Design 25
4.3.1 E-R Diagram 25
4.3.2 Data Dictionary 26
4.3.3 Data flow Diagram 31
VIII

4.4 Canvas 34
4.4.1 AEIOU Summary Canvas 34
4.4.2 Empathy Canvas 35
4.4.3 Ideation Canvas 36
4.4.4 Product Development Canvas 37
4.4.5 Business Model Canvas 38
CHAPTER 5 IMPLEMENTATION 39
CHAPTER 6 TESTING AND ANALYSIS 53
6.1 Testing and Result Analysis 53
6.1.1 testing 53
6.1.2 Result Analysis 60
6.2 Advantages 60
6.3 Usefulness with respect to existing System 60
6.4 Unique feature of project 60
CHAPTER 7 FUTURE ENHANCEMENT 61
CONCLUSION 62
REFERNCES 63
APPENDIX 64
A. Project Progressive Report
B. PDE Report
C. Plagiarism Report
D. BMC Report
E. Weekly Progressive Report
IX

Sport Tournament Management System
[Department Of Computer Engineering] Page 1
CHAPTER 1
INTRODUCTION OF PROJECT
1.1 Phase-I Summary
In Phase-I we have done following activity in our project.
 Literature Survey
For Literature Survey, We have visited website related to our system. We have
also reviewed some patent as a part of PSAR activity for literature survey. We
have visited website www.cricketgraph.com and www.victroclub.com for
literature survey.
 System Analysis
In system analysis part, we have studied about requirement specification of our
project. There is included functional and non-functional requirement of our
project. We have also designed Software requirement specification called SRS
for our system.
 Canvas
We made four canvas in this phase
1. AEIOU Canvas
2. Empathy Canvas
3. Ideation Canvas
4. Product Development Canvas
 Basic Implementation
In this part, we have made GUI of our project.
1.2 Phase-II Summary
In Phase-II we will do following activity in our project.
 Implementation
We will implement our project as per software requirement specification
As given in first phase.

 Business Model Canvas
We made BMC for strategic management and entrepreneurial tool for
allowance to describe, design, challenge, invent and pivot our business model.
 Testing
We will test all the module of project by many techniques like
1. Unit Testing
2. Functional Testing
3. Performance Testing
1.3 Introduction of problem
Nowadays, 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 incase 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.
1.4 Problem Statement and explanation
1.4.1 Problem Statement
Generally the most of the sport tournament management system, having problems
like offline registration, manage single tournament. It is difficult to manage records of
each player profile. There is also problem to manage schedule of the match.
1.4.2 Project Description
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 tournament 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.

1.5 Project useful to Society
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 provide them a single platform for all the details and management of
tournament.
1.6 Technologies Requirements
We want to develop this project in PHP Programming language and also android for
mobile application.so, we need following requirement.
 Nusphere for PHP
 Android SDK and Eclipse for android
 MYSQL for Database
 Wampserver
1.7 Background theory
1. Tournament Owner will organize tournament and advertise it to interested
team.
2. Tournament Owner will start the registration of limited team as per his
requirement.
3. Tournament Owner manage paperwork for player detail and team detail for
record of the tournament.
4. Tournament Owner display Rules and Regulation of tournament to every
team.
5. Tournament Owner create match scheduling and give it to every team by
Phone call or message.
6. Tournament Owner provide score after end of the match.
7. Final team will win the tournament and give trophy to that team or prize-
Money.
8. Dealing with paperwork, phone calls, emails and letters.

1.8 Project Plan
Figure 1.8 Project Plan

CHAPTER 2
LITERATURE REVIEW
2.1 EXISTING SYSTEM
2.1.1 www.cricketgraph.com
In this website, user can view tournament by name. User can search tournament by
Name. User can view team score and player score for each match. Here match scheduling
is not generate automatically. It generates manually. User can see rules and regulation of
match. Player are also group member of club. It is also provide news and blog and it
updates at the certain time of interval. Following is the screenshot of this system.
Figure 2.1.1.1 Screen shots of Cricketgraph (homepage)

Figure 2.1.1.2 Screen shots of Cricketgraph (player profile)

2.1.2 www.victroclub.com
This system is only limited to only single tournament. It manage only single
tournament. Player can view their profile by logging in the system. System provides
player log, tournament logs, news etc. There is no multiple games support. And it is static
website.
Figure 2.1.2.1 Screen shots of Victroclub (homepage)

Figure 2.1.2.2 Screen shots of Victrograph (team list)
2.2 Comparative statements from survey
Table.2.2 Comparative statement of survey
Functionalities Existing Proposed
Registration Offline Online
Scheduling Manually Manually/auto
Statistic Yes Yes
Notification No Yes
Android app No Yes
Manage data Offline Online

2.3 Motivation from Survey
After studied different website related to sport management system we can say that
there are different methodology and techniques to implement this kind of system. But, we
are thinking about make a system that includes multiple sport management. So, different
sport management and also different tournament can be managed. We are also making
android application that useful to player. Player get notification via android application.
So after literature survey we are fully sure that how can we develop the system which is
very useful now a days. And literature survey helps us to find out different approaches
and also motivated us for develops the system.
2.4 PSAR Summary
Table 2.4: PSAR Summary
Sr no. Patent_Id Description
1 US 20080280663 A1 User can registration in multiple gaming and it’s
include hierarchical rounds that include at least first
round and second round.
2 US 20070191102 Solved the problem of multiple tournament
3 US 20140040239 A1 It can manage scheduling and organize tournament.
4 US 2014004023 A1 The statistics being related to provide statistics levels
comparison at least game.

CHAPTER 3
SYSTEM ANALYSIS
3.1 Introduction
3.1.1 Purpose
The purpose of this document is to provide the reader with general, background
information about the software sports tournament management system.
3.1.2 Scope
This document is intended for all the users to understand the usage and maintenance
of the software who will know about the basic knowledge of computer.
3.1.3 Documentation Conventions
Throughout this documentation, the following conventions have been used:
 Fonts: Times New Roman
 Size 16 for Main Headings
 Size 14 for Sub Headings
 Size 12 for the Rest of the Document
3.2 OVERALL DESCRIPTION
3.2.1 Product Perspective
The STMS is replacement for sport management system which depend on
Paperwork for team and tournament registration. This project provides match scheduling
and player profile, team and player registration.

3.2.2 Product Function
Tournament Registration:-
In registration function, new tournament create 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.
3.2.3 Constraint, Assumptions and Dependencies
MS-Sql server will be used as a sql engine and database User may access system
from any computer that has internet connection. User must have to enter correct username
and password.
3.3 Special Requirement
3.3.1 User Interface
There is three different user interfaces in this system. That is one for Tournament
one for player and one for administrator.
3.3.2 Hardware Interface
Mobile phone for player to view notification.
3.3.3 Software Interface
Any Windows based operating system (Windows XP).
Wamp Server Package and Xamp Server Package.

Android Studio (eclipse Luna) and PHP (NuSphere PhpED)
3.3.4 Communication Interface
Internet is required.
3.4 Functional Requirement
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.
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.
Admin
 Admin can upload news.
 Admin can approve player and tournament.
 Admin manage all data

3.5 Other non-functional Requirement
3.5.1 Error handling
This Product shall handle expected and non-expected errors in ways that prevent
loss information and long downtime period.
3.5.2 Authentication Requirements
System checks username and password every time when user log in to the system
and System give different type of privilege to different users.
3.5.3 Security Requirements
System will use secured database normal users can just read information but they
cannot edit or modify anything. System will have different types of users and every user
has access constraints.

CHAPTER 4
SYSTEM DESIGN
4.1 System Flow Chart Diagram
4.1.1 Tournament Flow
Start
already
Registerd
Fill proper
detail
Login
yes no
Check
username &
Password
correct
detail
no
yes
no
match
Scheduling
Statistics
auto match
scheduling
Upload score
Logout
yes
yes
view participate
team
manually match
scheduling
Stop
Figure 4.1.1 System Flow for Tournament

4.1.2 System Flow for Player
Start
already
Registerd
Fill proper
detail
Login
yes no
Check
username &
Password
correct
detail
no
yes
no
view & manage
profile
view team request
Approval for Team
player
get notification
View
Detail
Logout
yes
Stop
Figure 4.1.2 System Flow for Player

4.2 UML Diagram
Unified Modeling Language (UML) combines techniques from data modeling (entity
relationship diagrams) and component modeling. It can be used with all processes,
throughout the software development life cycle, and across different implementation
technologies.
4.2.1 Usecase Diagram
Figure 4.2.1: Use case Diagram of STMS

4.2.2 Class Diagram
In software engineering, a class diagram in the Unified Modeling Language (UML)
is a type of static structure diagram.
Owner
Id:int
Name:char
Contact_no: int
Address:string
Tournament_Id:int
Create_Tournament()
View_Static()
System_Registration()
View_Profile()
Scheduling()
Update_Schedule()
Player
Id:int
Name:char
Contact_no: int
Address:string
Game_type:string
P_status:string
View_Static()
System_Registration()
View_Profile()
Authencation()
Team_Registration()
View_Schedule()
Match Schedule
T_Id:int
Team1_Id:int
Team2_Id:int
M_Id:int
M_Date:date
M_Time:time
Win_Id:int
Manage_Schedule()
Admin
Admin_Id:int
Admin_Name:char
Upload_News()
Approve_Owner_Reg()
News
Ne_Id:int
Ne_Contain:string
Ne_Status:string
Notice()
Report()
Statstics
T_Id:int
M_Id:int
Te_Id:int
P_Id:int
Scoring()
Cricket Score
P_Type:string
Balls:number
Runs:number
4's:number
6's:number
Wide:number
Wicket:number
Master Score
Point:int
*
1 *
Notice
No_Id:int
No_Contain:string
T_id:int
Notice()
Report()
*
Notification
Te_id:int
P_id:int
date:date
team1:varchar
team2:varchar
msg:varchar
Notification()
1
*
1
*
1
*
1
1
1
1
*
1
*
Figure 4.2.2 Class Diagram of STMS

4.2.3 Sequence Diagram:
When an object passes a message to another object, the receiving object might in
turn sends a message to another object, and so on. This stream of message forms a
sequence. The messages are ordered in sequence by time. Sequence diagram models these
sequences. A sequence diagram describes a pattern of interaction among objects, arranged
in a chronological order. It shows the objects participating in the interaction by their
“lifelines” and the message that they send to each other.
Figure 4.2.3: Sequence Diagram of STMS

4.2.4 Activity Diagram:
Activity diagram represent the dynamics of the system. It focuses on
representing various activities or chunk of processing and their sequence of activities.
Activity diagram are used to show the work flow of a system.
4.2.4.1 Activity for Player:
registration
Login
edit profile
view player
profile
view team
request
approve team
request
logout
Figure 4.2.4.1.: Activity Diagram for Player

4.2.4.2 Activity for Tournament:
Registration
Login
change profileview profile
view team
detail
view player
details
create match upload score
logout
Figure 4.2.4.2: Activity Diagram for Tournament Owner

4.2.5 State Chart Diagram:
4.2.5.1 Player:
registration
login
view team request
view profile
approve team
request
edit profile
logout
Figure 4.2.5.1 : State Chart for Tournament Owner

4.2.5.2: State chart for Tournament:
registration
login
upload score
create match
view team detail
view profile
view player detail
change profile
logout
Figure 4.2.5.2: State chart for Tournament Owner

4.2.6 Collaboration Diagram:
A collaboration diagram describes interactions among objects in terms of
sequenced messages. Collaboration diagrams represent a combination of information
taken from class, sequence, and use case diagrams describing both the static structure and
dynamic behavior of a system.
Figure 4.2.6 Collaboration Diagram of STMS

4.2.7 Component Diagram:
Figure 4.2.7 Component Diagram of STMS

4.3 Database Design
4.3.1 E-R Diagram:
An entity–relationship model (ER model) is a data model for describing the data or
information aspects of a business domain or its process requirements, in an abstract way
that lends itself to ultimately being implemented in a database such as a relational
database. The main components of ER models are entities (things) and the relationships
that can exist among them, and databases.
Player
Match
Schedule
Admin
match_score
Tournament
News
Register
Approve
Upload
fname
pno
gtype
P_Id
state
gnd ttype
to_id
uname
ps
uname
Upload
Ne_Description
Ne_Id
Ne_Date
to_id
win
ti
View
Manage
t_id
to_id
id
type
4s
6s
wck
Runs
ball
Wide
*
* *
*
*
*
*
1
*
1
*
*
*
Notification
team1
Te_Id
P_Id
team2
dt
get
*
*
id
Notice
No_content
T_id
Upload
m_id
total
p_id
over
No_id
Username
ps
pi
mname
lname
eid
dob
block
distic
addr
pin
status
a_id
logo
tname
ps
*
*
tsdate
tedate
rsdate
redate
block distic
state
eid
pno
pin
addr
status *
t2
t1 *
msg
Figure 4.3.1 E-R Diagram of STMS

4.3.2 Data Dictionary
Table 4.3.2.1: player
Column Name Data Type Size Constrains Description
p_id int 10 pk,not null Player id
uname varchar 100 not null Player User Name
ps varchar 100 not null Password
pi varchar 100 not null Player Image
fname varchar 100 not null Player First Name
mname varchar 100 not null Player Middle Name
lname varchar 100 not null Player Last Name
gnd varchar 100 not null Gender
pno varchar 100 not null Phone No
eid varchar 100 not null Email Id
dob date not null Date Of Birth
state varchar 100 not null State
distic varchar 100 not null District
block varchar 100 not null Block Or City
addr varchar 100 not null Address
pin varchar 100 not null Pincode
status enum not null Status
gtype varchar 100 not null Game Type
Table 4.3.2.2: block
b_id Int 10 not null,pk Block id
s_id Int 100 not null,fk State id
d_id Int 100 not null,fk Distic id
sname Varchar 100 not null State Name
dname Varchar 100 not null Distic Name
bname Varchar 100 not null Block Name

Table 4.3.2.3: admin
a_id Int 10 not null Admin user id
uname varchar 100 not null Admin user name
Ps varchar 100 not null Admin Password
Table 4.3.2.4: team
Column
Name
Data Type Size Constrains Description
t_id Int 10 pk,not null Team id
uname varchar 100 not null User Name
to_id Int 10 not null Tournament id
tname varchar 100 not null Tournament name
logo varchar 100 not null Tournament Logo
pno varchar 100 not null Phone Number
eid varchar 100 not null Email id
block varchar 100 not null Block
pin varchar 100 not null Pin
status Enum Player Status
tou_status Enum Tournament Status
Table 4.3.2.5: district
d_id Int 10 not null,pk District id
s_id int 10 not null,fk State id
sname varchar 100 not null State Name
dname varchar 100 not null District Name

Table 4.3.2.6: state
s_id int 10 not null,pk State id
sname varchar 100 not null State Name
Table 4.3.2.7: tona
to_id int 10 not null,pk Tournament Id
uname varchar 100 not null Uesrname
ttype varchar 100 not null Tournament Type
tname varchar 100 not null Tournament name
logo varchar 100 not null Tournament Logo
tsdate date not null Tournament Stating
Date
tedate date not null Tournament Ending
Date
rsdate date not null Registration Starting
Date
Redate date not null Registration Ending
Date
Pno varchar 100 not null Phone no
Eid varchar 100 not null Email Id
block varchar 100 not null Block
Pin varchar 100 not null Pincode
status enum not null Status
not Varchar 150 not null Notice

Table 4.3.2.8: gtype
Id int 10 not null,pk Game id
gtype varchar 100 not null Game Type
Table 4.3.2.9: tona_match
Id int 10 not null,pk Id
to_id int 10 not null,fk Tournament Id
t1 int 10 not null Team 1
t2 int 10 not null Team 2
Dt date not null Date
Ti time not null Time
win varchar 100 null Winner Team
Table 4.3.2.10: t_player
id int 10 not null,pk Id
to_id int 10 not null,fk Tournament Id
t_id int 10 not null,fk Team Id
p_id int 10 not null,fk Player Id
status enum not null Player Status
Table 4.3.2.11: news
ne_id int 10 pk,not null News id
ne_description varchar 500 not null News Description
ne_date varchar 20 News date

Table 4.3.2.12: notice
no_id int 10 pk,not null Notice id
to_id int 10 fk,not null Tournament id
no_description varchar 500 not null Notice Description
Table 4.3.2.13: notification
no_id int 10 pk,not null Notice id
msg varchar 500 not null Notice Message
date date not null Date
team1 varchar 100 not null Team 1
team2 varchar 100 not null Team2
Table 4.3.2.14: match_score
Id int 10 pk,not null Match score id
t_id int 10 not null Team id
m_id int not null Match id
p_id int 10 not null Player id
type varchar 50 not null Game type
ball int 10 not null Ball
4s int 10 not null 4s
6s int 10 not null 6s
runs int 10 not null Runs
wck int 10 not null Wicket
wide int 10 not null Wide
over float 10 not null Over
total int 10 not null Total

4.3.3 Data Flow Diagram
Level-0 DFD
Request
Response
Request
Response
Response
Database
0-Level
STMS
Tournament
Owner
Players
Admin
Figure 4.3.3.1 Level 0 of STMS

Level-1 DFD
Login
Upload News
Admin
login
Approve
tournament and
Player
Ifyes
If no
Manage all
data
to manage
Logout
news
tournament
1.1
1.1.1
1.1.2
1.1.3
Figure 4.3.3.2 Level 1 of admin
Level-2 Tournament
Tournament
Create Auto
match
scheduling
Create Manual
match
scheduling
Registration
Login
Ifno
G
enerate
View all match
Detail
View register
TeamIf yes
If yes
Manage score
Upload notice
2.1.2
2.1
2.1.3
2.1.5
2.1.2
2.1.2.1
2.2
2.1.4
login
notice
tona_match
match_score
Figure 4.3.3.3 Level 2 of tournament

Level-3 Player
Player
Registration in
the Tournament
Login
login
Ifno
view/
manage
profile
If yes
view team
request
3.1.1
3.1
3.1.3
3.1.2
Search
Tournament
3.2
player
t_player
tona
Approve team
request
3.1.3.1
Logout
3.1
Figure 4.3.3.4 Level 3 of player
Level-4 Team leader
team
leader
Registration in
the Tournament
Login
login
Ifno
view/
manage
profile
If yes
view requested
player
4.1.1
4.1
4.1.4
4.1.2
Search
Tournament
4.2
player
t_player
tona
Add player
Logout
4.3
4.1.3
t_player
team
approve team
player
4.4
t_player
updated
Figure 4.3.3.5 Level 4 of team leader

4.4 Canvas
4.4.1 AEIOU Summary Canvas
Figure 4.4.1 AEIOU Summary

4.4.2 Empathy Canvas:
Figure 4.4.2 Empathy Canvas

4.4.3 Ideation Canvas:
Figure 4.4.3 Ideation Canvas

4.4.4 Product Development Canvas:
Figure 4.4.4 Product Development Canvas

4.4.5 Business Model Canvas:
Figure 4.4.5: Business model Canvas

CHAPTER 5
IMPLEMENTATION
5.1 Home Page
Below page is the home page of website. In Home page, there are links navigate to
login, registration, player detail and tournament detail.
Figure 5.1 Home Page of STMS

5.2 Player Registration
Player fills all detail and register in the system.
Figure 5.2 Player Registration
5.3 Tournament Registration
Tournament is register in the system by a tournament owner.
Figure 5.3 Tournament Registration

5.4 Team Registration
Team leader fill all detail for new team in tournament.
Figure 5.4 Team Registration
5.5 Player Detail
Guest user can view all registered player.
Figure 5.5 Player Detail

5.6 Tournament Detail
Guest user can view all registered Tournament.
Figure 5.6 Tournament Detail
5.7 Player Login
Registered Player can log in to system.
Figure 5.7 Player Login

5.8 Tournament Login
Only Registered Tournament is log in in to the system.
Figure 5.8 Tournament Login
5.9 Login Player Detail
Player can change their profile and view team request.
Figure 5.9 Login Player Detail

5.10 Player Edit Profile
Player can change his profile if player wants to change his profile.
Figure 5.10 Player Edit Profile
5.11 Player Change Profile Picture
Player can change profile picture if player wants.
Figure 5.11 Player Change Profile Picture

5.12 Tournament Detail
After log in to the tournament, user can view registered team, create match and
upload score.
Figure 5.12 Tournament Detail
5.13 Match Schedule
User can schedule the match manually for registered team.
Figure 5.13 Match Schedule

5.14 Automatic match schedule
Match scheduling will done automatically.
Figure 5.14 Match Schedule
5.15 Player Score Input
Figure 5.15 Player Score Input

5.16 Team Scoreboard
Player score is uploaded for particular team and tournament.
Figure 5.16 Team Scoreboard
5.17 Tournament Edit Profile
User can edit his profile.
Figure 5.17 Tournament Edit Profile

5.18 Tournament Change Logo
User can change tournament logo.
Figure 5.18 Tournament change logo
5.19 Team Detail
After log in to the tournament, user can view team detail.
Figure 5.19 Team Detail

5.20 Add Player
Team leader search all player and add player in his team just after player gives
conformation to team.
Figure 5.20 Add Player
5.21 View Requested Player
Team leader can view requested player and his status. He can also delete requested
player.
Figure 5.21 View Requested Player

5.22 View Team Player
Team leader view player list that are given conformation to team.
Figure 5.22 View Team Player
5.23 Contact Us
Guest user can contact to Administrator by giving his detail.
Figure 5.23 Contact Us

5.24 Android Login Screen for Player
Android application is only for player. Player can log in to the application by
giving his username and password same as given in website.
Figure 5.24 login for player
5.25 Android Login Screen for Player Home Screen
This is the home screen for player. Player can view his profile and also player get
notification about his match.
Figure 5.25 player homepage

5.26 Android Player Detail
Player views his profile but can’t edit them. It is only editable in web application.
Figure 5.26 player detail
5.27 Android Notification to player screen
Player get notification and view the notification.
Figure 5.27 player notification

CHAPTER 6
TESTING AND ANALYSIS
6.1 Testing and Result Analysis
The software, which has been developed, has to be tested to prove its validity.
Testing is considered as the least creative phase of the whole cycle of system design. In
the real sense it is the phase, which helps to bring out the creativity of the other phases
and makes it shine.
6.1.1 Testing
Admin:
Table 6.1.1.1 Testing of Admin Login
TC
ID
TC
Name
Description Expected O/P
Actual
O/P
Test
Result
TC-1 Validate
username
and
password
User enters
username &
password to login
himself
System verifies
the username
and password
System
verifies the
username and
password
Pass
TC-2 Verify
incorrect
detail
User enters either
the username or the
password or both
incorrectly
System prompts
with the message
“Relogin”
System
prompts with
the message
“Relogin”
Pass
TC-3 Verify of
blank
field
User leaves the
email-id and
password Blank
System prompts
the message
“Please fill in
this field”
System
prompts the
message
“Please fill in
this field”
Pass

TC-4 Verify
correct
detail
User enters the
username and
password correctly
Redirect to
admin home
page
Redirect to
admin home
page
Pass
Player Login
Table 6.1.1.2 Testing of Player Login
TC
ID
TC Name Description Expected O/P
Actual
O/P
Test
Resul
t
TC-
1
Validate
username
and
password
User enters
username &
password to login
himself
System verifies the
username and
password
System
verifies the
username
and
password
Pass
TC-
2
Verify
incorrect
detail
User enters either
the username or the
password or both
incorrectly
System prompts
with the message
“Relogin”
System
prompts
with the
message
“Relogin”
Pass
TC-
3
Verify of
blank field
User leaves the
email-id and
password Blank
System prompts the
message
“Please fill in this
field”
System
prompts the
message
“Please fill
in this field”
Pass
TC-
4
Verify
correct
detail
User enters the
username and
password correctly
Redirect to player
home page
Redirect to
player home
page
Pass

Tournament Login
Table 6.1.1.3 Testing of Tournament Login
TC
ID
Actual
O/P
Test
Resul
t
TC-
1
Validate
username
and
password
User enters
username &
password to login
himself
System verifies the
username and
password
System
verifies the
username
and
password
Pass
TC-
2
Verify
incorrect
detail
User enters either
the username or the
password or both
incorrectly
System prompts
with the message
“Relogin”
System
prompts
with the
message
“Relogin”
Pass
TC-
3
Verify of
blank field
User leaves the
email-id and
password Blank
System prompts the
message
field”
System
prompts the
message
“Please fill
in this field”
Pass
TC-
4
Verify
correct
detail
User enters the
username and
password correctly
Redirect to
tournament home
page
Redirect to
tournament
home page
Pass

Player registration
Table 6.1.1.4 Testing of Player
TC
ID
TC
Name
Actual
O/P
Test
Resul
t
TC-1 Verify
form
detail
User enters
all fields
according to
format.
System verifies all
field and system
prompts message
“You have
successfully register”
System verifies
all field and
system prompts
message “You
have successfully
register”
Pass
TC-2 Verify
incorrect
detail
User enters
field invalid
format for
registration
System prompts with
the message at that
filed “Please match
the requested format”
System prompts
with the message
at that filed
“Please match the
requested format”
Pass
TC-3 Verify of
blank
field
User leaves
filed and
click to
submit button
System prompts with
the message at that
filed “Please fill in
this filed”
respectively.
System prompts
with the message
at that filed
filed”
respectively.
Pass

Tournament registration
Table 6.1.1.5 Testing of Tournament
TC
ID
TC
Name
Actual
O/P
Test
Resul
t
TC-1 Verify
form
detail
User enters
all fields
according to
format.
System verifies all
field and system
prompts message
“You have
System verifies
all field and
system prompts
message “You
have successfully
register”
Pass
TC-2 Verify
incorre
ct detail
User enters
field invalid
format for
registration
System prompts with
the message at that
System prompts
with the message
at that filed
“Please match the
requested format”
Pass
TC-3 Verify
of
blank
field
User leaves
filed and
click to
submit button
System prompts with
the message at that
this filed”
respectively.
System prompts
with the message
at that filed
filed”
respectively.
Pass

Team registration
Table 6.1.1.6 Testing of Team
TC
ID
TC
Name
Actual
O/P
Test
Resul
t
TC-1 Verify
form
detail
User enters
all fields
according to
format.
System verifies all
field and system
prompts message
“You have
System verifies
all field and
system prompts
message “You
have successfully
register”
Pass
TC-2 Verify
incorre
ct detail
User enters
field invalid
format for
registration
System prompts with
the message at that
System prompts
with the message
at that filed
“Please match the
requested format”
Pass
TC-3 Verify
of
blank
field
User leaves
filed and
click to
submit button
System prompts with
the message at that
this filed”
respectively.
System prompts
with the message
at that filed
filed”
respectively.
Pass

Functionality testing of the system
Table 6.1.1.7 Testing of Functionality
TC
ID
Actual
O/P
Test
Resul
t
TC-1 Add Player Team leader
add player to
team
Player added to
team and request
given to the
player
Player added to
team and request
given to the
player
Pass
TC-2 Match
Scheduling
In
Tournament,
Registered
team is
scheduled
Teams are
scheduled by
automatic or
manually.
Teams are
scheduled by
automatic or
manually.
Pass
TC-3 Notification
to player
Player get
notification
Player gets
notification as
reminder on
match day.
Player get
notification as
reminder on
match day.
Pass
TC-4 Statistics Display team
score
Team score
display at end of
the match
Team score
display at end of
the match
Pass

6.1.2 Result Analysis
Table 6.1.2 Result Analysis
Sr
No.
Module
Load Time
(sec)
Accuracy
(%) Status
1 Login 1.5 100 Complete
2 Registration 1.70 100 Complete
3 Scheduling 3.75 80 Complete
4 Notification 5 100 Complete
6.2 Advantages
Our application is useful for Tournament Owner and player. It will reduce paperwork
for Tournament Organizer. System will provide match scheduling. It is also provide
notification to player.
6.3 Usefulness with respect to Existing System
There is offline registration in existing system but, our System provides online
registration for manage tournament.
6.4 Unique feature of project
1. System provides automatic or manual match scheduling.
2. It provides notification to player in android application.
3. It provides statistics of match.

CHAPTER 7
FUTURE ENHENCEMENT
There is wide scope for expansion of this project. The following are aspect of this
project which is explained below.
1. In website, online payment for player can be implemented.
2. Live score update during live match and guest user can view score of live
matches.
3. Tournament Owner side module can be implemented in Android Application.
4. Expansion of Android application can be implemented.
5. There is also possibility of application for windows phone and IOS.

CONCLUSION
In our proposed system, system will allow to create multiple tournament 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 get notification before start of the match as a
reminder. Admin upload news and gallery. Admin can manage news and gallery. It will
avoid duplication of tournament for a player, team and game.

REFERNCES
[1] Mortimer, Robert G. (1999). Mathematics for Physical Chemistry. Academic Press.
[2] Dinitz, Jeff (13 November 2004). "Designing Schedules for Leagues and
Tournaments" (PDF). Home Page for Jeff Dinitz. Mount Saint Mary College: GRAPH
THEORY DAY 48.
[3] Bourque, P.; Fairley, R.E. (2014). "Guide to the Software Engineering Body of
Knowledge (SWEBOK)". IEEE Computer Society.
[4] Gluskin, Michael (March 23, 2005). "The tournament trim"
[5] www.cricketgraph.com
[6] www.wikipedia.com/scheduling
[7] www.victroclub.com
[8] http://www.tutorialspoint.com/uml/uml_class_diagram.htm
[9] http://en.wikipedia.org/wiki/Class_diagram
[10] http://en.wikipedia.org/wiki/Collaboration_diagram

APPENDIX

GIC Patent Drafting Exercise Team ID: 45252
GTU Innovation Council
Patent Drafting Exercise (PDE)
FORM 1 (FOR OFFICE USE ONLY)
THE PATENTS ACT 1970 Application No:
(39 OF 1970) Filing Date:
& Amount of Fee paid:
THE PATENTS RULES, 2003 CBR No:___________________
APPLICATION FOR GRANT OF PATENT
1. Applicant(s) :
ID Name Nationality Address Mobile No. Email
1 Prajapati Dilip
Joitaram
Indian Computer Science & Engineering
,
F a c u l t y O f E n g i n e e r i n g
,Technology And Research.
Bardoli, Surat ,
Gujarat Technologycal University.
9429730066 dilipprajapati94@gmail.
com
2 Amrani Rahul
Ashokbhai
,
Bardoli, Surat ,
9638690892 amrani_rahul@yahoo.c
om
3 Maisuriya Vinodkumar
Manharbhai
,
Bardoli, Surat ,
9033232901 vinodmm143@gmail.co
m
4 Patidar Nikhilkumar
Narayanbhai
,
Bardoli, Surat ,
9033587469 patidar.nikhil48@gmail.
com
2. Inventor(s):
ID Name Nationality Address Mobile No. Email
1 Prajapati Dilip
Joitaram
,
Bardoli, Surat ,
9429730066 dilipprajapati94@gmail.
com
2 Amrani Rahul
Ashokbhai
,
Bardoli, Surat ,
9638690892 amrani_rahul@yahoo.c
om
Note : This is just a mock Patent Drafting Exercise (PDE) for semester 8, BE students of GTU.These documents
are not to be submitted with any patent office.
Page 1

3 Maisuriya Vinodkumar
Manharbhai
,
Bardoli, Surat ,
9033232901 vinodmm143@gmail.co
m
4 Patidar Nikhilkumar
Narayanbhai
,
Bardoli, Surat ,
9033587469 patidar.nikhil48@gmail.
com
3. Title of Invention/Project:
4. Address for correspondence of applicant/authorized patent agent in india
Name: Patidar Nikhilkumar Narayanbhai
Address: Computer Science & Engineering , Faculty Of Engineering ,Technology And Research. Bardoli, Surat ,
Gujarat Technological University.
Mobile: 9033587469
Email ID: patidar.nikhil48@gmail.com
5. Priority particulars of the application(S) field in convention country
Country Application No. Filing Date Name of the Applicant Title of the Invention
N/A N/A N/A N/A N/A
6. Particulars for filing patent co-operation treaty (pct) national phase Application
International application number International filing date as alloted by the receiving office
N/A N/A
7. Particulars for filing divisional application
Original(First) Application Number Date of filing of Original (first) application
N/A N/A
8. Particulars for filing patent of addition
Original(First) Application Number Date of filing of Original (first) application
N/A N/A
9. DECLARATIONS:
(i) Declaration by the inventor(s)
I/We, the above named inventor(s) is/are true & first inventor(s) for this invention and declare that the applicant(s).
herein is/are my/our assignee or legal representative.
Date : 2 - April - 2016
Name Signature & Date
Page 2

1 Prajapati Dilip Joitaram ______________
2 Amrani Rahul Ashokbhai ______________
3 Maisuriya Vinodkumar Manharbhai ______________
4 Patidar Nikhilkumar Narayanbhai ______________
(ii) Declaration by the applicant(s) in the convention country
I/We, the applicant (s) in the convention country declare that the applicant(s) herein is/are my/our assignee or legal
representative.applicant(s)
(iii) Declaration by the applicant(s)
I/We, the applicant(s) hereby declare(s) that:-
I am/We in possession of the above mentioned invention.
The provisional/complete specification relating to the invention is filed with this aplication.
The invention as disclosed in the spcification uses the biological material from India and the necessary
permission from the competent authority shall be submitted by me/us before the grant of patent to me/us.
There is no lawful ground of objection to the grant of the patent to me/us.
I am/we are the assignee or the legal representative of true & first inventors.
The application or each of the application,particulars of each are given in the para 5 was the first applicatin
in the convention country/countries in respect of my/our invention.
I/we claim the priority from the above mentioned applications(s) filed in the convention country/countries &
state that no application for protection in respect of invention had been made in a convention country before
that date by me/us or by any person
My/Our application in india is based on international application under Patent Cooperation Treaty (PCT) as
mentioned in para 6
The application is divided out of my/our application(s) particulars of which are given in para 7 and pray that
this application may be treated as deemed to have been filed on ___________under section 16 of the Act.
The said invention is an improvement in or modification of the invention particulars of ehivh are given in para
8.
10. Following are the attachments with the application:
(a) Provisional specification/Complete specification
(b) Complete specification(In confirmation with the international application) / as amended before the
international Preliminary Examination Authority (IPEA),as applicable(2 copies),No.of pages.....No.of
claims.....
(c) Drawings (In confirmation with the international application)/as amended before the international
Preliminary Examination Authority(IPEA),as applicable(2 copies),No.of sheets....
(d) Priority documents
(e) Translations of priority documents/specification/international search reports
(f) Statement and undertaking on Form 3
(g) Power of Authority
Page 3

(h) Declaration of inventorship on Form 5
(i) Sequence listing in electronic Form
(j) ........................................ Fees Rs.XXX in Cash /Cheque/Bank Draft bearin No.XXX Date: XXX on XXX
Bank.
I/We hereby declare that to the best of my /our knowledge, information and belief the fact and mtters
stated herein are correct and I/We request that a patent may be granted to me/us for the said invention.
Dated this 2 day of April , 2016
Name Signature & Date
1 Prajapati Dilip Joitaram ______________
2 Amrani Rahul Ashokbhai ______________
3 Maisuriya Vinodkumar Manharbhai ______________
4 Patidar Nikhilkumar Narayanbhai ______________
Page 4

FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
&
THE PATENTS RULES, 2003
PROVISIONAL SPECIFICATION
1. Title of the project/invention :
2. Applicant(s) :
Prajapati Dilip Joitaram ( Indian )
Address : Computer Science & Engineering , Faculty Of Engineering ,Technology And Research. Bardoli, Surat ,
Amrani Rahul Ashokbhai ( Indian )
Maisuriya Vinodkumar Manharbhai ( Indian )
Patidar Nikhilkumar Narayanbhai ( Indian )
3. Preamble to the description :
The following specification describes the invention.
4. Description :
a. Field of Application / Project / Invention :
Computer Science
b. Prior Art / Background of the Invention / References :
The main purpose of this is that to easy for tournament organizer to manage their tournament.It is easy for manage
player,team and score record.
c. Summary of the Invention/Project :
Our project topic is Sport Tournament Management System.Our project is helpful for tournament organizer and player
to manage tournament.Player can view there record.Our project is also provide to manage multiple tournament.Player
get notification as a reminder before start of the tournament.
d. Objects of the Invention/Project :
Registration for player and tournament
Login for player and tournament
Match Scheduling
Score of matches
Notification to player
e. Drawing(s) :
f. Description of the Invention :
Page 1

Registration-In this Player and Tournament can register for login
Login- Player and Tournament can login and do their further process
Match scheduling-In this match will schedule
score of matches - In this player score and team score will be displayed
notification- In this notification will provide
g. Examples :
h. Unique Features of the Project :
NIL
5. Date & Signature :
Date :2 - April - 2016
____________________ ____________________
Sign and Date Sign and Date
Prajapati Dilip Joitaram Amrani Rahul Ashokbhai
____________________ ____________________
Maisuriya Vinodkumar
Manharbhai
Patidar Nikhilkumar
Narayanbhai
6. Abstract of the project / invention :
Our project provide solution to problems like offline registration,manage single tournament,manage log of player,team
and tournaments.It is also difficult to remind player incase player forget match day.so our proposed system provide
different tournament,match scheduling and provide notification to player via android application.
Drawing Attachments :
Page 2

FORM 3
THE PATENTS ACT, 1970
(39 OF 1970)
&
THE PATENTS RULES, 2003
STATEMENT AND UNDERTAKING UNDER SECTION 8
1. Declaration :
I/We, Prajapati Dilip Joitaram ,
Amrani Rahul Ashokbhai ,
Maisuriya Vinodkumar Manharbhai ,
Patidar Nikhilkumar Narayanbhai
2. Name, Address and Nationality of the joint Applicant :
Prajapati Dilip Joitaram ( Indian )
Address :Computer Science & Engineering , Faculty Of Engineering ,Technology And Research. Bardoli, Surat ,
Amrani Rahul Ashokbhai ( Indian )
Maisuriya Vinodkumar Manharbhai ( Indian )
Patidar Nikhilkumar Narayanbhai ( Indian )
Here by declare :
(i) that I/We have not made any application for the same/substantially the same invention outside India.
(ii) that the right in the application(s) has/have been assigned to,
Name of the
Country
Date of
Application
Application
Number
Status of the
Application
Date of
Publication
Date of Grant
N/A N/A N/A N/A N/A N/A
(iii) that I/We undertake that up to the date of grant of patent by the Controller , I/We would keep him inform in writing the
details regarding corresponding application(s) for patents filed outside India within 3 months from the date of filing of
such application.
Dated this 2 day of April , 2016
3. Signature of Applicants :
____________________ ____________________
Prajapati Dilip Joitaram Amrani Rahul Ashokbhai
Page 1

____________________ ____________________
Maisuriya Vinodkumar
Manharbhai
Patidar Nikhilkumar
Narayanbhai
To
The Controller of Patent
The Patent Office, at Mumbai.
Page 2

4/2/2016 Plagiarism Checker | Viper Free Plagiarism Checker and Scanner Software
file:///C:/Users/Akshay/Desktop/Report_stmsnik.doc.html 1/9
Contact us | Universities | History | Testimonies | Press | About us | Sitemap | Help | Essay help | RSS | Log in
Plagiarism Report For 'stmsnik.doc'
How does Viper work.....?
[+] Read more..
Location Title
Words
Matched
Match
(%)
Unique
Words
Matched
Unique
Match
(%)
Documents found to be plagiarised
https://en.wikibooks.org/wiki/Introduction_to_Software_Engineering/UML Introduction to Software Engineering/UML - Wikibooks 24 1 24 1
https://en.wikipedia.org/wiki/Entity-relationship_model Entity–relationship model - Wikipedia, the free encyclopedia 59 1 59 1
https://en.wikipedia.org/wiki/Round-robin_tournament Round-robin tournament - Wikipedia, the free encyclopedia 22 1 22 1
http://www.wow.com/wiki/Round_robin_tournament Round-robin tournament - WOW.com 22 1 0 <1
http://www.youtube.com/watch?v=EC8zrlMVJAQ Entity--relationship model - YouTube 63 1 4 <1
http://www.bing.com/knows/Round-robin%20tournament Round-robin tournament - 必应 - bing.com 22 1 0 <1
Matching Content: 3%
Master Document Text
CHAPTER
INTRODUCTION OF PROJECT
PhaseI Summary
In PhaseI we have done following activity in our project
Literature Survey
For Literature Survey, We have visited website related to our system. We have also reviewed some patent as a part of PSAR activity for literature
survey. We have visited website www.cricketgraph.com and www.victroclub.com for literature survey
System Analysis
In system analysis part, we have studied about requirement specification of our project. There is included functional and nonfunctional requirement
of our project. We have also designed Software requirement specification called SRS for our system
Canvas
We made four canvas in this phase
AEIOU Canvas
Empathy Canvas
Ideation Canvas
Product Development Canvas
Basic Implementation
In this part, we have made GUI of our project
PhaseII Summary
In PhaseII we will do following activity in our project
Implementation
We will implement our project as per software requirement specification
As given in first phase
Business Model Canvas
We made BMC for strategic management and entrepreneurial tool for allowance to describe, design, challenge, invent and pivot our business model
Testing
We will test all the module of project by many techniques like
Unit Testing
Functional Testing
Performance Testing
Introduction of problem
Nowadays, 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
incase 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
Problem Statement and explanation

Problem Statement
Generally the most of the sport tournament management system, having problems like offline registration, manage single tournament. It is difficult to

manage records of each player profile. There is also problem to manage schedule of the match
Project Description
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 tournament 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

Project useful to Society
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 provide them a single platform for all the details and management of tournament
Technologies Requirements

We want to develop this project in PHP Programming language and also android for mobile application.so, we need following requirement

Nusphere for PHP
Android SDK and Eclipse for android
MYSQL for Database
Wampserver

Background theory
Tournament Owner will organize tournament and advertise it to interested team

Tournament Owner will start the registration of limited team as per his requirement

Tournament Owner manage paperwork for player detail and team detail for record of the tournament

Tournament Owner display Rules and Regulation of tournament to every team

Tournament Owner create match scheduling and give it to every team by Phone call or message

Tournament Owner provide score after end of the match

Final team will win the tournament and give trophy to that team or prize
Money
Dealing with paperwork, phone calls, emails and letters
CHAPTER
LITERATURE REVIEW

EXISTING SYSTEM
www.cricketgraph.com

In this website, user can view tournament by name. User can search tournament by Name. User can view team score and player score for each match. Here
match scheduling is not generate automatically. It generates manually. User can see rules and regulation of match. Player are also group member of

club. It is also provide news and blog and it updates at the certain time of interval. Following is the screenshot of this system
Figure 2.1.1.1 Screen shots of Cricketgraph
Figure 2.1.1.1 Screen shots of Cricketgraph (player
www.victroclub.com

This system is only limited to only single tournament. It manage only single tournament. Player can view their profile by logging in the system
System provides player log, tournament logs, news etc. There is no multiple games support. And it is static website
Figure 2.1.2.1 Screen shots of Victroclub

Figure 2.1.2.2 Screen shots of Victrograph (team

Comparative statements from survey
Table.2.2 Comparative statement of survey

Functionalities Existing Proposed Registration Offline Online Scheduling Manually Manually/auto Statistic Yes Yes Notification No Yes Android

app No Yes Manage data Offline Online

Motivation from Survey
After studied different website related to sport management system we can say that there are different methodology and techniques to implement this

kind of system. But, we are thinking about make a system that includes multiple sport management. So, different sport management and also different

tournament can be managed. We are also making android application that useful to player. Player get notification via android application. So after

literature survey we are fully sure that how can we develop the system which is very useful now a days. And literature survey helps us to find out
different approaches and also motivated us for develops the system

PSAR Summary
Table 2.4: PSAR

Sr no. Patent_Id Description 1 US 20080280663 A1 User can registration in multiple gaming and it’s include hierarchical rounds that include at least

first round and second round. 2 US 20070191102 Solved the problem of multiple tournament 3 US 20140040239 A1 It can manage scheduling and organize

tournament. 4 US 2014004023 A1 The statistics being related to provide statistics levels comparison at least game
CHAPTER
SYSTEM ANALYSIS

Introduction
Purpose

The purpose of this document is to provide the reader with general, background information about the software sports
Scope
This document is intended for all the users to understand the usage and maintenance of the software who will know about the basic knowledge of
computer
Documentation Conventions
Throughout this documentation, the following conventions have been used
Fonts: Times New Roman

Size 16 for Main
Size 14 for Sub
Size 12 for the Rest of the
OVERALL DESCRIPTION
Product Perspective
The STMS is replacement for sport management system which depend on Paperwork for team and tournament registration. This project provides match
scheduling and player profile, team and player registration
Product Function
Tournament Registration

In registration function, new tournament create 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
Constraint, Assumptions and Dependencies
MSSql server will be used as a sql engine and database User may access system from any computer that has internet connection. User must have to
enter correct username and password
Special Requirement
User Interface
There is three different user interfaces in this system. That is one for Tournament one for player and one for administrator

Hardware Interface
Mobile phone for player to view notification
Software Interface
Any Windows based operating system (Windows XP
Wamp Server Package and Xamp Server Package

Android Studio (eclipse Luna) and PHP (NuSphere PhpED
Communication Interface
Internet is required
Functional Requirement
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

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

Admin
Admin can upload news
Admin can approve player and tournament
Admin manage all data
Other nonfunctional Requirement
Error handling
This Product shall handle expected and nonexpected errors in ways that prevent loss information and long downtime period
Authentication Requirements
System checks username and password every time when user log in to the system and System give different type of privilege to different users

Security Requirements
System will use secured database normal users can just read information but they cannot edit or modify anything. System will have different types of

users and every user has access constraints
CHAPTER

SYSTEM DESIGN
System Flow Chart Diagram
Tournament Flow

Figure 4.1.1 System Flow for
System Flow for Player
Figure 4.1.2 System Flow for
UML Diagram
Unified Modeling Language (UML) combines techniques from data modeling (entity relationship diagrams) and component modeling. It can be used with all
processes, throughout the software development life cycle, and across different implementation technologies

Usecase Diagram
Figure 4.2.1: Use case Diagram of
Class Diagram
In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of static structure diagram
Figure 4.2.2 Class Diagram of
Sequence Diagram
When an object passes a message to another object, the receiving object might in turn sends a message to another object, and so on. This stream of
message forms a sequence. The messages are ordered in sequence by time. Sequence diagram models these sequences. A sequence diagram describes a
pattern of interaction among objects, arranged in a chronological order. It shows the objects participating in the interaction by their “lifelines

and the message that they send to each other
Figure 4.2.3: Sequence Diagram of
Activity Diagram
Activity diagram represent the dynamics of the system. It focuses on representing various activities or chunk of processing and their sequence of
activities. Activity diagram are used to show the work flow of a system
Activity for Player
Figure 4.2.4.1.: Activity Diagram for
Activity for Tournament

Figure 4.2.4.2: Activity Diagram for Tournament

State Chart Diagram
Player
Figure 4.2.5.1 : State Chart for
State chart for Tournament

Figure 4.2.5.2: State chart for Tournament

Collaboration Diagram
A collaboration diagram describes interactions among objects in terms of sequenced messages. Collaboration diagrams represent a combination of
information taken from class, sequence, and use case diagrams describing both the static structure and dynamic behavior of a system
Figure 4.2.6 Collaboration Diagram of
Component Diagram
Figure 4.2.7 Component Diagram of
Database Design
ER Diagram
An entity–relationship model (ER model) is a data model for describing the data or information aspects of a business domain or its process
requirements, in an abstract way that lends itself to ultimately being implemented in a database such as a relational database. The main components
of ER models are entities (things) and the relationships that can exist among them, and databases
Figure 4.3.1 ER Diagram of STMS
Data Dictionary
Table 4.3.2.1:

Column Name Data Type Size Constrains Description p_id int 10 pk,not null Player id uname varchar 100 not null Player User Name ps varchar 100 not

null Password pi varchar 100 not null Player Image fname varchar 100 not null Player First Name mname varchar 100 not null Player Middle Name
lname varchar 100 not null Player Last Name gnd varchar 100 not null Gender pno varchar 100 not null Phone No eid varchar 100 not null Email Id
dob date not null Date Of Birth state varchar 100 not null State distic varchar 100 not null District block varchar 100 not null Block Or City
addr varchar 100 not null Address pin varchar 100 not null Pincode status enum not null Status gtype varchar 100 not null Game Type

Table 4.3.2.4:

Column Name Data Type Size Constrains Description b_id Int 10 not null,pk Block id s_id Int 100 not null,fk State id d_id Int 100 not null,fk

Distic id sname Varchar 100 not null State Name dname Varchar 100 not null Distic Name bname Varchar 100 not null Block Name

Table 4.3.2.3:

Column Name Data Type Size Constrains Description a_id Int 10 not null Admin user id uname varchar 100 not null Admin user name Ps varchar 100 not

null Admin Password
Table 4.3.2.2:

Column Name Data Type Size Constrains Description t_id Int 10 pk,not null Team id uname varchar 100 not null User Name ps varchar 20 not null

Password to_id Int 10 not null Tournament id tname varchar 100 not null Tournament name logo varchar 100 not null Tournament Logo pno varchar

not null Phone Number eid varchar 100 not null Email id state varchar 100 not null State distic varchar 100 not null District block varchar

not null Block addr varchar 100 not null Address pin varchar 100 not null Pin status Enum Player Status tou_status Enum Tournament Status

Table 4.3.2.5:

Column Name Data Type Size Constrains Description d_id Int 10 not null,pk District id s_id int 10 not null,fk State id sname varchar 100 not null

State Name dname varchar 100 not null District Name
Table 4.3.2.6:

Column Name Data Type Size Constrains Description s_id int 10 not null,pk State id sname varchar 100 not null State Name

Table 4.3.2.8:

Column Name Data Type Size Constrains Description to_id int 10 not null,pk Tournament Id uname varchar 100 not null Uesrname ps varchar 100 not

null Password ttype varchar 100 not null Tournament Type tname varchar 100 not null Tournament name logo varchar 100 not null Tournament Logo

tsdate date not null Tournament Stating Date tedate date not null Tournament Ending Date rsdate date not null Registration Starting Date Redate

date not null Registration Ending Date Pno varchar 100 not null Phone no Eid varchar 100 not null Email Id state varchar 100 not null State
distic varchar 100 not null District block varchar 100 not null Block addr varchar 100 not null Address Pin varchar 100 not null Pincode status
enum not null Status not Varchar 150 not null Notice

Table 4.3.2.7:

Column Name Data Type Size Constrains Description Id int 10 not null,pk Game id gtype varchar 100 not null Game Type

Table 4.3.2.9: tona_match

Column Name Data Type Size Constrains Description Id int 10 not null,pk Id to_id int 10 not null,fk Tournament Id t1 int 10 not null Team 1 t

int 10 not null Team 2 Dt date not null Date Ti time not null Time win varchar 100 null Winner Team

Table 4.3.2.10: t_player

Column Name Data Type Size Constrains Description id int 10 not null,pk Id to_id int 10 not null,fk Tournament Id t_id int 10 not null,fk Team Id

p_id int 10 not null,fk Player Id status enum not null Player Status
Table 4.3.2.11:

Column Name Data Type Size Constrains Description ne_id int 10 pk,not null News id ne_description varchar 500 not null News Description ne_date

varchar 20 News date
Table 4.3.2.12:

Column Name Data Type Size Constrains Description no_id int 10 pk,not null Notice id to_id int 10 fk,not null Tournament id no_description varchar

not null Notice Description
Table 4.3.2.12:

Column Name Data Type Size Constrains Description no_id int 10 pk,not null Notice id to_id int 10 fk,not null Tournament id msg varchar 500 not

null Notice Message date date not null Date team1 varchar 100 not null Team 1 team2 varchar 100 not null Team

Data Flow Diagram
Level0 DFD
Figure 4.3.3.1 Level 0
Level1 DFD
Level2 Tournament

Level3 Player
Level4 Team leader

Figure 4.3.3.5 Level 4 of
Canvas
AEIOU Summary Canvas
Figure 4.4.1 AEIOU
Empathy Canvas
Figure 4.4.2 Empathy
Ideation Canvas
Figure 4.4.3 Ideation
Product Development Canvas
Figure 4.4.4 Product Development
Business Model Canvas
Figure 4.4.5: Business model
CHAPTER
IMPLEMENTATION

Home Page
Below page is the home page of website. In Home page, there are links navigate to login, registration, player detail and tournament detail
Figure 5.1 Home Page of
Player Registration
Player fills all detail and register in the system
Figure 5.2 Player
Tournament Registration

Tournament is register in the system by a tournament owner

Figure 5.3 Tournament

Team Registration

Team leader fill all detail for new team in tournament

Figure 5.4 Team

Player Detail
Guest user can view all registered player
Figure 5.5 Player
Tournament Detail

Guest user can view all registered Tournament


Player Login
Registered Player can log in to system
Figure 5.7 Player
Tournament Login

Only Registered Tournament is log in in to the system


Login Player Detail
Player can change their profile and view team request
Figure 5.9 Login Player
Player Edit Profile
Player can change his profile if player wants to change his profile
Figure 5.10 Player Edit
Player Change Profile Picture
Player can change profile picture if player wants
Figure 5.11 Player Change Profile

Tournament Detail

After log in to the tournament, user can view registered team, create match and upload score

Match Schedule
User can schedule the match manually for registered team
Figure 5.13 Match
Automatic match schedule
Match scheduling will done automatically
Figure 5.14 Match
Player Score Input
Figure 5.15 Player Score
Team Scoreboard

Player score is uploaded for particular team and tournament
Figure 5.16 Team

Tournament Edit Profile

User can edit his profile
Figure 5.17 Tournament Edit

Tournament Change Logo

User can change tournament logo
Figure 5.18 Tournament change

Team Detail

After log in to the tournament, user can view team detail
Figure 5.19 Team

Add Player
Team leader search all player and add player in his team just after player gives conformation to team

Figure 5.20 Add
View Requested Player

Team leader can view requested player and his status. He can also delete requested player

Figure 5.21 View Requested

View Team Player

Team leader view player list that are given conformation to team

Figure 5.22 View Team

Contact Us
Guest user can contact to Administrator by giving his detail
Figure 5.23 Contact
Android Login Screen for Player
Android application is only for player. Player can log in to the application by giving his username and password same as given in website

Figure 5.24 login for
Android Login Screen for Player Home Screen
This is the home screen for player. Player can view his profile and also player get notification about his match

Figure 5.25 player
Android Notification to player screen
Player view his profile but can’t edit them. It is only editable in web application
Figure 5.26 player home
Android Notification to player screen
Player get notification and view the notification

SPORT TOURNAMENT MANAGMENT SYSTEM (STMS)

SPORT TOURNAMENT MANAGMENT SYSTEM (STMS)

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to SPORT TOURNAMENT MANAGMENT SYSTEM (STMS)

Similar to SPORT TOURNAMENT MANAGMENT SYSTEM (STMS) (20)

Recently uploaded

Recently uploaded (20)

SPORT TOURNAMENT MANAGMENT SYSTEM (STMS)