ABHIBUS

SOFTWARE REQUIREMENTS SPECIFICATIONS

<Version 1.0>

1
 INDEX

Sl.No. TOPIC Page No.

1. INTRODUCTION 3
1.1 PURPOSE 3
1.2 SCOPE OF PROJECT 3
2. GENERAL DESCRIPTIONS 4
2.1 PRODUCT PERSPECTIVE 4
2.2 PRODUCT FUNCTIONS 4
2.3 USER CHARACTERISTICS 4
2.4 ADMIN CHARACTERISTICS 5
2.5 GENERAL CONSTRAINTS 5
2.6 ASSUMPTION AND DEPENDENCIES 5
3. GENERAL REQUIREMENTS 6
3.1 EXTERNAL USER INTERFACE 6
3.1.1 LOGIN INTERFACE 6
3.1.2 REGISTRATION INTERFACE 7

3.1.3 SEARCH INTERFACE 8

3.1.4 PAYMENT INTERFACE 9
3.1.5 BUS BOOKING INTERFACE 10
3.2 USE-CASE 11
4. DATA FLOW DIAGRAMS 12
4.1 DFD FOR LOGIN 12
4.2 DFD FOR ADMIN 12
4.2 DFD FOR USER 13

5 E-R DIAGRAM 14

2
 1. INTRODUCTION

1.1 Purpose

The purpose of this document is to give a detailed description of the requirements for the “abhibus”
web application. This will illustrate the purpose and complete declaration for the development of
system. This will also explain system constraints, interface and interactions with other external
applications. This document is primarily intended to be proposed to a customer for its approval
and a reference for developing the first version of the system for the development team.

1.2 Scope of Project

The abhibus is an efficient and user friendly web application which is intended to enable users to
book bus tickets from any source to any destination in a quick, simple and secure way. This
application provides information about wide range of buses including their fares, timings and
routes and process bookings and payments. Registered users can search for available tickets, book
it with their abhibus wallet amount and also cancel the tickets whereas the unregistered users can
search for the available buses based on their boarding and destination points.
Users can add amount to their wallet at any time and each time they book a ticket the corresponding
bus fare will be deducted from the wallet amount. Available buses, their fare and timing
information based on the boarding point and destination point will be fetched from the database
and shown to the user. Only the admin has access to bus related operations like updating fares,
updating routes, adding or removing bus operators and the authority to remove a user and view the
users.

3
 2. GENERAL DESCRIPTIONS

2.1 Product Perspective:

 This product is used to book bus tickets from available bus operators to different routes at different times.
 Users can select bus types of their choice and also their preferred seats.
 Users can view the status (i.e. available, unavailable, selected etc.) of each seat in the bus.
 Users can select the boarding points according to their convenience.
 Users can pay the fare using the wallet facility provided.
 Users can cancel booked tickets according to the cancellation policy.

2.2 Product Functions:

2.2.1User

 Search Bus: Search for buses available based on destination.

 View Booked Tickets: View booked tickets.
 Cancel Booked Tickets: Cancel booked tickets.
 Add Money to Wallet: Add extra cash into wallet.

2.2.2 Admin

 Add/Remove Bus: Add new bus routes and discard routes which are not in service.
 Add/Remove Operator: Add new operators and discard ones which are not available.
 View/Delete User: View registered user and delete unwanted accounts.
 Update User: Update user details.

2.3 User Characteristics:

 User can book tickets to their preferred destinations from the available bus operators.
 User can select a maximum of 6 seats from the available pool of seats.
 User can cancel tickets according to the cancellation policy.
 User can view the booked tickets.
 User can add money to the wallet from where money will be deducted when a booking is performed.
4
2.4 Admin Characteristics:

 Admin can add/modify the bus details.

 Admin has rights to update and remove users.
 Add, update and remove bus routes.

2.5 General Constraints:

 A user can book a maximum of 6 tickets at a time.

 Bus operators cannot enroll themselves and only admin can manage the enrollment.
 Tickets can be cancelled only according to the cancellation policy.

2.6 Assumptions and Dependencies:

 Each user is managed and monitored by admin.

 All the bus operators and bus routes are managed by the admin.

5
 3. GENERAL REQUIREMENTS

3.1 External User Interfaces

There are three main user interfaces:

 Login Interface
 Registration Interface
 Search Interface
 Payment Interface
 Bus booking interface

3.1.1 Login Interface

The login page allows the user to enter their credentials. Based on the credentials they will
redirected to their respective interfaces.

6
3.1.2 Registration Interface
The registration page allows the user to enter their credentials. Based on the credentials they will
redirected to their respective interfaces.

7
3.1.3 Search Interface
The search page allows the user to search for the available buses based on their boarding and
dropping points including the date of journey.

8
3.1.3 Payment Interface
The payment page allows the user to make the payment for the seats opted for the journey.

9
3.1.3 Bus booking Interface
The payment page allows the user to make the payment for the seats opted for the journey.

10
3.2 Use-Case Diagram

11
 4. DATA FLOW DIAGRAMS

4.1 DFD for Login

4.2 DFD for Admin

12
4.3 DFD for User

13
4.4 E-R Diagram

14