Professional Documents
Culture Documents
193117137440
CERTIFICATE
HOD
Table of Contents
1 Introduction 1
1.1 Introduction 2
2 System Analysis 3
4 System Design 9
4.1 ER Diagram 10
6 Screens 20-28
7 Testing 29-33
8 Conclusion 34-35
9 Bibliography 36-37
CRICBUZZ
INTRODUCTION
1
1.1Introduction
History of cricket
First Grand Match of Cricket Played by Members of the Royal Amateur Society
on Hampton Court Green
The sport of cricket has a known history beginning in the late 16th century.
Having originated in south-east England, it became the country's national sport in
the 18th century and has developed globally in the 19th and 20th centuries.
International matches have been played since 1844 and Test cricket began,
retrospectively recognized, in 1877. Cricket is the world's second most popular
spectator sport after association football (soccer). Governance is by the
International Cricket Council (ICC) which has over one hundred countries and
territories in membership although only eleven currently play Test cricket.
2
SYSTEM ANALYSIS
3
2. System Analysis
4
2.3 Software Requirement Specification
2.3.1 Functional Requirements
Modules
This system consists of 4 modules namely;
● Ground booking
● Member registration
● Batch registration
● Administrative
Ground booking
The end users may request to book the ground by filling up a form.
Once the admin approves the request, ground gets booked accordingly
Member registration
People may register for club membership. No more lengthy paperwork
required.
Batch registration
People may register for various training batches happening on the ground.
They can do simply by filling up on a contact form.
Administrative
The admin module serves the purpose of admin. User registration
approval, ground booking approval, batch registration approval are a few
features of this module. The admin has access to all the club members profile as
well as the batches registered.
5
2.3.2 Nonfunctional Requirements
Software requirements
Hardware requirements
6
DATABASE DESIGN
7
3. DATABASE DESIGN
TABLES:
Currentmatch table:
Ipl table:
T20 table:
8
SYSTEM DESIGN
9
3. System Design
3.1 ER Diagram
10
3.2 UML Diagram
State Chart Diagram:
State Chart diagram explains the behavior of individual objects in terms of states
and transitions between the states this is also shows the starting and end point of
sequences of state changes. State Chart diagrams helps during the system
design to describe domain objects with intersecting behavior.
11
UML Class Diagrams
The object model-represented in UML with class diagrams, describes the
structure of a system in terms of objects, attributes, associations. The UML
enables us to model the classes in a system and their relationships via class
diagrams.
12
Use Case Diagrams
UML Provides the Use case diagram to facilitate the process of requirements
gathering the Use case diagram models the interactions between the systems
external clients and the Use cases of the system. Each Use case represents a
different capability that the system provides the client. Actors are the external
clients such as, people, robots and the other systems etc., that use the system.
13
Sequence diagrams
Sequence diagrams demonstrate the behaviour of objects in a Use case by
described the objects and the messages they pass. The diagrams are read from
left to right and descending.
Sequence Diagram:
14
Activity Diagram
An activity diagram describes a system in terms of activities are states that
represent the execution of set of operations. This can be used to represent
control flow that is the order in which operations occur and dataflow. This is
useful for showing what happens in business process or an operation.
15
SOFTWARE ENVIRONMENT
16
5. SOFTWARE ENVIRONMENT:
About php:
PHP started out as a small open source project that evolved as more and more
people found out how useful it was. RasmusLerdorf unleashed the first version
of PHP way back in 1994.
● PHP is a recursive acronym for "PHP: Hypertext Pre-processor".
● PHP is a server side scripting language that is embedded in HTML. It is
used to manage dynamic content, databases, session tracking, even build
entire e-commerce sites.
● It is integrated with a number of popular databases, including MySQL,
PostgreSQL, Oracle, Sybase, Informix, and Microsoft SQL Server.
● PHP is pleasingly zippy in its execution, especially when compiled as an
Apache module on the UNIX side. The MySQL server, once started,
executes even very complex queries with huge result sets in record-
setting time.
● PHP supports a large number of major protocols such as POP3, IMAP,
and LDAP. PHP4 added support for Java and distributed object
architectures (COM and CORBA), making n-tier development a possibility
for the first time.
● PHP is forgiving: PHP language tries to be as forgiving as possible.
● PHP Syntax is C-Like.
17
Characteristics of PHP
Five important characteristics make PHP's practical nature possible −
● Simplicity
● Efficiency
● Security
● Flexibility
● Familiarity
About HTML
● Markup is what HTML tags do to the text inside them. They mark it as a
certain type of text (italicised text, for example).
18
How does it work?
HTML consists of a series of short codes typed into a text-file by the site author
— these are the tags. The text is then saved as a html file, and viewed
through a browser, like Internet Explorer or Netscape Navigator. This browser
reads the file and translates the text into a visible form, hopefully rendering the
page as the author had intended. Writing your own HTML entails using tags
correctly to create your vision. You can use anything from a rudimentary text-
editor to a powerful graphical editor to create HTML pages.
The tags are what separate normal text from HTML code. You might know them
as the words between the <angle-brackets>. They allow all the cool stuff like
images and tables and stuff, just by telling your browser what to render on the
page. Different tags will perform different functions. The tags themselves don’t
appear when you view your page through a browser, but their effects do. The
simplest tags do nothing more than apply formatting to some text, like this:
In the example above, the <b> tags were wrapped around some text, and their
effect will be that the contained text will be bolded when viewed through an
ordinary web browser.
19
SCREENS
20
6.SCREENS
LOGIN:
21
T20 Insertion:
22
Current match Schedule
23
Uploading Future Match Schedule:
24
VIEW:
25
IPL Live Score
26
Current Match Score:
27
Cricket Schedule
28
TESTING
29
7. Testing
Testing is a process of executing a program with the intent of finding error.
Software Testing are contains two types:
Manual Testing:
Manual testing is the process of manually testing software for defects. It
requires a tester to play the role of an end user, and use most of all features of
the application to ensure correct behavior.
To ensure completeness of testing, the tester often follows a written test
plan that leads them through a set of important test cases
Automation testing:
Automation testing is an Automatic technique where the tester writes
scripts by own and uses suitable software to test the software.
In other word, Automation testing uses automation tools to write and
execute test cases, no manual involvement is required while executing an
automated test suite.
Basics of software testing
There are two basics of software testing: black box testing and white box
testing.
Black box testing:
Black box testing is the s/w testing method which is used to test the s/w
without knowing the internal structure of code or program.
White box testing:
White box testing is the s/w testing method which is used to test the s/w
with knowing the internal structure of code or program is known to tester.
Generally these types of testing are done by developers.
30
Types of testing
There are many types of testing like
● Unit Testing
● Integration Testing
● Functional Testing
● System Testing
● Stress Testing
● Performance Testing
● Usability Testing
● Acceptance Testing
● Regression Testing
● Beta Testing
Unit Testing
Unit testing is the testing of an individual unit or group of related units. It
falls under the class of white box testing. It is often done by the programmer to
test that the unit he/she has implemented is producing expected output against
given input.
Integration Testing
Integration testing is testing in which a group of components are combined
to produce output. Also, the interaction between software and hardware is tested
in integration testing if software and hardware components have any relation. It
may fall under both white box testing and black box testing.
Functional Testing
31
Functional testing is the testing to ensure that the specified functionality
required in the system requirements works. It falls under the class of black box
testing.
System Testing
System testing is the testing to ensure that by putting the software in
different environments (e.g., Operating Systems) it still works. System testing is
done with full system implementation and environment. It falls under the class of
black box testing.
Stress Testing
Stress testing is the testing to evaluate how system behaves under
unfavourable conditions. Testing is conducted at beyond limits of the
specifications. It falls under the class of black box testing.
Performance Testing
Performance testing is the testing to assess the speed and effectiveness of the
system and to make sure it is generating results within a specified time as in
performance requirements. It falls under the class of black box testing.
Usability Testing
Usability testing is performed to the perspective of the client, to evaluate
how the GUI is user-friendly? How easily can the client learn? After learning how
to use, how proficiently can the client perform? How pleasing is it to use its
design? This falls under the class of black box testing.
Acceptance Testing
Acceptance testing is often done by the customer to ensure that the
delivered product meets the requirements and works as the customer expected.
It falls under the class of black box testing.
Regression Testing
Regression testing is the testing after modification of a system,
component, or a group of related units to ensure that the modification is working
32
correctly and is not damaging or imposing other modules to produce unexpected
results. It falls under the class of black box testing.
Beta Testing
Beta testing is the testing which is done by end users, a team outside
development, or publicly releasing full pre-version of the product which is known
as beta version.
33
CONCLUSION
34
8. Conclusion:
This application has been successfully and was also tested successfully by
taking “test cases”. It is user friendly, and has required options, which can be
utilized by the users to perform the desired operations
The software is developed using java as front end and oracle as back end
in windows environment. The goals that are achieved by the software
❖ Instant access
❖ Improved productivity
❖ Optimum utilization of resources
❖ Simplification of the operation
❖ Efficient management of records
❖ Less processing time and getting required information
❖ User friendly
❖ Portable and Flexible for further enhancement
35
BIBLIOGRAPHY
36
9.BIBLIOGRAPHY
Books:
Objects oriented software engineering practical software development
using uml.W3schools.
Website:
http:\\www.online computersbook.com
http:\\www.w3schools.com
www.oraclecorporation.com
37