A prediction game design project

1. K. Sai Nithin
20671A0516
CSE-A
Fantasy League
Fantasy League
Fantasy League

2. Introduction
The abstract presents a cricket prediction game with a user-friendly graphical interface, intended for
individuals with basic cricket knowledge. Users must register, verify their identities via Gmail, and
receive an initial 500-point allocation.
The game allows users to predict match outcomes, invest points, and potentially double or halve their
points based on prediction accuracy, administered by an admin who sets up matches and provides
answers post-match. Leaderboard positions are displayed, and questions are straightforward, focusing
on identifying top run-scorers or wicket-takers among players. Inspired by the Indian Premier League,
the project utilizes Python's tkinter for GUI development, enabling a risk-free betting experience.

3. ABSTRACT
This is a prediction game with a Graphical User Interface (GUI) designed for cricket enthusiasts. Anyone
with basic cricket knowledge can participate. Users must register and verify themselves using their
Gmail accounts, and they'll receive 500 points upon registration. Users can select from the available
matches and invest their points in various options. They have the flexibility to allocate their points to
both options for a given question. If their choices are correct, their points double; otherwise, the invested
points are halved. An admin login allows the admin to set up matches and provide answers after the
match concludes. Leaderboard positions are displayed for all registered users, regardless of their level of
participation. The questions are straightforward, such as predicting the leading run-scorer or wicket-
taker among the listed players.
The project is designed for entertainment, allowing users to enjoy betting without spending any money.
The idea for this project was inspired by advertisements during the Indian Premier League. To develop
it, the team gained basic knowledge of GUI programming in Python, utilizing the tkinter package for the
required GUI.

4. The existing system is a prediction game for cricket enthusiasts that uses a
Graphical User Interface (GUI).
Users are required to register and verify their identity with a Gmail account.
Upon registration, users are given 500 points.
Users can select available cricket matches and invest their points on various
prediction options.
If their predictions are correct, they double their points; otherwise, the invested
points are halved.
Admins are responsible for setting up matches and providing correct answers after
the match.
The system displays a leaderboard with the positions of all registered users.
EXISTING SYSTEM

5. Dependency on Gmail Account: Requiring users to verify themselves with a Gmail
account can be a limitation, as not all potential users may have Gmail accounts.
Limited Game Variety: The game seems to have limited options, mainly focusing on
simple cricket predictions (e.g., top run-getters, most wickets). This may not cater to a
broad audience.
Risk of Gambling Mentality: While it claims to offer the fun of betting without real
money, the system may inadvertently encourage a gambling mentality among users,
which can be problematic.
Lack of Real-Time Data: The system relies on admin-provided answers after
matches, which means users cannot see real-time results. This might decrease user
engagement.
1.
2.
3.
4.
DISADVANTAGES OF EXISTING SYSTEM

6. User Authentication: Allow users to register using various authentication methods,
not just Gmail accounts, to be more inclusive.
Diverse Game Options: Expand the types of games and predictions offered beyond
basic cricket statistics. This can attract a wider range of users with different interests
in the sport.
Responsible Gaming: Implement features that encourage responsible gaming, such
as daily or weekly point limits to prevent users from investing too many points.
Automation: Reduce the need for manual admin intervention by automating the
process of setting up matches and recording results. Use APIs to fetch real-time
data for match results.
Leaderboards: Enhance the leaderboard functionality to provide more detailed
statistics and trends, making it more engaging for users.
1.
2.
3.
4.
5.
PROPOSED SYSTEM

7. Enhanced User Inclusivity: Allowing multiple authentication methods makes the system
accessible to a broader user base.
Greater Engagement: Diversifying game options and real-time data can increase user
engagement and excitement.
Reduced Admin Workload: Automation reduces the workload on admins, making the
system more efficient and accurate.
Improved Responsible Gaming: Implementing features for responsible gaming can
create a safer and more enjoyable user experience.
Better User Insights: With an enhanced leaderboard, users can gain insights into their
performance, fostering healthy competition and motivation to participate more actively.
1.
2.
3.
4.
5.
ADVANTAGES OF PROPOSED SYSTEM

8. SYSTEM ARCHITECTURE
User Interface
web GUI
SYSTEM CORE
User Management
Match management
Prediction Engine
Data Integration
Scoring & Rewards
Leaderboard
Admin Panel
Database
External Data APIs |
(Real-time Data)

9. HARDWARE REQUIREMENTS
System : Intel Core i5.
Hard Disk : 120 GB.
Monitor : 15’’ LED
Input Devices : Keyboard, Mouse
Ram : 2 GB

10. SOFTWARE REQUIREMENTS
Operating system : Windows 7.
Coding Language : Python
Tool : ·Python Interpreter

11. MODULES
1
2
3
4
User Management :
Match Management :
Prediction Game :
Leaderboard Module :
5 Admin Panel Module :
Manages user registration, authentication, and profiles.
Handles match setup, scheduling, and prediction
question definition.
Manages user predictions and calculates scores based
on match outcomes.
Displays user rankings based on points and performance.
Provides admin functions for match management and
result entry.

12. Use Case ID: UC01
Name: Registering
Actors: Player
Description: Allows the user to register himself.
Pre-conditions: None
Post-conditions: Account will be created for the user.
Main Flow:

13. Use Case ID: UC02
Name: Login
Actors: Player
Description: Allows the user to login into his account.
Pre-conditions: The player must have a registered account.
Post-conditions: The user logs in.
Main Flow:

14. Use Case ID: UC03
Name: Leader Board
Actors: Player and Admin
Description: Allows the actor to view the leaderboard positions
Pre-conditions: The actor player must login
Post-conditions: The leader board is displayed
Main Flow:

15. Use Case ID: UC04
Name: Match Bet
Actors: Player
Description: Checks for match availability and displays the matches
Pre-conditions: The player must login
Post-conditions: The matches will be displayed onto the screen
Main Flow:

16. Use Case ID: UC05
Name: Questions
Actors: Player
Description: Allows the player to invest his coins on the respective options
Pre-conditions: The matches must be available.
Post-conditions: The investment amount will be saved.
Main Flow:

17. Use Case ID: UC06
Name: Match Setup
Actors: Admin
Description: Allows the admin to set the match.
Pre-conditions: None
Post-conditions: The match will be set up by the admin.
Main Flow:

18. Use Case ID: UC07
Name: Results
Actors: Admin
Description: The result of the match will be published by feeding the correct options.
Pre-conditions: There must be a match for which the results are not declared yet.
Post-conditions: The results will be declared and the leaderboard will be updated.
Main Flow:

19. Activity Diagram

20. Use Case
Diagram

21. Output
ScreenShots

22. Future Work & Conclusion
The user can connect through his Facebook account and play
contests with his friends.
To include the data on to a database and make it a kind of a mobile
app.
This app may be extended for football events.
In addition, the user may invest real money into it and get some
coupons in return.

23. THANK YOU
THANK YOU
THANK YOU