REQUIRMENT SPECIFICATION DOCUMENT

bus ticketing system specification

Requirement specification
Requirement Specification a complete description of the behavior of a system to be
developed and may include a set of use cases that describe interactions the users will have
with the software. In addition, it also contains non-functional requirements. Non-
functional requirements impose constraints on the design or implementation (such as
performance engineering requirements, quality standards, or design constraints)

Functional Requirements
Functional requirements define the specific functions that the system performs, along with
the data operated on by the functions. The functional requirements are presented in
scenarios that depict an operational system from the perspective of its end users. Included
are one or more examples of all system features and an enumeration of all the specific
requirements associated with these features.

 The system shall incorporate mechanism to authenticate its users

 The system shall verify and validate all user input and should notify in case of

error detection and should help the user in error correction

 The system shall allow sharing of files in the system

 The system shall allow quick messages to be exchanged without face to face
interaction .

Non-Functional Requirement
Non-functional requirements address aspects of the system other than the specific
functions it performs. These aspects include system performance, costs, and such general
system characteristics as reliability, security, and portability. The non-functional
requirements also address aspects of the system development process and operational
personnel. It includes the following:

 The system shall be user friendly and consistent

 The system shall provide attractive graphical interface for the user

 The system shall allow developer access to installed environment

2
 REQUIRMENT SPECIFICATION DOCUMENT

 The system shall target customer base

Architecture of The Proposed System

User Activities
The most common activities carried out by user are illustrated bellow

 The user can search for the seat

 The user can sign up/do registration with the system

 The registered user can login to the proposed system

 The user can check for the available seat

 The user can also do payment for the seat on the proposed system

 The user can print receipt on the system as evidence of payment

Administrator Activities
 The administrator will verify all the registered user, and allow them to login to the
system

 The administrator give acknowledge to any payment user made on the system

 The administrator can add vehicle, driver and generate report as well

User app
 Forgot password
the user can change his password for security reasons or reset it if the user forget
it

 Registration

Users who are got privilege to access this system they might be registered of the
system.

2
 REQUIRMENT SPECIFICATION DOCUMENT

admin and operator used their user name and password to login this system. It is
the login user interface who is star user of the system and using the Admin
Dashboard fill the email and password field
 Search

User of the system (visitors)search ticket to fulfill station from and station to and
specific date for Searching bus
 Seat selection

ONLINE BUS TICKET RESERVATION SYSTEM Able to choose the seats which can
are available for a certain class.
 Choose seat from the map

User or visitors of the system book ticket and saw ticket details which is booked and
which is non-booked, and user can book ticket to fill up the passenger info after
selecting the seats

 Ticket types (e-ticket. M-ticket, counter ticket)

 nearest by collection center, we will let the client to choose the nearest collection
place

 View & write reviews

 Online payment
users can book their seat by paying online using online payment systems

 Payment integration
 Bus ticket booking confirmation through SMS & email
Confirmation message sending the system to the user via SMS and email to generate
a pin code to identify the owner of ticket
 for foreign users we will activate by email or google authentication or by
phone number

2
 REQUIRMENT SPECIFICATION DOCUMENT

 Buy vouchers and use/send to friends & relatives

user can buy, send or transfer bus ticket for other persons.

 Automated reminder for ticket/bus booking

the system reminds the user his trip and the day and time of the trip.

 Print & download Ticket

the user can print and download his ticket.

 Send ticket via Email

A mail should be send to the concerned person about the confirmation of the ticket
to the specified email address.

 Manage wallet
Wallet helps the user flexibly plan his budget and track spending, so the user stay in
control and achieve his future goals.

 Manage Trips

 Ticket verification through QR code

Qryptal's solution plugs into existing document production systems and generates a
highly secure digital signature with embedded data to be placed on the document as
a barcode. After that, anyone can instantly verify the credibility of the information,
through an App on their smart phone.

 Cancel tickets by ticket number as per the T&C

E-ticket cancellation is hassle-free and smooth. the user don’t have to wait in long
queues at the bus station or pay exorbitant fees to travel agents to cancel the user
ticket. cancellation can be done on the internet, from the comfort of the user home.

 Request refund & track them

the company has to pay the full cost of the user ticket in cases of travel delays,
travel cancellations and denied boarding.

 Reschedule booking/ticket

2
 REQUIRMENT SPECIFICATION DOCUMENT

user can reschedule his Trip whenever he is ready to travel again.

 Manage profile
 Security Assured
 Newsletter subscription
 Notification & updates
there will be announcement for new notification and updates.

AGENT PANEL
 Login
Login to the system through the first page of the application, admin and operator
used their user name and password to login this system
 Control panel
Ticket Administration in allows to have full control:-
-Booking report
-Report
-Wallet deposit
-Print ticket
-Cancellation
SUPER ADMIN PANEL:

 Login credentials
 Tickets sold (Day, Month, Year)
 Admin management: Admin In this system can maintain all the Bus information and
also maintain Bus category, comments etc. In this system admin can maintain the
registered users, manage news, and also admin can generates a reports and manage
the whole system.
 Admin Access for each menus and features
 Admin, employee and manager’s access and roles can be managed.
 Tickets sold (Day, Month, Year)
 Ticket sale graph
 City management
 Manage the city details (edit, status, delete, pagination)

2
 REQUIRMENT SPECIFICATION DOCUMENT

 Route management
 User management
 Manage the user’s details (Edit, Delete, Status)
 Passenger’s management
 Ticket details/Booker details
 Seat details
 Bus type management
In this module admin can add or Update Bus using this module. It contains the
information about the Bus type, photo, description, Location of tour, Available Seats
in Bus etc.
 Ticket booking managed
 Ticket cancellation
 Seat managed
 Payment managed
 Commission managed
 Refund status
 Cancelling Policy
 Bus service details
 Bulk SMS managed
 SMS log details
 Email log details
 Banners managed

ADMIN PANEL:
 Login Statistics
 General settings
 City management
 Route management
 User management
 Passenger’s management
 Bus type management
 Ticket booking

2
 REQUIRMENT SPECIFICATION DOCUMENT

 Ticket management
 Seat management
 Cancel tickets
 Payment management
 Commission management
 Cancellation policies
 Bus service details
 Ticket booking advantage
 Bulk SMS management
 SMS log details Email log details
 Manage banners
 Manage marquee text
 Coupon

AFFILIATE USER PANEL:

 Login Registration
 Forgot password
 User Dashboard
 Commission managed
 Widget managed
 Widget design managed
 User Profile

GUEST USER:

 Search option enabled for source city and destination city.

 Check on available bus details and boarding point.
 Can view numbers of bus snaps and videos.
 Fill details and book, it.
 Payment Gateway enabled.

2
 REQUIRMENT SPECIFICATION DOCUMENT

 Print tickets.
 Cancel Tickets.
 Check refund status by entering the ticket number.
 Coupon codes.
 Promotions codes.
 Wallet offers credits.
 Refer a friend…etc.

WALLET USER:
Sign in sign up options.

 Personal my account details with history.

 Reports for all booked, cancel and return tickets.
 Get Email Options. Get SMS Options.
 Search option enabled for source city and destination city.
 Check on available bus details and boarding point.
 Can view en-numbers of bus snaps and videos.
 User Wallet available.

 Payment Gateway enabled

Payments system might be wallet or other to book ticket and got confirmation
report
we can link our Santimpay payment gateway that is linked with all banks or other
payment Gate way according to the client requirement.
 Print tickets.
 Cancel Tickets.
 Fund transfer.
 Check refund status by entering the ticket number.
 Coupon codes.
 Promotions codes.

2
 REQUIRMENT SPECIFICATION DOCUMENT

 Refer a friend…etc.

TESTING AND FIXING BUGS

 Quality Testing for the entire website
 Unit testing
In this type of testing, the smallest testable parts of the system I.e. units are
individually tested and independently examined for correct functionality. This type
of testing involves both the positive testing and negative testing.
 Integration testing
This is where two or more related programs are tested. The test will
involve two types of approaches i.e. the bottom-up approach that begins
with the simplest task to the most complex part

 System testing
this type of testing we shall test the entire system for functionality to ensure that the
system can process and handle large volumes of data quickly and efficiently.
 Acceptance testing
This test will complete the formal testing process where all the users and the
administrator will use the system so as they get familiar with it. The users test the
system before it is rolled out to be fully used.

i.Beta testing-Carried out at bus company premise. This involve delivering the
system to number of potential clients to use the system and report back to
developer key malfunctions with an understanding that the product is still being
tested.

ii.Alpha testing-It takes place at the developer site. It is the final testing before the
software is about to be released to the hospital for use
 Fixing if any bug is found