Project Overview

 

🧿2. Project Goals

The objective is to provide a robust backend system for suppliers and admins to manage football match tickets, verify details, and deliver unique ticket links to customers. The system scope includes:

• Admin dashboard for match and supplier management.
• Supplier dashboard for ticket information input and point tracking.
• Customer-facing pages to view ticket details and QR codes.

:man-pouting:3. Stakeholders

Admin: Manages matches, suppliers, and ticket generation.
Supplier: Inputs ticket details and requests generation.
Customer: Views match/ticket details just like the Chelsea App ticket preview.
External Server/API/Image: QR codes.

:white_check_mark:Feature (Brief)

4. Functional Requirements

4.1 Admin Mode

• Authentication: Secure login for Admin.
• Add Matches: Admin can add new matches to the system.
• Manage Supplier Information: Admin can view and manage supplier information.
• Ticket Generation Requests: Admin receives requests for ticket generation from suppliers and can send generate requests for each ticket, including bulk requests.
  Ticket Add and Generation Requests: Admins can add and request ticket generation as well, and can send generate requests for each ticket, including bulk requests.
• Ticket Status Updates: Admin validates ticket with external server manually and changes ticket status, updating it to "Matched" or "Unmatched" based on validation from the Google sheet. Matched tickets generate a unique link that appears in both the Admin and Supplier dashboards.
• Ticket Verification: Initially, Admin manually verifies tickets against external data from a Google sheet.
• Points System: Admins can add points to suppliers’ accounts, which are used to generate tickets. Suppliers’ point balances are visible to them. (Debit and credit both)
• Dashboard Management: Admin can track all ticket generation requests and the generated ticket list and adjust statuses.

4.2 Supplier Mode

• Authentication: Secure login for suppliers.
• Add Ticket Information: Suppliers can input ticket details (ID, seat info, etc.) into the system.
• Google sheet integration: Supplier can control their info. by Google spreadsheet
• Track Ticket Status: Suppliers can track the status of their requests (Matched/Unmatched), copy ticket links, or delete tickets from the list.
• Point Management: Suppliers can view their points and transaction history. (Debit and credit both)
• Member Management: Suppliers can add member IDs and passwords.

4.3 Customer Front-End

• Mobile: Match information (mobile-optimised).
• Chelsea-Like QR: The generated QR code will have the same look and feel as the one in the Chelsea ticket app, with a rotating Chelsea lion around the QR code. The QR code will be available on both mobile devices and can be downloaded as an A4 PDF format.

5. Non-Functional Requirements

• Scalability:
• Handle ~100+ tickets per game with a total of 5-10 suppliers actively using the platform at any time.
• The system should be scalable to accommodate an increasing number of suppliers and ticket requests
• Security:
• Authentication for admin & suppliers, secure API data handling.
• Data encryption for ticket information
• Secure management of QR code.
• Performance: Low-latency ticket generation and API response during huge traffic.
• QR-Code: The customer receives a QR code that matches the format in the Chelsea ticket app.
• Usability:
• The user interface should be simple and intuitive for both Admin and Supplier users.
• The customer-facing pages should be mobile-optimized for easy access to tickets, QR, and scanning.
• Reliability
• The system should be highly available and capable of handling simultaneous requests for ticket generation.
• Handle Google Sheet integration accurately.
• Downtime for maintenance should be minimal during matchday week and for 3 days of the match till the match ends; no downtime should be allowed.