SPORTIMO
PLAY FAIR WITH SPORTIMO. How would you create a schedule, manage the cheats and share the results with the participants? SPORTIMO is a very simple tool to do so!
Created on 28th March 2021
•
SPORTIMO
PLAY FAIR WITH SPORTIMO. How would you create a schedule, manage the cheats and share the results with the participants? SPORTIMO is a very simple tool to do so!
The problem SPORTIMO solves
All athletes have a their own identification e.g. Aadhar Card, Birth Certificate etc. The cheats among them conceal the certificates when they come to know that the age entered in their original documents make them ineligible to participate in junior competitions. Instead, with the connivance of unscrupulous touts, they “manufacture“ fake documents which make them eligible to participate in the relevant competition. Age fraud is as serious an offence as doping. In the case of age fraud, it is high time the government enforces a code of conduct to deal with it.
But we have developed a web-based application which authenticates the user’s/athletes information using his Aadhar Card. Once it’s verified, the portal allows the user to apply in various tournaments. We have 2 kinds of users i.e. an Athlete and an Organizer. The organizer can add tournaments and update them. On the other hand, the athlete can apply to these tournaments.
The detailed information about the tournament is displayed to the athlete. The winner wins certain points based on the formula "First Prize/ (team rank*No of teams)" and is given certain perks.
The authentication gap is thus eliminated by using our application.
Challenges we ran into
Challenges Faced:
- Technical issues: Having too many options was a problem for us developers and that lead to application structure incongruency.
- Poor documentation: It likely extended the development time, and made the whole process more difficult. It mainly exposed our application to problems with performance and inhibited the implementation of new features.
- Code quality: Our application worked decently, but the overall code quality seemed to be low or inconsistent.
Other small errors:
a. Forgetting to Test and Inspect the Codes.
b. Presuming Numbers to be Integer Data.
How did we overcome it?
- Focusing on microservices: We realized that the actual problem lies in the monolithic structure of our app, we tried to extract microservices out of the app so that they can work separately. Each mini-application serves its own purpose, for example: API, communicating with the database, fetching data from external services, etc. It significantly streamlined scalability, because we were able to move services around different machines.
- Improved documentation: We focused on working towards our goal on what the main components are, how they relate to each other, and what the main purpose of the application is. It provided us explanations as to why certain solutions, especially the less obvious ones, should be used.
- When fixing the issues with our application, we thought about the expected outcome and our resources: time and money. We had a clear idea of what we wanted to achieve, and how much we can spend on it, it became much easier for our team to choose the optimal solution.