heroic-ticket

byShivakumar Shivakumar

Create a full-stack web application project titled: "E-Ticket Fraud Detection System" The system should detect whether an uploaded or entered ticket is genuine or fraudulent. Project Requirements: 1. Welcome Page (Home Page) - Design an attractive welcome page with animations. - Include interactive UI elements using Bootstrap / CSS animations / JavaScript. - Add a "Get Started" button. - Include navigation buttons: - Register - Login - Add smooth transitions and hover effects. - Make the interface modern and responsive. 2. Authentication System Create two types of login: A. User Login - Users can register with: name email password - Secure login authentication required. B. Admin Login - Only one admin account exists. - Admin login should NOT appear publicly on UI. - Admin login accessible only through a hidden/admin route. Example: /admin-login 3. Transportation Selection Page After user login: Display transportation options: - Bus - Train - Metro - Flight Each option should be clickable cards with icons and animations. After selecting one option → redirect to Dashboard. 4. User Dashboard Dashboard should contain THREE fraud detection modules: Module 1: URL-Based Detection - User pastes ticket verification URL - System checks whether URL is genuine or suspicious - Display result: Genuine Ticket or Fraud Ticket Module 2: QR Code Detection - User uploads ticket QR code image - Extract QR data - Compare with stored dataset - Display result: Genuine Fraud Already Used Ticket Module 3: Ticket Details Entry + QR Generator - User enters ticket details: ticket ID passenger name source destination date transport type - System generates QR code from these details - Store QR data in database Then: If user uploads the SAME ticket again System should detect duplicate usage and display: "Fraud Detected – Ticket Already Used" 5. Fraud Detection Logic System should detect fraud using: - duplicate ticket ID detection - duplicate QR detection - suspicious URL pattern detection - dataset comparison validation 6. Admin Panel Admin can: - view all registered users - view uploaded tickets - view fraud detection logs - view duplicate ticket alerts - manage dataset (add genuine ticket samples) 7. Dataset Storage Store: ticket_id transport_type QR_data URL_data status: genuine used fraud Use database: SQLite or MySQL 8. Tech Stack Frontend: HTML CSS Bootstrap JavaScript animations Backend: Python Flask (preferred) Database: SQLite Libraries: qrcode opencv pyzbar pandas 9. UI Requirements Make UI: interactive animated responsive card-based layout dashboard styled sidebar navigation Add: hover effects icons smooth transitions 10. Output Generate complete working project with: folder structure backend code frontend templates database setup QR detection module URL detection module admin panel fraud detection logic

LandingLoginTicketsAdminLogin
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirement Document
Page 1 of 7

System Requirements Document (SRD)

Project Name: heroic-ticket

1. Introduction

The heroic-ticket project is a full-stack web application designed to detect fraudulent tickets in various transportation systems. The system enables users to verify the authenticity of tickets through multiple detection modules, including URL-based detection, QR code analysis, and manual ticket entry with QR code generation. It also provides an admin panel for managing users, tickets, and fraud detection logs.

This document outlines the functional and non-functional requirements, user personas, design concepts, and technical specifications for the project. The system is tailored for Shivakumar's needs, with scalability and extensibility in mind, including future API integration for automated dataset updates.

Page 2 of 7

2. System Overview

The heroic-ticket system aims to provide a secure and user-friendly platform for detecting fraudulent tickets across multiple transportation modes, including buses, trains, metros, and flights. The system will feature:

  • A modern, animated, and responsive user interface.
  • Fraud detection modules leveraging URL analysis, QR code scanning, and manual ticket entry.
  • An admin panel for managing users, tickets, and fraud detection datasets.
  • Initial support for manual dataset uploads, with future extensibility for API integration.

The system will be developed using Python Flask for the backend and a combination of HTML, CSS, Bootstrap, and JavaScript for the frontend. The database will use MySQL for scalability and reliability.

3. Functional Requirements

As User:

  • I should be able to register with my name, email, and password.
  • I should be able to log in securely.
  • I should be able to select a transportation mode (Bus, Train, Metro, Flight) after logging in.
  • I should be able to verify tickets using:
    • URL-based detection.
    • QR code scanning.
    • Manual ticket details entry with QR code generation.
  • I should be notified if a ticket is fraudulent, genuine, or already used.
Page 3 of 7

As Admin:

  • I should be able to log in through a hidden route (/admin-login).
  • I should be able to view all registered users.
  • I should be able to view uploaded tickets and fraud detection logs.
  • I should be able to view duplicate ticket alerts.
  • I should be able to manage the fraud detection dataset by adding genuine ticket samples manually.

4. User Personas

1. Regular User

  • Description: A passenger who wants to verify the authenticity of their transportation tickets.
  • Goals: Ensure their ticket is genuine and avoid fraud.
  • Actions: Register, log in, select transportation mode, and use fraud detection modules.

2. Admin

  • Description: A system administrator responsible for managing users, tickets, and fraud detection datasets.
  • Goals: Maintain the integrity of the system and ensure accurate fraud detection.
  • Actions: Log in through a hidden route, view logs, manage datasets, and monitor system activity.

5. Visuals Colors and Theme

The heroic-ticket project will feature a unique and modern color palette to create a professional and engaging user experience.

Page 4 of 7

Color Palette:

  • Background: #F4F9FF (Soft Sky Blue)
  • Surface: #FFFFFF (Pure White)
  • Text: #2C3E50 (Dark Slate)
  • Accent: #3498DB (Vivid Blue)
  • Muted Tones: #BDC3C7 (Light Gray)

This palette ensures readability, visual appeal, and a clean, professional look.

6. Signature Design Concept

The heroic-ticket homepage will feature an interactive 3D transportation hub.

Key Features:

  • 3D Animation: The homepage will display a rotating globe with animated transportation icons (bus, train, metro, flight) orbiting around it.
  • Interactive Elements: Users can click on the icons to select their transportation mode, triggering smooth transitions to the dashboard.
  • Dynamic Background: The background will feature a gradient animation that shifts between shades of blue and white, evoking a sense of motion and travel.
  • Micro-Interactions: Hovering over icons will trigger subtle animations, such as enlarging the icon or displaying a tooltip.
  • Get Started Button: A prominent, animated "Get Started" button will pulse gently to draw user attention.

This design will create a memorable first impression and set the tone for the rest of the application.

Page 5 of 7

7. Non-Functional Requirements

  • Performance: The system should handle up to 1,000 concurrent users without performance degradation.
  • Scalability: The architecture should support future API integrations for automated dataset updates.
  • Security: Implement secure authentication and data encryption to protect user information.
  • Responsiveness: The UI should be fully responsive across devices, including desktops, tablets, and smartphones.
  • Maintainability: The codebase should follow best practices for readability and modularity.

8. Tech Stack

Frontend:

  • React for Web

Backend:

  • Python
  • FastAPI

Database:

  • MySQL (with Alembic for migrations)

AI Models:

  • GPT 5.4 for user-friendly responses
Page 6 of 7

AI Tools:

  • Langchain
  • Litellm for LLM Routing

Orchestration:

  • Docker
  • Kubernetes

9. Assumptions and Constraints

Assumptions:

  • Users will have access to a stable internet connection.
  • Admins will manually upload genuine ticket datasets initially.
  • The system will primarily serve users in India (IN), with locale-specific defaults such as IST timezone and INR currency.

Constraints:

  • API integration for ticket datasets is not available at launch and will be added in future updates.
  • The admin panel will be accessible only through a hidden route for security purposes.
Page 7 of 7

10. Glossary

  • Fraudulent Ticket: A ticket that is either fake, duplicated, or already used.
  • QR Code: A machine-readable code containing ticket details.
  • Dataset: A collection of genuine ticket samples used for fraud detection.
  • Admin Panel: A secure interface for managing users, tickets, and fraud detection logs.
  • API Integration: Connecting to external services to fetch genuine ticket datasets automatically.
Landing design preview
AdminLogin: Sign In
AdminPanel: View Dashboard
AdminPanel: View Users
AdminPanel: View Tickets
AdminPanel: View Fraud Logs
AdminPanel: View Duplicates
AdminPanel: Manage Dataset
Dataset: Add Samples
Tickets: Review Details
Users: View Profile