Table of Contents

1
Table of Content

1. INTRODUCTION
1.1 Purpose and background
1.2 Structure
1.3 Parameters of the project
1.4 RELATED WORK

2. OBJECTIVES AND SCOPE

2.1 Purpose
2.2 Scope

3. METHODOLOGY
3.1 OVERVIEW OF METHODOLOGY
3.1.1 MANAGING THE TORNAMENT
3.1.2 MANAGING THE MATCH
3.1.3 UPDATING THE MATCH
3.1.4 END OF THE MATCH
3.1.4 DISPLAYING THE MATCH

4. System Analysis
4.1.1 Performance Requirements
4.1.2 System Requirements
4.1.3 Acceptance Criteria

5. FEASIBILITY STUDY
5.1 Economic Feasibility:
5.2 Technical Feasibility:
5.3 Behavioral Feasibility:
5.4 Proposed System Functionality

6. System Design
6.1 DESIGN GOALS
6.2 FUNCTIONAL FLOW OF THE SYSTEM
6.3 ENTITY RELATIONSHIP DIAGRAM
6.4-DATA FLOW DIAGRAM

2
 6.5-TABLE DESIGN
6.6 SYSTEM FLOW CHART
6.7 SYSTEM SCREENS AND FORMS

7. Technology Introduction
7.1 MySQL
7.2 HTML
7.3 CSS
7.4 JavaScript
7.5 jQuery
7.6 PHP

8. Testing and Debugging

8.1 Goals and Objectives
8.2 Statement of scope
8.3.Test Case
8.4 Testing Process
8.5 Debugging

9. Implementation
9.1 Conversion
9.2 Direct Implementation

10. Scope and Limitation

10.1 Scope of the proposed System
10.2 Limitation of the Proposed System

11. Conclusion

12. References

3
Abstract

4
Project Title : Cricket Score App

Abstract : The project has been developed to keep track of detailed Score of the cricket
match.. The current product is paper based system where scorer has to maintain the score by pen
and paper manually. The product will take care of all the team, players. Leagues and matches

‘Managing’ a cricket tournament is not as simple as it looks. When managing cricket

tournaments, tournament administrators go through a painful process of entering match and
tournament information into physical and large data sheets. And, they go through a lot of trouble
to match the teams in a tournament.

With the difficulty of handling a large number of matches manually, there are international level
software’s out there to automate these processes. These systems that are used to manage matches
and tournaments are known as ‘Tournament management systems’.

By using these systems, tournament administrators have achieved a great relief in planning the
match schedules and managing the matches. But those software’s are not available for small and
medium scale club levels, or they are very complex that small clubs tend to stick to the
traditional physical managing systems of club level tournaments.

Therefore, this project offers a flexible and easily adoptable web application for small and
medium sized clubs to easily manage the tournaments.

Tools & Technologies used :

 PHP (Scripting Language)

 MySQL (Relational Database)
 HTML, CSS, Javascript, AJAX

5
Introduction

6
 1. INTRODUCTION

1.1 Purpose and background

When managing cricket tournaments and matches, tournament administrators in the past went through a
painful process to match the teams in a tournament, and to enter match and tournament information into
physical and large data sheets.

With the increasing difficulty of handling a large number of matches manually, there are international
level software to automate these processes. These systems that are used to manage tournaments are
known as ‘Tournament management systems’. By using these systems, tournament administrators have
achieved a great relief in planning the match schedules and managing the matches. But those softwares
are not adoptable by small and medium scale club levels as they are custom made for those parties, and
are not for sale.

Therefore, this project offers a flexible and easily adoptable web application for small and medium sized
clubs to easily manage the tournaments.

1.2 Structure
The report is organized in a way that a complete walk though of the project details are presented. First,
some related work was analyzed and discussed. After understanding the limitations and weaknesses of
those work, a model was designed to get the intended results and intended objectives. Then under a well
planned structure, after identifying objectives and the scope, the project was executed as explained in the
‘methodology’ section in detail.

1.3 Parameters of the project

Our project was a plan of three basic intentions;

1. Storing match and tournament data in a centralized location

2. Showing the real time updates of the match and the tournament
3. Easy match managing system by automatic matching of the teams

7
It is very important that you have a history of data of completed tournaments for many reasons and
situations such as introducing a weight age for the teams in matching teams against each other. And with
our product where a cloud storage would be used to store the tournament data, a club will be able to
securely store and maintain tournament data. It was succeeded by introducing a method of dynamically
generated databases and tables to systematically arrange tournament information in a cloud storage.

As in the internationally played matches, even in club level matches, it is very important to display the
live scores in real time. It was successful with an additional step to display the real time updates of the
player performance in each match as well as in the complete tournament.

Even though we were successful in materializing the first two intentions, with some practical problems
which will be described later, we couldn’t achieve the 3rd objective of the project, to automate the
matching of the teams in each round under the categories of ‘league’ and ‘knockout’.

1.4 RELATED WORK

We could find several products related with the project.

1. http://cricket.jhalak.com is a web application which provides almost the same

features which our Tournament management provides. But the scope of the particular web application is
higher than our system because it’s not only based on Cricket. But our system is specifically based on
Cricket. Because of that, our web application is simple and can be used to manage club level tournaments
as well while it has the ability to \ manage a larger tournament as well. The main difference between these
two web applications is the simplicity.

Features and the structure provided in our system is not complicated for any user.

2. http://scheduler.leaguelobster.com/ is also a similar kind of web application that could be found. But
this only allows the tournament administrator to schedule matches and display the schedule details. But
our system includes match managing methods, tournament managing methods and real time updated
score card as well, making it more supportive and fit for purpose.

8
Objective and Scope

9
 2. OBJECTIVES AND SCOPE

2.1 Purpose
Purpose of this system is to design a simple Cricket Score App, as most of the available
tournament managing systems are complicated for normal users. Also to give the administrative
access for tournament managers, and to provide live updates of the matches for the viewers.

2.2 Scope
The web application product ‘Cricket Score App’ will be an application that will provide the
features of storing all the match data and the tournament details in separate dynamically created
databases, and it’ll show the real time updates of every match with detailed view or in a simple
view on user demand, and finally to provide methods to easily manage matches by placing them
in teams.

But automatically placing the teams in a group gave a practical problem. One of the main
reasons is the inability to place the teams after the first round, because the results the first round
will be deciding the teams of the second round in situations like knockout matches. And also, the
administrator has no details about the past match results. The unavailability of that information
about teams caused this system not to include an automatically pacing teams in groups. But still
this includes a match managing system using manual inputs.

10
Methodology

3. METHODOLOGY

11
3.1 OVERVIEW OF METHODOLOGY

3.1.1 MANAGING THE TOURNAMENT

Log in to the system is given only to the authorized users. They are here by reffer as admin users. When
user name and password are given user have the chance to choose to create a tournament. Here the user
name and passwords are hard coded. User name is ‘user’ and password is ‘password’.

In the Tournament management system we have developed, there is a pre built database called TRMDB
where the details about the tournaments are recorded. Inside this database there is only one table and it is
‘trm’. This entity has only 2 attributes.

TRMDB

When creating a tournament after we give the name of the tournament and number of teams it will
automatically create a database in the name of the tournment. Actualy whole process after this stage is
dynamic. If the name of the tournament is IPL it will automatically create a database called ipl. Inside this
database at the beginning there are tables as matches and teams. Then we have to enter the name of the
teams. According to the name of the teams inside the database automatically tables will be made. Then
the database have tables in the names of teams too.

IPL

If the names of the teams are SL and AUS then there will be tables as follow.

12
Now the process of making the tournament is over. Now we have to manage it by making matches. But
before the mid evaluation the system we developed had this facility to automatically schedule the
tournaments. But due to practical problems like giving weights to the team according to their performance
we had to omit it.

3.1.2 MANAGING THE MATCH

In the above section how a tournament will be made is discussed. Now we have to manage the
tournament by making matches. Here the user will have to enter details about the round and the name of
the ground. Name of the teams can be choose by the dropdown menu and when we proceed a new
database will be automatically made in the name by using the details user gave. If this is a first round
game and teams are SL and AUS. Name of the database will be round1_SL_vs_AUS. In parallel to this
name of the match is entered in to the matches table in the database of the current tournament. Inside the
new database there are tables as inning1, inning2 and players.

3.1.3
UPDA
TING

13
THE MATCH

After we proceed it will give a summary about the match details and then after user proceed there are 2
tabs opened to edit information about match. Only the details about score, wickets, noball, wideball,
batsmen1, batsmen2, bowler are filled by user. System

automatically decide whether it is a ball or not according to the number user gives to the

noball and wideball boxes. This section should be filled ball by ball.

In the batsmen1,batsmen2 and bowler boxes what user has to put is the player ids given to the
playerNumber name playerNumber name id score wickets wideball noball batsment1 batsmen2 bowler
balls id score wickets wideball noball players.

It will be from 1 to 22. 1 to 11 will be given to the team who bats first. And from 12 to 22 will be given to
the team who bowls first.

In the other tab there will be boxes to add information about players. The information in this tab will be
directly related to the players table in the database mention in above section.

Note: if the admin user who enter data logout before the match ends there is a button called manage
current match to get in to the current match and continue updating.

3.1.4 END OF THE MATCH

After match is end a full summary of the match will be displayed. This will include the details about two
innings and player by player information.

3.1.5 DISPLAYING THE MATCH

Information about the match will be displayed in the home page. Innings will be displayed in the screen
with details of total, no of wickets, current batsmen, batsmen in the other side and current bowler. This is
updated using the data from inning1 and inning2 tables. For total, number of wickets and no of overs total
of each column will be selected. Here the number of balls should be displayed as overs for that following
formula was used.

14
CODE LOGIC:

$over1 = $row2["balls"]/6;

$over = floor($row2["balls"]/6);

echo "Over " .$over. "." .($row2["balls"]-6*$over). "<br>";

Furthermore using the details obtained run rate and wickets in hand are calculated using

simple algorithms.

if($over1=='0'){

$runrate='0';

}else{

$runrate = $total/$over1;

$wickHand = '10'-$wicketsT;

echo "##Run Rate: ". $runrate. " ##Wickets in hand: ".$wickHand."<br>";

Along with the current batsmen and bowler their personal information will be displayed for a batsman, his
current score and number of balls faced will be displayed and for the bowler how many overs bowled and
how many wickets taken will be displayed. These data are taken from players table.

Far more to give the big picture of the match there is a button to go to the detailed view of match. In that
view batting and bowling performances of players will be displayed.

Other than creating a match there is a tab for admin users to view the past match summaries. There all the
databases will be used to take information.

15
System Analysis

16
 4. System Analysis

System Analysis refers into the process of examining a situation with the intent of improving it
through better procedures and methods. System Analysis is the process of planning a new
System to either replace or complement an existing system. But before any planning is done the
old system must be thoroughly understood and the requirements determined. System Analysis, is
therefore, the process of gathering and interpreting facts, diagnosing problems and using the
information to re-comment improvements in the System. Or in other words, System Analysis
means a detailed explanation or description. Before computerized a system under consideration,
it has to be analyzed. We need to study how it functions currently, what are the problems, and
what are the requirements that the proposed system should meet.

System Analysis is conducted with the following objectives in mind:

1. Identify the customer’s need.

2. Evaluate the system concept for feasibility.
3. Perform economic and technical analysis.
4. Allocate functions to hardware, software people, database and other system elements.
5. Establish cost and schedule constraints.
6. Create a system definition that forms the foundation for all the subsequent engineering
work.

4.1.1 Performance Requirements

The following performance characteristics should be taken care of while developing the
system:

User friendliness: The system should be easy to learn and understand so that new user can
also use the system effectively, without any difficulty.

User satisfaction: The system should meet user expectations.

Response time: The response time of all the operations should be low. This can be made
possible by careful programming.

17
 Error handling: Response to user errors and the undesired situations should be taken care of
to ensure that the system operates without halting.

Safety: The system should be able to avoid or tackle catastrophic behavior.

Robustness: The system should recover from undesired events without human
intervention.

4.1.2 System Requirements

SOFTWARE REQUIREMENT

 XAMPP Server (with PHP-5)

 MySQL Database Engine
 Windows 7 or Above Operating System

HARDWARE REQUIREMENT

 Pentium IV processor or Above

 1 GB RAM
 40GB HARD DISK

4.1.3 Acceptance Criteria:-

The following acceptance criteria were established for the evaluation of the new system:

User friendliness:- The system should meet user needs and should be easy to learn and
use.

Modularity:- The system should have relatively independent and single function parts .

Maintainability:- The system should be such that future maintenance and enhancements
times and efforts are reduced.

18
Timeliness:- The system should operate well under normal, peak and recovery
conditions.

The system developed should be accurate and hence reliable i.e. The error rate should be
minimized and the outputs should be consistent and correct.

Both the execution time and response time should be negligibly low.

The system should be efficient i.e. the resources utilization should be optimal.

The system should have scope to forsee modifications and enhancements i.e. it should be
able to cope with the changes in future technology.

19
Feasibility Study

20
 5. FEASIBILITY STUDY

All projects are feasible given unlimited resources and infinite time. Unfortunately the
development of computer-based system in many cases is more likely to be plagued by scarcity of
resources and delivery date. Hence, we have made use the concept of reusability that is what
Object Oriented Programming (OOPS) is all about.

The feasibility report of the project holds the advantages and flexibility of the project. This is
divided into three sections:
 Economical Feasibility
 Technical Feasibility
 Behavioral Feasibility

5.1 Economic Feasibility:

Economic analysis is the most frequently used method for evaluating the effectiveness of the
candidate system. More commonly known as cost/benefit analysis, the procedure is to be
determining the benefits and savings that are expected from a candidate and compare them with
costs. If benefits outweigh costs, then the decision is made to design and implement the system.

A systems financial benefit must exceed the cost of developing that system. i.e. a new system
being developed should be a good investment for the organization. Economic feasibility
considers the following

i. The cost to conduct a full system investigation.

ii. The cost of hardware and software for the class of application.

iii. The benefits in the form of reduced cost or fewer costly errors.

iv. The cost if nothing changes (i.e. The proposed system is not developed).

21
The proposed “Cricket Score App” is economically feasible because

i. The system requires very less time factors.

ii. The system will provide fast and efficient automated environment instead

of slow and error prone manual system, thus reducing both time and man

power spent in running the system.

iii. The system will have GUI interface and very less user-training is required

to learn it.

iv. The system will provide service to view various information for proper

managerial decision making.

5.2 Technical Feasibility:

Technical feasibility centers around the existing computer system (Hardware and
Software etc) and to what extend it support the proposed addition. For example, if the
current computer is operating at 80 percent capacity - an arbitrary ceiling - then running
another application could overload the system or require additional Hardware. This
involves financial considerations to accommodate technical enhancements. If the budgets
is a serious constraint ,then the project is judged not feasible. In this project, all the
necessary cautions have been taken care to make it technically feasible. Using a key the
display of text/object is very fast. Also, the tools, operating system and programming
language used in this localization process is compatible with the existing one.

5.3 Behavioral Feasibility:

People are inherently resistant to change, and computers have been known to
facilitate change. An estimate should be made of how strong a reaction the user staff is
likely to have toward the development of a computerized system. Therefore it is
understandable that the introduction of a candidate system requires special efforts to

22
 educate and train the staff. The software that is being developed is user friendly and easy
to learn. In this way, the developed software is truly efficient and can work on any
circumstances, tradition, locales.

Behavioral study strives on ensuring that the equilibrium of the organization and status in the
organization neither are nor disturbed and changes are readily accepted by the users.

5.4 Proposed System Functionality

The proposed system will be designed to support the following features:-

 The proposed system has a user friendly Interface for porting of data to server.
 The proposed system provides the facility to pull the data from the server of the specified
Supply order number and get the respective report.
 The proposed system provides the no replication of data.
 User can get the desired output according to their queries .This is an added advantage.

23
System Design

24
 6. System Design

Designing is the most important phase of software development. It requires a careful planning and
thinking on the part of the system designer. Designing software means to plan how the various parts of
the software are going to achieve the desired goal. It should be done with utmost care because if the phase
contains any error then that will affect the performance of the system, as a result it may take more
processing time, more response time, extra coding workload etc.

Software design sits at the technical kernel of the software engineering process and is applied
regardless of the software process model that is used. After the software requirements have been analyzed
and specified, software design is the first of the three technical activities Designing, Coding and Testing
that are required to build and verify the software. Each activity transforms information in such a manner
that ultimately results in validated computer software.

6.1 DESIGN GOALS

The following goals were kept in mind while designing the system:

Make system user-friendly. This was necessary so that system could be used efficiently and
system could act as catalyst in achieving objectives.

Make system compatible i.e. It should fit in the total integrated system. Future maintenance
and enhancement must be less.

Make the system compatible so that it could integrate other modules of system into itself.

Make the system reliable, understandable and cost-effective.

25
6.2 FUNCTIONAL FLOW OF THE SYSTEM

26
 6.3 ENTITY RELATIONSHIP DIAGRAM

6.4-DATA FLOW DIAGRAM

The Data Flow Diagram shows the flow of data or information. It can be partitioned into single
processes or functions. Data Flow Diagrams can be grouped together or decomposed into multiple
processes.

The DFD is an excellent communication tool for analysts to model processes and functional
requirements. Used effectively, it is a useful and easy to understand modeling tool. It has broad
application and usability across most software development projects. It is easily integrated with data
modeling, workflow modeling tools, and textual specs. Together with these, it provides analysts and

27
 developers with solid models and specs. Alone, however, it has limited usability. It is simple and easy
to understand by users and can be easily extended and refined with further specification into a
physical version for the design and development teams.

The different versions are Context Diagrams (Level 0), Partitioned Diagrams (single process only -- one
level), functionally decomposed, and leveled sets of Data Flow Diagrams.

Data Store
A repository of information. In the physical model, this represents a file, table, etc. In the logical
model, a data store is an object or entity.

Data Flows
DFDs show the flow of data from external entities into the system, showed how the data moved
from one process to another, as well as its logical storage. There are only four symbols:

1. Squares representing external entities, which are sources or destinations of data.

2. Rounded rectangles representing processes, which take data as input, do something to it, and
output it.
3. Arrows representing the data flows, which can either, be electronic data or physical items.
4. Open-ended rectangles representing data stores

There are several common modeling rules for creating DFDs:

1. All processes must have at least one data flow in and one data flow out.
2. All processes should modify the incoming data, producing new forms of outgoing data.
3. Each data store must be involved with at least one data flow.
4. Each external entity must be involved with at least one data flow.
5. A data flow must be attached to at least one process

28
CONTEXT- FREE DIAGRAM ( 0-LEVEL DFD)

1-LEVEL DIAGRAM

29
2-LEVEL DIAGRAM

30
31
6.5-TABLE DESIGN (ER-DIAGRAM)

32
6.6 SYSTEM FLOW CHART

33
6.7 SYSTEM SCREENS AND FORMS

34
35
36
37
38
39
40
41
42
43
44
45
Technology Introduction

46
 7. Technology Introduction

7.1 MySQL
Features of MYSQL:

 Relational Database Management System (RDBMS): MySQL is a relational database

management system.
 Easy to use: MySQL is easy to use. You have to get only the basic knowledge of SQL.
You can build and interact with MySQL with only a few simple SQL statements.
 It is secure: MySQL consist of a solid data security layer that protects sensitive data
from intruders. Passwords are encrypted in MySQL.
 Client/ Server Architecture: MySQL follows a client /server architecture. There is a
database server (MySQL) and arbitrarily many clients (application programs), which
communicate with the server; that is, they query data, save changes, etc.
 Free to download: MySQL is free to use and you can download it from MySQL official
website.
 It is scalable: MySQL can handle almost any amount of data, up to as much as 50
million rows or more. The default file size limit is about 4 GB. However, you can
increase this number to a theoretical limit of 8 TB of data.
 Compatibale on many operating systems: MySQL is compatible to run on many
operating systems, like Novell NetWare, Windows* Linux*, many varieties of UNIX*
(such as Sun* Solaris*, AIX, and DEC* UNIX), OS/2, FreeBSD*, and others. MySQL
also provides a facility that the clients can run on the same computer as the server or on
another computer (communication via a local network or the Internet).
 Allows roll-back: MySQL allows transactions to be rolled back, commit and crash
recovery.
 High Performance: MySQL is faster, more reliable and cheaper because of its unique
storage engine architecture.

47
  High Flexibility: MySQL supports a large number of embedded applications which
makes MySQL very flexible.
 High Productivity: MySQL uses Triggers, Stored procedures and views which allows
the developer to give a higher productivity.

Disadvantages / Drawback of MySQL:

Following are the few disadvantages of MySQL:

 MySQL version less than 5.0 doesn't support ROLE, COMMIT and stored procedure.
 MySQL does not support a very large database size as efficiently.
 MySQL doesn't handle transactions very efficiently and it is prone to data corruption.
 MySQL is accused that it doesn't have a good developing and debugging tool compared
to paid databases.
 MySQL doesn't support SQL check constraints.

7.2 HTML

Introduction to HTML

Background

The HTML5 work stems from the WHATWG ( Web Hypertext Application Technology
Working Group), HTML and their focus is the development of HTML and APIs for web
applications.

What is HTML5?

HTML5 is the new standard for HTML. The previous version of HTML, HTML4.01, came in
1999. The web has changed a lot since then. HTML5 is still a work in progress. HTML5 has
defined a new standard for HTML, XHTML, and the HTML DOM.

48
HTML5 is not something completely new. Most of the HTML5 specifications came from HTML
or HTML1.0. A web browser can read HTML files and compose them into visible or audible
web pages.

Features in HTML5 are

 The DOCTYPE declaration for HTMl5 is very simple, <!DOCTYPE html>

 The character encoding<meta charset=”UTF-8”>
 New function for embedding audio(<audio>), video(<video>), graphics(<svg>
and<canvas>)
 Client-side data storage
 Interactive documents
 New structural elements <article> ,<header>,<footer>,<nav>,<section>,and<figure>
 New from control calendar, date,time,email,url,search
 Java script enhancement
 New HTML5 API’s
 HTML Geolocation, HTML Drag And Drop, html local storage, HTML Application
Cash, HTMl Web Workers, HTML SSE

HTML5 Browser support

The latest versions of Apple Safari, Google Chrome, Mozila Fierbox, Opera, and Microsoft
Internet Expoler 9.0 along with Microsoft Edge, all support many of the new HTML5 features.

In addition, the mobile web browsers that come pre-installed on iPhones, iPads, and Andriod
phones all have support for HTML5.

Specific browsers

 IE9+(Windows
 Firefox3.0+(all operating systems)
 Safari3.0+(Windows, OS X, and iphone OS1.0)
 Chrome 3.0195
 Opera 9.5

49
Example program

1. <!DOCTYPE html>
2. <html>
3.
4. <head>
5. <title> MY FIRST HTML5 DOCUMENT</title>
6. </head>
7.
8. <body>
9. <p>THIS IS NEW HTML5 DOCUMENT</P>
10. </body>
11.
12. </html>

50
 7.3 CSS

Introduction to CSS

Cascading Style Sheets, fondly referred to as CSS, is a simple design language intended to
simplify the process of making web pages presentable.

CSS handles the look and feel part of a web page. Using CSS, you can control the color of the
text, the style of fonts, the spacing between paragraphs, how columns are sized and laid out,
what background images or colors are used, layout designs, variations in display for different
devices and screen sizes as well as a variety of other effects.

CSS is easy to learn and understand but it provides powerful control over the presentation of an
HTML document. Most commonly, CSS is combined with the markup languages HTML or
XHTML.

Advantages of CSS

 CSS saves time − You can write CSS once and then reuse same sheet in multiple HTML
pages. You can define a style for each HTML element and apply it to as many Web
pages as you want.

 Pages load faster − If you are using CSS, you do not need to write HTML tag attributes
every time. Just write one CSS rule of a tag and apply it to all the occurrences of that
tag. So less code means faster download times.

 Easy maintenance − To make a global change, simply change the style, and all elements
in all the web pages will be updated automatically.

 Superior styles to HTML − CSS has a much wider array of attributes than HTML, so
you can give a far better look to your HTML page in comparison to HTML attributes.

 Multiple Device Compatibility − Style sheets allow content to be optimized for more
than one type of device. By using the same HTML document, different versions of a
website can be presented for handheld devices such as PDAs and cell phones or for
printing.

51
  Global web standards − Now HTML attributes are being deprecated and it is being
recommended to use CSS. So its a good idea to start using CSS in all the HTML pages
to make them compatible to future browsers.

Who Creates and Maintains CSS?

CSS is created and maintained through a group of people within the W3C called the CSS
Working Group. The CSS Working Group creates documents called specifications. When a
specification has been discussed and officially ratified by the W3C members, it becomes a
recommendation.

These ratified specifications are called recommendations because the W3C has no control over
the actual implementation of the language. Independent companies and organizations create that
software.

NOTE − The World Wide Web Consortium, or W3C is a group that makes recommendations
about how the Internet works and how it should evolve.

CSS Versions
Cascading Style Sheets level 1 (CSS1) came out of W3C as a recommendation in December
1996. This version describes the CSS language as well as a simple visual formatting model for
all the HTML tags.

CSS2 became a W3C recommendation in May 1998 and builds on CSS1. This version adds
support for media-specific style sheets e.g. printers and aural devices, downloadable fonts,
element positioning and tables.

52
 7.4 JavaScript

Features of JavaScript

JavaScript is a client side technology, it is mainly used for gives client side validation, but it
has lot of features which are given below;

 JavaScript is a object-based scripting language.

 Giving the user more control over the browser.

 It Handling dates and time.

 It Detecting the user's browser and OS,

 It is light weighted.

 JavaScript is a scripting language and it is not java.

53
 JavaScript is interpreter based scripting language.

 JavaScript is case sensitive.

 JavaScript is object based language as it provides predefined objects.

 Every statement in javascript must be terminated with semicolon (;).

 Most of the Javascript control statements syntax is same as syntax of control statements in
C language.
 An important part of JavaScript is the ability to create new functions within scripts.
Declare a function in JavaScript using function keyword.

Limitations of JavaScript

JavaScript have some limitation which is given below;

 Client-side JavaScript does not allow the reading or writing of files.

 It cannot be used for networking applications because there is no such support available.

 It doesn't have any multithreading or multiprocessor capabilities.

7.5 jQuery

Features of JQuery:

jQuery is a JavaScript library designed to simplify HTML DOM tree traversal and manipulation,
as well as event handling, CSS animation, and Ajax.[3] It is free, open-source software using the
permissive MIT License.[2] Web analysis (from 2017) indicates that it is the most widely
deployed JavaScript library by a large margin.[4][5]

54
jQuery's syntax is designed to make it easier to navigate a document, select DOM elements,
create animations, handle events, and develop Ajax applications. jQuery also provides
capabilities for developers to create plug-ins on top of the JavaScript library. This enables
developers to create abstractions for low-level interaction and animation, advanced effects and
high-level, themeable widgets. The modular approach to the jQuery library allows the creation of
powerful dynamic web pages and Web applications.

jQuery includes the following features:

 DOM element selections using the multi-browser open source selector engine Sizzle, a
spin-off of the jQuery project
 DOM manipulation based on CSS selectors that uses elements' names and attributes, such
as id and class, as criteria to select nodes in the DOM
 Events
 Effects and animations
 Ajax
 Deferred and Promise objects to control asynchronous processing
 JSON parsing
 Extensibility through plug-ins
 Utilities, such as feature detection
 Compatibility methods that are natively available in modern browsers, but need fallbacks
for older browsers, such as jQuery.inArray() and jQuery.each().
 Cross-browser support

55
7.6 PHP

56
Features of PHP

It is most popular and frequently used worldwide scripting language, the main reason of
popularity is; It is open source and very simple.

1. Simple
2. Faster
3. Interpreted
4. Open Source
5. Case Sensitive
6. Simplicity
7. Efficiency
8. Platform Independent
9. Security
10.Flexibility
11.Familiarity
12.Error Reporting
13.Loosely Typed Language
14.Real-Time Access Monitoring

Table : Features of PHP

57
Simple

It is very simple and easy to use, compare to other scripting language it is very simple and easy,
this is widely used all over the world.

Interpreted

It is an interpreted language, i.e. there is no need for compilation.

Faster

It is faster than other scripting language e.g. asp and jsp.

Open Source

Open source means you no need to pay for use php, you can free download and use.

Platform Independent

PHP code will be run on every platform, Linux, Unix, Mac OS X, Windows.

Case Sensitive

PHP is case sensitive scripting language at time of variable declaration. In PHP, all keywords
(e.g. if, else, while, echo, etc.), classes, functions, and user-defined functions are NOT case-
sensitive.

58
Error Reporting

PHP have some predefined error reporting constants to generate a warning or error notice.

Real-Time Access Monitoring

PHP provides access logging by creating the summary of recent accesses for the user.

Loosely Typed Language

PHP supports variable usage without declaring its data type. It will be taken at the time of the
execution based on the type of data it has on its value.

59
Testing and Debugging

60
 8. Testing and Debugging

Software testing is a critical element of the ultimate review of specification design and coding.
Testing of software leads to the uncovering of errors in the software functional and performance
requirements are met .Testing also provides a good indication of software reliability and software
quality as a whole. The result of different phases of testing are evaluated and then compared with
the expected results. If the errors are uncovered they are debugged and corrected. A strategy
approach to software testing has the generic characteristics:

 Testing begins at the module level and works “outwards” towards the integration of the
entire computer based system.
 Different testing techniques are appropriate at different points of time.
 Testing and debugging are different activities, but debugging must be accommodated in
the testing strategy

8.1 Goals and Objectives

“Testing is a process of executing a program with the intent of finding an error”. A good test
case is one that has a probability of finding an as yet undiscovered error. A successful test is one
that uncovers an as yet undiscovered error. Our Objective is to design test processes that
systematically uncover different classes of errors and do so with minimum amount of time and
effort.

8.2 Statement of scope

A description of the scope of the software testing is developed. All the features to be tested are
noted as follows. The basic principles that guides software testing are,

 All test cases should be traceable top customer requirements. The most severe defects
from the customer’s point of view are those that cause the program to fail to meet its
requirements.

61
  Test case should be planned long before testing begins. Testing plan can begin as soon as
the requirement model is complete. Detailed definition of the test cases can begin as soon
as the design is solidified. Therefore, the entire test can be planned before any code has
been generated.

 Testing should begin “in the small” and progress towards “in the large”. The first test
planned and executed generally focus on the individual modules. As testing progresses
testing shifts focus in an attempt to find errors in integrating clusters of modules and
ultimately in the entire system

8.3.Test Case

Before the project is released, it has to has pass through a test cases suit, so that the required
functionality is met and previous functionality of the system is also not broken to do this, there is
an existing test cases which checks for the previous functionality. New test cases are prepared
and added to this existing test suit to check for the added functionality.

Test case describes an input description and compare the observed output with expected output
to know the outcome of the test case. If it is different, then, there is a failure and it must be
identified.

A pictorial representation of this can be shown as follows.

62
8.4 Testing Process
The testing process can be shown as:

Following types of testing are done on the System.

a) Unit Testing

The module interface is tested to ensure that information properly flows into and out of the
program unit under test. The unit testing is normally considered as an adjunct step to coding step.
Because modules are not a standalone program, drivers and/or stubs software must be developed
for each unit. A driver is nothing more than a “main program” that accepts test cases data and
passes it to the module. A stub serves to replace the modules that are subordinate to the modules
to be tested. A stub may do minimal data manipulation, prints verification of entry and returns.

Approaches used for Unit Testing were:

63
Functional Test: Each part of the code was tested individually and the panels were tested
individually on all platforms to see if they are working properly.

Performance Test: These determined the amount of execution time spent on various parts of units
and the resulting throughput, response time given by the module.

Stress Test: A lot of test files were made to work at the same time in order to check how much
workloads can the unit bear.

Structure Test: These tests were made to check the internal logic of the program and traversing
particular execution paths.

b) Integration Testing

“If they all work individually, they should work when we put them together.” The problem of
course is “putting them together “. This can be done in two ways:

Top down integration: Modules are integrated by moving downwards through the control
hierarchy, beginning with main control module are incorporated into the structure in either a
depth first or breadth first manner.

Bottom up integration: It begins with construction and testing with atomic modules i.e.
modules at the lowest level of the program structure. Because modules are integrated from the
bottom up, processing required for the modules subordinate to a given level is always available
and the need of stubs is eliminated.

 Testing includes

 Verification and Validation

 Verification:-is a process of confirming that software meets its
specification.

64
  Validation:- is the process of confirming that software meets the
customer’s requirements.

c) Validation Testing

Validation succeeds when software functions in a manner that can be reasonably expected by the
customer. It covers the following :-

Validation test criteria: Performance, functional characteristics and uncovered deviation from
specification

Configuration review: Ensures that all the elements of software configuration have been
properly developed cataloged and have support for the maintenance phase of software life cycle

Alpha Beta testing: Alpha test is conducted by developer’s site by customer. Beta test is
conducted at one or more customer site by software end user

Modular integration testing:

Modular integration testing is done to ensure that the module is working independently. The
inputs as required by the module are given as required and the output is tested as per the
specifications

65
8.5 Debugging
Debugging occurs as a consequence of successful testing i.e. when a test case uncovers an error,
debugging is the process that results in identifying the location of error ad the removal of error. The
poorly understood mental process that connects a symptom to cause is debugging. This process will
always have one of the two outcomes:

 The cause will be found, corrected and then removed or

 The cause will not be found. In the latter case the person performing debugging may suspect a cause,
design a test case to help validate his suspicion, and then work towards the correction of errors in the
interactive fashion.
Following three approaches of debugging were used:

 Debugging by Induction
 Debugging by Deduction
 Backtracking
 In this project we mainly used PRINT STATEMENTS debugging technique.

Enter
Cricket Score App
Deliver
Repots

Team/Player/Match

Score

Score Sheet (Ball by Ball)

Update Score
Generate Report
Score Algorithm Sheet

Cricket Score Database

66
Implementation

67
 9. Implementation
Once the system was tested, the implementation phase started. A crucial phase in the system development
life cycle is successful implementation of new system design. Implementations simply mean converting
new system design into operation. This is the moment of truth the first question that strikes in every one’s
mind that whether the system will be able to give all the desires results as expected from system. The
implementation phase is concerned with user training and file conversion.

The term implementation has different meanings, ranging from the conversion of a basic
application to a complete replacement of computer system Implementation is used here to mean the
process of converting a new or revised system design into an operational one. Conversion is one aspect of
implementation. The other aspects are the post implementation review and software maintenance. There
are three types of implementation:
 Implementation of a computer system to replace a manual system
 Implementation of a new computer system to replace an existing one.
 Implementation of a modified application to replace an existing one.

9.1 Conversion

Conversion means changing from one system to another. The objective is to put the tested system into
operation while holding costs, risks and personnel irritation to a minimum. It involves creating
computer compatible files; training the operational staff; installing terminals and hardware. A critical
aspect of conversion is not disrupting the functioning of organization.

9.2 Direct Implementation

In direct implementation; the previous system is stopped and new system is started up
coincidentally. Here there is a direct change over from manual system to computer-based system. In
direct change over implementation; employees can face the problems. Suppose our software is not
working much efficiently as manual one then we can’t find the defects in our software. It will not be
beneficial in finding errors.

 The proposed system “Cricket Score App” is fully implemented using Direct
Implementation.

68
Scope and Limitation

69
 10. Scope and Limitation

10.1 Scope of the proposed System:

The proposed system provides the automated generation of LPP reference that includes the LPP Rate and
the reference date. LPP is used at the time of Worksheet preparation along with the tender price, which
helps to obtain the overall and annual escalation. Escalation is related to the number of months, calculated
by the LPP reference date and the worksheet preparation date of the particular financial year.

The “Cricket Score App” software is being developed as an accurate and efficient system for the
user. In this system the record of the each request details are preserved along with their transaction related
to them. The system is also made secured as all the updating and transaction can be done by the
authorized person .

10.2 Limitation of the Proposed System:

 Database used is MySQL and it has a stack limit.

 Manual Errors at the time of entering the data can’t be check, only the validation required w.r.t
proposed system is checked.

70
Conclusion

71
 11. Conclusion

The objective of this project was to build a program for maintaining the details of all Supply
Order .The system developed is able to meet all the basic requirements. It will provide the facility to the
user so that they can keep tracks of all the equipments being supplied. The management of the Inventory
will be also benefited by the proposed system, as it will automate the whole supply procedure, which will
reduce the workload. The security of the system is also one of the prime concerns.

There is always a room for improvement in any software, however efficient the system may be. The
important thing is that the system should be flexible enough for future modifications. The system has
been factored into different modules to make system adapt to the further changes. Every effort has been
made to cover all user requirements and make it user friendly.

 Goal achieved: The System is able provide the interface to the user so that he can replicate his
desired data. .

 User friendliness: Though the most part of the system is supposed to act in the background,
efforts have been made to make the foreground interaction with user as smooth as possible. Also
the integration of the system with Cricket Score App project has been kept in mind throughout
the development phase.

72
References

73
 12. References

Books Referred

Books and Sites

I. PHP book by Vasvani (TMH publications).

II. Beginning PHP5 by WROX.
III. www.computoplus.com.
IV. www.wikipedia.com
V. www.w3schools.com
VI. Infomiatics practices by Sumitra Arora.
VII. Head First PHP & MySOL by Lynn Beighley and Michael Morrison(O.Reilly)

74