9. Features
● You can book any kind of tickets such as
sports,cinema,bus,train,air tickets etc.
● You can buy ticket at it’s original price.
● There will be no chance for any ticket blackers.
13. Advantages
● Each person can buy at most three tickets .
● Here you can buy any kind of tickets such as
sports,cinema,bus,train,air tickets etc.
● No ticket blackers can get advantages from this system.
17. Future Scope
● We will be able to book all kinds of tickets in this system .
● We will be able to add a huge amount of data in the system .
● Payment system can be added .
19. SRS Document
Anti-Black Ticket Management System - Software Requirements
Specification (SRS)
1. Preface
This document serves as the SRS for the Anti-Black Ticket Management System. It outlines
the requirements and specifications for developing a web-based ticket booking application
integrated with a QR code system to prevent black market ticket sales.
20. SRS Document
2. Introduction
The Anti-Black Ticket Management System is designed to combat illegal ticket sales and
ensure fair distribution of tickets. It provides users with a secure and efficient ticket booking
process. The system includes a web-based application for ticket booking and a
complementary Android scanner app for validating tickets.
22. SRS Document
4. User Requirements Definition
4.1 User Registration and Login
● Users can register using their NID or Passport as identification.
● Registered users can log in to the system using their credentials.
4.2 Ticket Booking
● Each user can purchase a maximum of three tickets per transaction.
● Users can view available events and select the desired event.
● Users can choose the number of tickets to purchase and provide the required details.
● The system should validate the user's eligibility and available ticket quantity.
23. SRS Document
4.3 User Dashboard
● Users can access their personal dashboard after logging in.
● The dashboard should display the user's purchased tickets.
● The user should have the option to view individual tickets with a QR code generated
based on the current time.
4.4 Android Scanner App
● An Android scanner app will be developed for event staff to validate tickets.
● The scanner app will scan the QR code on the ticket.
● The app should determine whether the ticket is accepted or rejected based on
validation rules.
24. SRS Document
5. System Architecture
The system architecture consists of the following components:
● Web-based application for user registration, ticket booking, and user management.
● Database for storing user information, events, and ticket details.
● QR code generation module for generating unique QR codes for each ticket.
● Android scanner app for ticket validation.
25. SRS Document
6. System Requirements Specification
6.1 Functional Requirements
● User registration and login functionality with NID or Passport verification.
● Ticket booking functionality with validation rules and quantity limits.
● User dashboard to view purchased tickets and generate QR codes.
● Android scanner app to scan and validate tickets.
26. SRS Document
6.2 Non-functional Requirements
● User data and ticket information should be stored securely.
● The system should be scalable to accommodate a large number of users and events.
● The web-based application should be responsive and compatible with various devices
and browsers.
● The Android scanner app should have fast and accurate QR code scanning capabilities
27. SRS Document
7. System Models
● Use case diagrams, sequence diagrams, and activity diagrams can be included here to
illustrate the system's functionality and interactions.
28. SRS Document
8. System Evolution
● Future enhancements and updates can be mentioned here, such as additional features
or integration with third-party ticketing platforms.
29. SRS Document
9. Appendices
● Any additional relevant information, such as technical specifications, can be included in
the appendices.
30. SRS Document
10. Index
● A comprehensive index of terms and topics mentioned throughout the document.
