SRS SYNOPSIS

For
Punbus-Online Bus Reservation System
Name : - Rajesh Gupta
Reg No. : - 11718235
Section: - K17DP
Roll No: - B34
Submitted to:-PRA
 Contents

1. Introduction
1.1. Purpose......................................................................................................................(3)
1.2. Scope……………………………………………………………………………….(3)
1.3. Overview…………………………………………………………………………...(3)
1.4. Definition…………………………………………………………………………..(4)

2. General Description
2.1. Product Perspective…………………………………………………………………(6)
2.2. Product Function……………………………………………………………………(6)
2.3. User Characteristic………………………………………………………………….(6)

3. Specific Requirements
3.1. Function Requirements specification
3.1.1. Seller use case (posting an item)………………………………………………..(7)
3.1.2. User use case (buying an item)………………………………………………….(8)
3.1.3. User use case (reviewing an item)………………………………………………(9)
3.2. Non Functional Requirement………………………………………………………..(10)

4. Requirement Specification
4.1. External Interface Requirement……………………………………………………..(11)
4.2. Functional Requirement
4.2.1. Search Item………………………………………………………………………(11)
4.2.2. Add Item……………………………………………………………………….(12)
4.2.3. Add Review……………………………………………………………………(12)
4.3. Detailed Non Functional Requirement
4.3.1. Logical Structure of the data……………………………………………………(12)
4.3.2. Security ………………………………………………………………………...(13)

1. Introduction
1.1. Purpose
To make the digital India which is dream and scheme by our Prime Minister of India Mr. Narendra Modi and making cashless India in
which people pay by debit cards or wallet or net banking etc... Punjab Roadways is a commercial organization and having a fleet of 868
buses at present. In addition, 101 buses of Kilometre Scheme are also operating under Punjab Roadways. It has been operating

2.77 lacks km daily for different State/Inter-state routes. These buses are being operated by the PUNBUS on the valid route
permits of the Punjab Roadways and are giving good results.

1.2. Project Scope

 We will provide the best functionality of makemytrip.com, yatra.com etc.

 Our project is the follow on of irctc type’s projects. It will contain most of the functionalities of these services with some new
advancement.
 Our online bus system site will be available 24 hours a day and 7 days in a week. There will be partially maintenance for once a
week.
 We will guide user to book comfortable bus through our online bus system system.
 We will provide the email facility for further correspondence.
 We
1.3. Overview
 The Overall Description section, of this document gives an overview of the functionality of Punbus. It describes the formal and

informal requirements of Passengers.

 The third chapter, Requirements Specification section, of this document is written primarily for the developers and describes in

technical terms the details of the functionality of the bus.

 Both sections of the document describe the same software product in its entirety, but are intended for different audiences and thus

use different language.

0-Level DFD

statics
Statics PUNBUS

Online
Registered user
Ticket
Query updates
Booking

Indent Statics Query

Guest User
 1-Level DFD

User Table

Request Passwo
Generate Reports
rd
Change

Store
Sales Details

Ticket
Confirmed Bill

Genera Reports
tion

User Login Request

View
registratio
n Process Online
Ticket
Users
Booking

View
 Buses

Online
BUS Details

Add/Delete

View View
1.3. Definition

Passenger: -A passenger is a person who book ticket online.

Sign-up/Login: - The user (seller and buyer) can sign - up through their email id or through Facebook or even with twitter. If user has

already signed in he or she can login with the id and password.

Review: - Passengers can review for any buses, their source and destination, fare and many more.
Transaction: - User can pay via online transaction i.e. they have the privilege of online payment as well as they can use COD (cash on

delivery) service.

Cancelation: - It provides user to cancel their ticket i.e. they have the privilege of cancelation of tickets in case of major issues.

2. General Description

2.1. Product Perspective

Online ticket booking system (Punbus) work independently. It needs a platform, software, an internet connection.

2.2. Product Function

The software should contain the capability to connect to database using internet and the device on which it is being installed must also
have internet connectivity. The software must always be connected to the server and the database.

2.3. User Characteristic

 There are several user of the online bus ticket booking site.

 The customer/passenger is expected to be Internet literate and be able to use a search engine. The main screen of the punbus will have
the search function and a link to “bus.infomation”

 The Customer or Passenger is expected to be Internet literate and to be able to use email.

3. Specific Requirement
3.1. Function Requirement Specification

Ref No. Requirements Category

Create and maintain account Evident
View booking history Hidden
Add details of passengers Evident
Delete details of passenger Evident
Update details of passengers Evident
If there time password wrong then stop asking password Frill
Search the require bus Hidden
View the Bus Hidden
GUI should be same in different browsers Evident
System should validate credit card information Evident
Give information about latest bus Evident
Compare the bus in different category Frill

3.2. Non Functional Requirement

Performance Requirements

 You will be sign in within 26sec

 If anybody makes new account then he will receive confirmation email within 6 minutes
 Search results shown within 15 sec.
 Credit cart validate within 5 sec.
 Web support 200 customers logged at the same time.
. 4. Requirement Specification

4. External Interface Requirement

The only link to an external system is the link to the Punbus Database to verify the membership of a Reviewer. The Punbus Database

fields of interest to the Web Publishing Systems are member’s name, membership (ID) number, and email address (an optional field for

the Punbus Database).

The Assign reviews use case sends the Reviewer ID to the Punbus Database and a Boolean is returned denoting membership status.

These update reviews case requests a list of member names, membership numbers and (optional) email addresses when adding a new

Reviewer. It returns a Boolean for membership status when updating a Reviewer.

4.2 Functional Requirement

4.2.1 Search Items

 The passenger chooses how to search the online bus. The choices are by Category, by Price and by Destination
 If the search is by Category, the system creates and presents an alphabetical list of all available buses in the database.
 The customer selects a bus.
 The system creates and presents a list of all buses by that category/price in the database.
 The customer selects an item.
 The customer selects to travel with his chosen category or to return to the list or to the previous list.
4.2.2 Add Item

 The system presents a blank grid to enter the item information.

 The customer enters the information and submits the form.
 The system checks that the name and email address fields are not blank and updates the database.

4.2.3 Add Review

 The system accesses Punbus database and presents an alphabetical list of the permanent members.
 The system transfers the member information from the Punbus database to the Item Manager database. If there is no email address in
the Punbus database, the customer is prompted for an entry in that field.
 The information is entered into the IM database.