Introduction of Bidding Management System:
Are you looking for a Bidding management system project? We are here to help you. You can contact us. The Indian Premier League (IPL, officially Vivo Indian Premier League for sponsorship reasons) is a professional Twenty20 cricket league in India contested during April and May of every year by teams representing Indian cities.
The league was founded by the Board of Control for Cricket in India (BCCI). The IPL is the most attended cricket league in the world and ranks sixth among all sports leagues. Before the start of every season, players are auctioned for teams. Currently, this system is not fully computerized. So, we are trying to develop a fully computerized Bidding system for the next IPL season.
This system would be a fully cloud-based system. Bidders can bid on players from their offices, homes, or place where they want to be. This system would be more transparent anyone can view the IPL auction. But only registered team owners can bid on registered players. The system would be more available for bid 24X7 when online bidding of IPL going on.
You can also check these posts:
- House Bidding Management System
- Hotel Management System
- 2048 Android Game Project
- Cinema Hall Booking System
- Case Management System
Modules of Bidding Management System:
There are several modules required to complete this system. Here we are discussing the main modules or core modules of the system.
Admin Profile:
Admin profile is profiled which is assigned to a superuser having full access to the system. Admin module contains Admin Id, name, address, contact no. Admin can view player details, team owner details, bidding process, etc.
Player Profile:
Registered player details would be available for view. Player details would include player name, age, record, base price, etc. Once any player goes in the auction. A team owner can bid on him. The player would ably see the details of the owner who has won the bid. The player would also receive payment and bond to signed.
Team Owner:
The team owner is someone who holds the maximum share of the team. A team owner can manage his/her team. Bid on a new player to join the team squad.
Search Player Details:
A team owner can search the details of each player. Sort them, add them to the cart, bid on them. Once they won the bid, they need to make payment to the player.
Availability:
A team owner can check whether a player is available for bid or not. If a player is available for bid and the player has not been sold. They wish to bid on a player they can.
Bidding:
The bidding process is a real-time process. Data in the database would be updated in real-time and visible to users in real-time.
Payment Details:
After successful winning of bid Team owners needs to pay the money using cash/net banking/ATM card. The payment portal would use a payment gateway to clear payment. Once payment will clear receipt of payment will be generated automatically. Add/update/delete Player’s Details. Only the admin can add, update, and delete the player’s details and others user details. Admin has special permission to do so.
User authentication according to his/her role:
The system is strong enough to make authentication as per logged in user.
Add Team Owners:
Admin can add team owner details, update owner’s budget. Team owner needs validate their profile before going in the bidding process.
System Design of Bidding Management System:
The system basically needs very simple architecture. This is system is there main three users i.e. Admin, Player, And owners.
Use Cases for Admin of Bidding Management System:
Bidding Management System has an actor user (Admin). These actors would manage the Bidding management system and help the IPL committee to do the auction process easier and faster than previous. These users can log in to the system using a user id and password. When security is verified, these users can make the change that needs to be done in the system.
Users can manage player’s details. Admin can change the details of the owner if needed or if there are any changes. Admin can verify the bid, player details, Owner details. Admin would manage the bidding process in real-time using this system. Admin needs to log out of the system before leaving it for security purposes.
The Use Case for Players of Bidding Management System:
Our second end-user is a player. The player can log in to the system and verify their identity. The player can view the listed team owner. The player can edit, update his information in the system. The player can view the bid. The player can find the owner’s details. The player would able to accept the contract. Once they accept the contract, they would receive money.
The player needs to log out of the system before leaving it for security purposes.
Use Case for Team Owner of Bidding Management System:
A team owner is someone who bids on players. Owners need to log in to the system before they go into the bid process. They can view players’ details, sort them. They can bid on players, increase bids. Once they won the bid successful. They need to pay the price of the player to the player’s manager.
The team Owner needs to log out of the system before leaving it for security purposes. The team owner is someone who bids on players. Owners need to log in to the system before they go into the bid process. They can view players’ details, sort them. They can bid on a player, increase the bid. Once they won the bid successful.
They need to pay the price of the player to the player’s manager. The team Owner needs to log out of the system before leaving it for security purposes.
User Interface of Bidding Management System (UI):
The user interface is a very important part of the system. A good and user-friendly interface attracts the user toward it. Whereas a bad one makes the user experience bad and they never return to the system. As we have shown several use cases in this system. We have developed these interfaces to interact with the system.
Login Page:
Admin or client need to log in using login id and password.
Owner Page:
The owner can view their details as well as the player’s details. A team owner can participate in the bidding process, buy a player, pay the bidding amount to the player’s manager.
Player Page:
The player page includes player details, player records. The player can see the owner details who is paying him. The team’s name of the player would be updated as soon as they accept the contract.
Search Page:
The search page allows the team owner to search for the player profile. Player records, name, type of player, base price, previous team everything would be visible to the Owner.
Bidding Page:
The bidding page allows the Team owner to bid on the player. If someone raises the bid. Another user can also rise the bidding prices.
Payment Page:
This interface helps in paying the money via several modes.
Er-Diagram of Bidding Management System
There are mainly five entities Admin, Player, Team Owner, Bid, Payment. These five entities would manage the whole system. There are mainly five entities Admin, Player, Team Owner, Bid, Payment. These five entities would manage the whole system.
Admin:
Admin is a superuser of the system. Admin has all right to view and modify the data in the system.
Admin has the following attributes:
Admin ID:
This is a numeric 14 digits number that is unique to every admin. Admin ID is the primary key to the admin table in the database.
Name:
This attribute would hold the name of admin. The name is a varchar type variable that holds the data length up to 250 characters.
Email ID:
This is an essential attribute of the table. Every admin must have a working email id to keep in contact with employees. This field has validation only email formatted values will be stored.
Contact No.:
This is multi valued attributes which mean every admin can have more the one mobile number in database.
Address:
This attribute would hold the address of the admin. Each employee must provide the address. Admin address is verified via the Human resource team.
Player:
The player is the basic end-user of our system most of the business is done through them. The player can add details about himself.
The Player has the following attributes:
Player ID:
This is a numeric 14 digits number that is unique to every Client. Player ID is the primary key to the client table in the database.
Name:
This attribute would hold the name of clients. The name is a varchar type variable that holds the data length up to 250 characters.
Base Price:
This is the price of a player decided by the player. Minimum this much amount is needed to buy a player.
Player type:
Player type is a player is batsman, bowler, all-rounder.
Player record:
Player record helps the owner to decide that whether they go for player or not.
Contact No.:
This is multi valued attributes which mean every client can have more the one mobile number in database.
Address:
This attribute would hold the address of clients. The address of clients would help us to connect with them and visit the location. This would provide better services.
Team owner:
The team owner is the end-user of our system most of the business is done through them. A team owner can add details about himself.
The team owner has the following attributes:
Owner ID:
This is a numeric 14 digits number that is unique to every Client. The owner ID is the primary key to the client table in the database.
Name:
This attribute would hold the name of team owners. The name is a varchar type variable that holds a data length of up to 250 characters.
Team name:
This attribute would hold the name of teams. Team Name is a varchar type variable that holds the data length of up to 50 characters.
Contact No.:
This is multi valued attributes which mean every client can have more the one mobile number in database.
Address:
This attribute would hold the address of clients. The address of clients would help us to connect with them and visit the location. This would provide better services.
BID:
The bidding table holds the complete information of bidding. The system is basically designed for the bidding process. Therefore, this table needs to be secure.
The bid entity would have the following attributes:
Bid ID:
This is a numeric 14 digits number that is unique to every property. Bid ID is the primary key to the property table in the database. Each property is uniquely identified using this id.
Owner ID:
This is a foreign key to the Team owner table. The owner is also a user of the system. The owner field just holds the id of the owner and the rest information is mapped with the owner table.
Player ID:
This is a foreign key to the player table. the player is also a user of the system. The player ID field just holds the id of the player and the rest information is mapped with the owner table.
Status.:
This attribute would able to hold the data about the current status of bid such as not started, over, or live.
Final bid:
This attribute would help to get the information of the final amount of bid.
Payment:
Everyone is doing the job for money-making. Whenever it comes to money, we should make that our client’s money would be safe. In this, Entity every single transaction is recorded in the database. Our company would use a safe and secure payment gateway to clear the payment.
Followings are the attributes:
Payment ID:
Payment ID is the primary key to the payment Entity. Every payment is uniquely identified using this ID or attribute. This is also a 14-digit natural number.
Bid ID:
This is a foreign key to book entity. Every booking is redirected to the payment page. It carries a bidding ID that would update the payment status in the book table.
Transaction Reference No.:
This is an attribute used to hold the transaction reference number provided by Payment Gateway Bank. Any issue with payment would be resolved using this number.
Functional and Non-Functional Requirements of Bidding Management System:
There are two types of requirements of system in any system, these are:
Functional Requirement of Bidding Management System:
Registration:
Users can register themself in the system. Admin will verify their profile to work properly. Once a user is registered with the system. He/she can register his/her team to Bidding Management System. Admin will view the bids and verify that bid only if that would be above than base price.
Validation:
Validation is very important in the system. Invalid data can corrupt the valid data. So, we need to apply validation in each module. Validation would ensure the safety and security of data.
Player Record:
Player, Owner data should be secure. We should take care of clients’ data privacy in our minds. The client is the basic unit of our business. Client data and records would help us to provide them better information.
Add Player, a team owner:
This function allows the admin to add the player details. But only the admin can verify the player’s details. Without verification, player details would not reflect in the system.
List of players with details:
All players should be listed and reflected team owner. A team owner can view these listed properties and book the desired property.
Payment options:
Clients can pay the money for property via any mode they wish to do. They can pay via cash, credit cards, debit cards, online net banking, online wallets, etc. The system should not restrict them to some payment option.
Feedback and Suggestion:
Feedback and suggestions are key to improve in business. Therefore, we need to take the feedback from our customers to improve our services.
Non-Functional Requirement of Bidding Management System:
Improve Search option:
The search option should be rich enough to provide the property details to clients as per their requirements and wish. The search option should search in the whole database. An efficient search option attracts the client to buy and rent the property.
Support Multi User:
Nowadays, every system work in an environment of multi-users. As per the requirement of the system, our system is developed in a multi-user environment.
Fast:
The search option should be fast enough to produce a result of the search in seconds. Every module should to compatible with other modules. There should not be any lag or delay in processing the data.
Available(24X7):
Property Management System should be available to clients 24X7. The user can access the system whenever they need to access it, wherever they want to access provided having an internet connection and device to access it.
Design Data Dictionary for Er-Diagram of Bidding Management System:
The data dictionary is useful in case of development.
Table Name: Admin Master
Primary Key: Admin ID
Description: To store the details of admin
| Serial No. | Fields | Datatype | Description |
| 1. | Admin ID | Integer | Primary key |
| 2. | Name | varchar | |
| 3. | Email ID | varchar | |
| 4. | Contact No. | Integer | Multiple contacts can exist for a single admin |
| 5. | Address | varchar |
Table Name: Player Master
Primary Key: Player ID
Description: To store the details of players
| Serial No. | Fields | Datatype | Description |
| 1. | Player ID | Integer | Primary key |
| 2. | Name | varchar | |
| 3. | Contact No. | Integer | Multiple contacts can exist for a single client |
| 4. | Address | varchar | |
| 5. | Base price | Float | |
| 6. | Player Type | Varchar | |
| 7. | Player record | Varchar |
Table Name: Team Owner Master
Primary Key: Owner ID
Description: To store the details of Team owners
| Serial No. | Fields | Datatype | Description |
| 1. | Owner ID | Integer | Primary key |
| 2. | Name | varchar | |
| 3. | Contact No. | Integer | Multiple contacts can exist for a single client |
| 4. | Address | varchar | |
| 5. | Team Name | varchar |
Table Name: Bid Master
Primary Key: Bid ID
Description: To store the details of Property
| Serial No. | Fields | Datatype | Description |
| 1. | Bid ID | Integer | Primary key |
| 2. | Owner ID | Integer | Foreign key to Team Owner Master |
| 3. | Player ID | Integer | Foreign key to Player Master |
| 4. | Status | varchar | Available, sold, rented, etc. |
| 5. | Final | Float |
Table Name: Payment Master
Primary Key: Payment ID
Description: To store the details of Payment details
| Serial No. | Fields | Datatype | Description |
| 1. | Payment ID | Integer | Primary key |
| 2. | Bid ID | Integer | Foreign key to Bid Master |
| 3. | Transaction Reference No. | varchar | Bank Transaction number |
Conclusion of Bidding Management System:
We have developed a secure, user-friendly Bidding Management System. This system is capable of taking care of each work that needs to be done in IPL Auction. The client can log in using a user id and password. This means the unauthorized users cannot enter the system making it secure. Searching player help to find their desire player fast.
Online payment and verification make it more client friend. This system would definitely be going to reduce labor and make bidding easier and promising to team owners. IPL Bidding management system takes care of each process required in bidding. This system is a next-generation bidding solution.