In that project, I would like to take this opportunity to express my sincere gratitude to my project supervisor, Iftekharul Alam Efat, who has guided me a lot during the development of the project. I would like to thank him once again because he shared his experience with us so that we can understand more logically how to develop a software suitable for current needs. Last but not least I would like to thank my coursemate Bishawjet Banik &.
Introduction
- Overview
- Purpose
- Background
- Benefits
- Goals
- Stakeholders
- Propose System Model
- Project Schedule
- Gantt Chart
- Milestones
In this system the participants can bet on two types of games like cricket and football. This system provides three types of application methods for different user roles such as system administrator, bet creator and participants. Only bet creator and system administrator are allowed to access the restricted functions like create game, results publication etc.
Participants can bet on a game in three ways, such as match betting, toss/withdrawal betting and man of the match betting. Generally we can see that when someone wants to bet on a game, he has to find another person who is willing to bet on that game. When participants place a bet on the game, the bet amount is deducted from the participant's account and the winning ratio is deducted.
When participants place a bet on the game, the amount of the bet will be deducted from the account of the participants and the winning ratio will be deducted from the account of the bet maker.
Requirement Specification
- Functional Requirements
- Bet creator can post game
- Participants view game list
- Participants place a bet on game REQS-03 Participants can place on bet
- Bet creator show betting history
- System administrator maintain transaction process REQS-05 System administrator maintain transaction Process
- Result publish at the end of the game
- System will calculate profit & lose
- Data scrapping from third party website
- Performance Requirements
- Speed and Latency Requirements
- Precision and Accuracy Requirements
- Capacity requirements
- Dependability Requirements
- Reliability and Availability Requirements
- Robustness and Fault Tolerance Requirements
- Safety Critical Requirements
- Maintainability and Supportability
- Maintenance Requirements
- Supportability Requirements
- Adaptability Requirements
- Security Requirements
- Access Requirements
- Integrity Requirements
- Privacy Requirements
- Usability and Human Integrity Requirements
- Ease of Use Requirements
- Understandability and Politeness Requirements
- Accessibility Requirements
- User Documentation
- Look and Feel Requirements
- Appearance Requirements
- Style Requirements
- Operational and Environmental Requirements
- Expected Physical Requirements
- Requirement for Interfacing with Adjacent System
- Release Requirements
- Legal Requirements
- Compliance Requirements
- Standard Requirements
Description To create or post a game bet, creators must be registered in the system. This requirement specifies the system speed, accuracy and precision requirements of the system. The system is able to manage all the requests, input information from the participants and the bet maker.
These requirements specify the general requirements for maintaining the system and how long the system will be available, how much the participants rely on the system, etc. To provide unavoidable support, the system must be available 24 hours a day and participants can trust this system. The system will never crash due to a single minor error and the server will never go down.
Description When the system is full of participants during this time, the system will not crash and the server will not go down. The system will provide support in any situation if any of the following causes occur. To access this system or a specific module, the system must provide a central authentication mechanism.
These requirements define how the system will interact with the participants and bettors and how easily they can use the system. Description The system is more efficient, easy to use, more functions added. The system is understandable both for the bet maker and for the participants. Look and feel requirements describe how the system will look and how the user interface of that system will appear.
These requirements provide what color will be used for the system design and how the system will respond to mobile view etc. These requirements focus on how the system administrator and bettors will work with this system and what environment the system will provide to the system. bet participants.
Requirement Analysis
Use Case Diagram
- Post Game Use Case Use case name Post game
The use case diagram represents the interactions of the system administrator, bet maker, and participants in this system. This diagram describes all the interactions of the stakeholders of this system and shows how the system works. Condition The bet maker who placed the bet must be registered in the system.
Alternative flows
- View Game Use Case Use case name View game
- Place Bet Use Case Use case name Place bet
- Betting history
- Request Coin
Condition The bet creator places the bet and participants will place bet on the game.
Use case name Request coin
- Withdraw Coin
- Result Publication
- Data Scrapping
- Activity Diagram
- Post Game Activities
- Place Bet Activities
- Transaction Process Activities
- Sequence Diagram
- Create Game
- Placed a Bet
- Result Announcement of a Game
Prerequisite The bet creator will post the game and participants will place bets on the bet. The system checks the participants who have placed bets on the game and selects the winner. Deposit condition After publication of the result system, you must check the participants and their bet amount on this game and refund the winning amount to the participant account as well as the bet maker account.
I am using some activity diagram against use case diagram so that the user of this system can easily understand what he has to do in this system. The bet maker first visits the registration page, if he has already registered in this system, then goes to the login page. If he successfully logs into this system, he can add a game to participate in betting.
When participants enter the system, he can see the posted game list and can choose anyone. The sequence diagram shows the interaction between the class and the object and the behavior of the system stakeholders with these classes and objects. Add form game page bet maker enter all the necessary information required for a game and set the winning ratio on a bet, enter the match and submit the form.
If the form is submitted successfully, the posted game will be displayed on the system index page. If the participant account has sufficient balance, the system will show him a success message, otherwise the system will show an error message. If the bet is successfully placed, the stake amount will be deducted from the participant's account.
First he selects the entire winning team of the match, then throws the winner and the player of the winning match and clicks the publish button. Meanwhile the system will count all the users who have bet on this game and check their betting status and calculate their winning amount and return them to their account who are the winners of this game.
Design and Development
- Development Tools and Technology
- User Interface Technology
- Implemented Tools and Platform
- Class Diagram
- Database Diagram
- Test Plan
- Testing Features
- Testing Strategy
It also describes a tool that allows developers and testers to view and interact with the user interface of this system. The user interface is related to the design of that system and the interactions of that system's stakeholders with that system. This language is used to format the content of the HTML element of this system.
I can easily use this to design the interface of my project based on the color and position of the content, element. Also, the main purpose of using a bootable system is how the system will look when the system changes from device to device. After adding some classes to the existing elements in the HTML code and changing some CSS code, such as removing some values for the width specified in pixels, the site was resizing based on the width of the window.
The tools and platforms implemented are the ones I used to successfully complete my project on time. We can use this platform not only for PHP code but also for HTML, CSS JavaScript. For entry-level developers, this IDE is very useful because this IDE suggests the code or code element that I need to use.
A class diagram is a diagram that shows the relationship between system code dependencies and classes. From this diagram we can know all the information of the interested parties as well as the general information of the system. The testing feature is the process of which functionality I needed to test and which functionality I didn't need to test.
This also indicates what methods, approach I used to test the functionality of this system. A test approach is the implementation of a project's test strategy, which defines how testing would be performed.
5.2.1.1.1 Equivalence Class Partitioning
5.2.1.1.2 Boundary Value Analysis
White Box Testing
5.2.1.2.1 Unit Testing
5.2.1.2.1.1 Login
5.2.1.2.1.2 Login and placed a bet
5.2.1.2.1.3 Logout
5.2.1.2.2 Integration Testing
- Pass/Fail Criteria
- Testing Schedule
- Trace Ability Matrix
- Testing Environment
- Test Cases
- Login
- Bet Post
- Place a Bet
- Request for Coin
- Request for Withdraw
- Result Publish
- Bet Amount Calculation
- Testing Deliverables
- User Acceptance Test
- User Manual
- Landing Page
- Bet Creator Account
- Participants Account
- Conclusion
- Project Summary
- Limitations
- Obstacles and Achievements
- Future Scope
The tester set the pass-fail criteria that indicate what inputs will be processed on this system and what will not be processed. Entry condition: participants and bet maker are both logged into this system and can access the system. Posting Condition: The posted game will be displayed on the system index page and participants can bet on this posted game.
Prerequisite: Participants must be registered in the system and have sufficient funds in their account. 2 Click Team/Player The name of the selected team or player will appear on the submission form. Post condition: participants place bets stored in the system for a specific game until the result is published.
Posting condition: If the system administrator accepts the request, the requested amount will be added to the account of the participant or bet maker. Posting Condition: If the system administrator accepts the request, the requested amount will be deducted from their account and the balance will be sent to the requesting person's account. When a participant, bettor or system administrator first browses this system, they will display this page.
This is the bet maker module in which all bet maker activities are displayed graphically. After entering the system, he can see his profile betting history, how many bets he has placed and his total earnings from this system. This is the page for adding a game form. Here the bet maker enters all the necessary information required for a game, sets the winning ratio on a bet, enters the match and submits the form.
On this page the bettor can see all his published games and on this page he can edit the game, delete the game and publish the result of this game. If the system administrator accepts his request, the amount will be deducted from his account. But before submitting the request successfully, the system first checks his account whether the requested amount is available or not.
Since starting the system I have learned so many things that are necessary for the developer.
