SEMINAR

Cricket Score Board

Submitted by:
Indrajeet Sahu [17BC005]
Manohar Kr. Gupta [17BC017]
BCA 5th Semester
Guided by:
Linuskrishna Rajbongshi
Dept. Computer Science
North Lakhimpur College
topic:

Introduction
Purpose of the Project
Scope of the Project
Data Flow Diagram
Context Diagram
Level 1 DFD
ER Model
System Testing
Limitation and Future Scope
Conclusion
References
Introduction:

This project entitled as “Cricket Score Board” will help to count the score in
cricket matches, which removes the complexity of teams, player, runs, balls over
separately for each player from different teams.
In this project we computerize and keeps the track the status of each player.
The system is developed using HTML, PHP, JavaScript coding and also web server
like MySql, Apache.
Purpose of the project:
The “Cricket Score Board” is a web based application which use to store the team
players runs, balls, over separately. The main purpose of the application is to count the
score and store runs temporarily and keeping updating of each and every runs, balls and
over till the end of the innings until game is not completed.

scope of the project:

It provides easy updating technique of the cricket scores of each match in simple way.
Alert a message when any batsmen get out.
Updating the runs, balls, over easily.
The scope of project is to maintain the scores of each player from different teams.
data flow diagram (dfd):
 The DFD presented a picture of what is being specified and is a conceptually easy to
understand application.
 The process is partitioned so that we have a clear picture of the progress general to
the specific in the system flow.
 It is logical than physical. It specifies in a precise, concise and a highly readable
manner the working of the system.
It calls for a rigorous study of the user domain.
Level of DFD are:
Level 0 DFD
Level 1 DFD
Level 2 DFD
Level 3 DFD
Context diagram:
The Context Diagram is the most abstract data flow representation of the system. It
represents the entire system as a single bubble. The bubble is labeled according to the
main function of the system. The various external entities with which the system
interacts and the data flows occurring between the external entities are also represented.
The context diagram is also called level 0 DFD.

Batsman Total Runs,

Batsman performance Runs, Balls,
Wickets, Over’s,
Separate run for
Each Updated
Keeping Score Board
Updating
Bowler performance

Bowler

Fig. Level 0 DFD

 Updated
Score Board

2.1
Total 2.3
Run 1
Over
Status
Updating
Process

2.5
Separate
Run 2.2
Ball
2.4
Wkt

Making
runs Playing Keep
Balls Balling

Batsman Bowler
Level 1 DFD
Entity relationship model:
The most important consideration in designing the database is how the information
will be used. The various applications and procedures that will use the database
introduce the requirements upon the structure of the data.
First plan is what tables that we required and what data they will contain. It also
determines how the tables are created, it’s the most important step and deserve careful
observation.
ER Daigram
relationship scheme:
In a data model it is important to distinguish between the description of the
database and the database schema is specified during the database is called the database
scheme. A database scheme is specified during the database design and is not expected
to change frequently. Most data model has certain convention for diagrammatically
displaying the schemas. The displays only some aspects of a schema such as name of
record types and data items and some types of constrains.
 
Schema Design
System testing:
The testing phase is an important part of the software development. It is the
process of finding errors and missing operations and also a complete verification to
determine whether the objectives are met and the user requirements are satisfied.

Unit Testing:
The first includes unit testing, where each module is tested individually and if any
errors are found then it was corrected.
results from which correctness of the unit testing is confirmed.
Integration Testing:
The module is a part of “Cricket”, when the module is run individually and
showing the perfect scores. The individual module is clipped under the system module
and tested again and verified the scores.
Validation:
The final step involves validation and testing which determines whether the
module functions as the user expected.
Limitation and future scope:
SQL query injection problem is not taken care of, it has to be corrected.
Auto increment of runs, balls, over in each balls
Auto updated of runs in score board.
Auto update of changing batsman and bowler.
We need more to do better in our project database.
conclusion:
This system in the current scenario completely meets the requirement which
was set when this project was conceived. It will help the empire and the cricket
tournament committee to reduce the complexity of scores keeping updating
manually. Still this project will help a lots of tournament committee to count the
score in each and every matches, see the records of recent matches. In other hand
it’s very easy to maintainable.
 
References:

www.w3schools.com
www.en.wikipedia.org
www.webdeveloper.com
www.phpeasystep.com
https://www.youtube.com/watch?v=ymQu4hAZ0vQ
https://www.youtube.com/watch?v=lDExf7wyyJU
https://www.youtube.com/watch?v=dZR448LHMy4
THANK YOU
VERY MUCH