Bus Ticket Reservation System: Software Requirements Specification

Software Requirements Specification
SRS DOCUMENT
Bus Ticket Reservation

System
Version 1.0
Group Id: F14CS6191C910

Supervisor Name: Muhammad Tariq Pervez
Page 1 of 25

SRS DOCUMENT
Date
(dd/mm/yyyy)
09/01/2015
Version
1.0
Author
Description
Bus Ticket
Reservation System
will automate ticket
reservation system
to bring a change in
the trend of manual
ticket reservation
system and
facilitates customers
to avoid long waiting
queuing as well as
easy management of
records.
MC130400035
MC130200704
Page 2 of 25

SRS DOCUMENT
Table of Contents
Scope of the project
Functional
Requirements
requirements
Use Case Diagram
Non
Functional
Usage Scenarios
Adopted Methodology
Work Plan
Page 3 of 25

SRS DOCUMENT
SRS Document
Scope of the Project:
It is good idea for Bus travelling company that wants to automate and
improve its ticket reservation system to bring a change in the trend of manual
ticketing reservation system. This system will bring improvements in the
management and revenue of the bus company. It could help in many ways in
improving services to customers.
As we see that in manual ticketing system all the records are maintained in
the hard document format which needs special place and protection to keep the
data record saved.
By using this Automatic System Company can easily handle the big set up of bus
system like Daewoo, Faisal movers etc.
Functional and Non Functional Requirements

Functional Requirements:
Functional requirements describe the behaviors, functions or services of the
system that support user goals, tasks or activities:
System should provide facility for all actors to log into the website.
System should provide facility to send email or SMS to all actors if they forgot
their password.
Page 4 of 25
SRS DOCUMENT
System should provide facility to register new visitors by itself.
System should provide facility for all actors to change his password.
System should provide facility for all customers to change their profile.
System should provide facility to only admins to add, delete and edit news
and events.
System should provide facility to admins to reset users passwords.
System should provide facility to only admins to block, view and edit the
customers.
System should provide facility to only admins to add, block, view, edit to all
employees.
System should provide facility to only admins to change fares of tickets,
cargo and waiting rooms.
System should provide facility to only admins to add new terminals (add new
cities in routes).
System should provide facility to only admins to generate staff salary slips.
System should provide facility to only admins to view the credit card details
of customers.
System should provide facility to call operators for the booking of the tickets
and booking cargo consignments but not confirms. Create customers account
to login into the site (auto generated after booking of the ticket).
System should provide facility to managers to confirm the booking if payment
is received.
System should provide facility when ticket gets confirmed email and SMS
should be sent to the customer.
System should provide facility to managers for creation of all the ticket slips.
System should provide facility to staff to check their duties time and place of
duty. Each bus has total four members of the staff (Driver, Security guard,
Doctor, Bus hostess). System should provide facility to each staff member to
enter their employee id and check his/ her current schedule.
System should provide facility to customers for booking of the tickets and
booking of cargo consignments but it should not be giving confirmation.
System should provide facility to customers to edit profile and change their
password.
System should provide facility to customers to register on site.
System should provide facility to customers for searching reservations.
System should provide facility to customers to track their consignments.
System should provide facility to generate the pdf to confirm the tickets and
confirm the cargo reservations.
System should provide facility to save the reservations of every customer.
System should provide 5% discount to all regular customers for returning
customers only using the existing account.
Company provides 10% discount to family. (If buys more than 5 tickets at
once.)
Each bus contains two extra seats for emergency cases extra seats has extra
reservation charges, 30% extra charges plus regular ticket price.
Page 5 of 25

SRS DOCUMENT
Query the list of buses for two weeks (Only two weeks advance reservation is
available).
No reservation before two days can be made.
On cancelation of reservation 50% will be deducted from the whole amount.
(Cancellation interface closed before 3 hours of the confirmation of the ticket
date and time).
Changing the reservation date or time may cause 20% deduction from the
whole amount. (Cancellation interface will be closed before 3 hours of the
confirming cargo date and time).
System should provide facility to stay in room during the journey for the VIP
customers and the paying customers.
System should provide facility for booking tables in the restaurants during the
journey to the vip customers.
Online Payment mode is credit card and if customer has no credit card than
customer should send money through easy paisa when a money transfer sms
is received by the company with customer id number and phone no. than the
ticket will be confirmed.
Money will be deducted from the customers account after a verification call.
Non Functional Requirements:

The Non-Functional Requirements are the requirements that tells us about the
functionality of the system as well as how the system will be functioning. If
functional requirements are well elaborated and fulfilled but non-functional
requirements are not taken under consideration then the software will be rejected.
So, we can say that both the functional and the non-functional requirements should
be fulfilled by the software system.
Non-Functional Requirements are as follows:
Performance
Usability
User friendly
Maintainability
Flexibility
Performance:
This system will allow users (Customers, Managers or Admins) faster access
of the system.
Usability:
This system will allow all users of average IQ to use this system effectively
without the need of any formal training.
User friendly:
It will have a user-friendly interface so that users are able to understand the
system easily and can work effectively.
Page 6 of 25

SRS DOCUMENT
Maintainability:
Administrators should be able to maintain different aspects of the system like
maintaining the record of the users and space allocated to each user.
Flexibility:
System should be flexible as if any user requires more space then
administrator will allocate more space to that user.
Page 7 of 25

SRS DOCUMENT
Page 8 of 25

SRS DOCUMENT
Use Case Diagram(s)
Page 9 of 25

Use Case Title:
SRS DOCUMENT
Visits the list of today schedule
Use Case Id:
Requirement Id:
Description:
Pre-Conditions:
Staff visits the list of today schedule.

Staff Logins in the System.
Task Sequence:
Staff clicks list of today schedule.

Staff selects list of today schedule.
System shows the schedule
Staff views it.
Exceptions:
Invalid time of duty
Post Conditions:
Staff has checked the today Schedule
Unresolved issues:
None
Authority:
Staff
Modification history:
Author:
1.0
Page 10 of 25

Use Case Title:
SRS DOCUMENT
Reads Place of duty
Use Case Id:
Requirement Id:
Description:
Pre-Conditions:
Staff reads place of duty.

Staff logins in The System.
Task Sequence:
Staff clicks reads place of duty.

Staff selects place of duty.
System displays the place of duty.
Staff checks it.
Exceptions:
Invalid place of duty
Post Conditions:
Staff has checked the place of duty.
Unresolved issues:
None
Authority:
Staff
Author
1.0
Page 11 of 25

Use Case Title:
SRS DOCUMENT
Reads the time of duty
Use Case Id:
Requirement Id:
Description:
Pre-Conditions:
Staff reads the time of duty

Staff logins in the System.
Task Sequence:
Staff clicks read the time of duty.

System displays the time of Duty.
Staff checks the time of duty.
Exceptions:
Invalid time of duty
Post Conditions:
Staff reads the duty time in list.
Unresolved issues:
None
Authority:
Staff
Author
1.0
Page 12 of 25

Use Case Title:
SRS DOCUMENT
Makes user account
Use Case Id:
Requirement Id:
Description:
Pre-Conditions:
Task Sequence:
4
Call operator makes user account in Buss system.
Call operator Logins in the System.
Call operator clicks Creates user account.
System opens the form
Call operator fills it.
System creates the user Account.
Exceptions:
Invalid account
Post Conditions:
Call operator has makes user account.
Unresolved issues:
None
Authority:
Call operator
Author
1.0
Page 13 of 25

Use Case Title:
SRS DOCUMENT
Creates ticket/cargo booking consignments
Use Case Id:
Requirement Id:
Description:
consignments in this system.
Call operator creates ticket/cargo booking
Pre-Conditions:
Call Operator has login in the system.
Task Sequence:
Booking Consignments.
Call operator clicks and Creates Ticket/Cargo

System responds to create it.
Call operator gets the message
System creates ticket/cargo booking consignments
Exceptions:
Invalid consignments
Post Conditions:
consignments.
Call operator has Created ticket/cargo booking
Unresolved issues:
None
Authority:
Call operators.
Author
1.0
Page 14 of 25

SRS DOCUMENT
Use Case Title:
Searches websites
Use Case Id:
Requirement Id:
Description:
Pre-Conditions:
User searches website in this system.

Opens the website list
Task Sequence:
User searches website

User selects the website of bus System.
Exceptions:
Invalid Searches
Post Conditions:
User has searched websites;
Unresolved issues:
None
Authority:
User
Author
1.0
Use Case Title:
Registers in Bus system
Use Case Id:
Requirement Id:
Description:
Pre-Conditions:
7
User registers in bus system.
User has visited the website.
Page 15 of 25

SRS DOCUMENT
User clicks the registers in bus system;
Task Sequence:
System opens the form.

User fills it.
System pops up a message of Success in Registration.
Exceptions:
Invalid Registration form.
Post Conditions:
User Registers in the Bus System.
Unresolved issues:
None
Authority:
User
Author
1.0
Use Case Title:
Conforms booking status
Use Case Id:
Requirement Id:
Description:
system.
Pre-Conditions:
8
Bus manager conforms booking status in this
Bus Manager Logins in the System.
Page 16 of 25

SRS DOCUMENT
Bus manager clicks Confirms booking status
Task Sequence:
System responds.
He/ She clicks on Yes
System confirms the booking
Exceptions:
Invalid booking
Post Conditions:
Bus Manager has confirmed the booking.
Unresolved issues:
Authority:
None
Bus Manager
Author: 1.0
Use Case Title:
Makes tickets/cargo slips
Use Case Id:
Requirement Id:
Description:
Pre-Conditions:
Task Sequence:
9
Bus manager makes the ticket /Cargo slips.
Bus Manager Login in the bus System.
Bus manager clicks Make Ticket/Cargo Slips.
System opens the options.
Page 17 of 25

SRS DOCUMENT
She/he selects one option.
Save it.
Generate the tickets/ Cargo slips.
Exceptions:
Invalid slips
Post Conditions:
Bus Manager Creates the ticket/cargo slips.
Unresolved issues:
Authority:
None
Bus manager
Author: 1.0
Use Case Title:
Generate bus staff salary
Use Case Id:
10
Requirement Id:
Description:
Pre-Conditions:
Task Sequence:
10
Admin generates bus staff salary.
Admin has login in the System.
Admin clicks Generates the staff Salary
System generates the staff salary
Page 18 of 25

SRS DOCUMENT
System saves it.
Exceptions:
Post Conditions:
Admin has generated the data on bus staff salary;
Unresolved issues:
None
Authority:
Admin
Author: 1.0
Use Case Title:
Change cargo fares
Use Case Id:
11
Requirement Id:
11
Description:
Admin changes cargo fares.
Pre-Conditions:
Cargo fares system is running.
Task Sequence:
Admin clicks Change cargo Fares

Admin selects the cargo fares.
Page 19 of 25

SRS DOCUMENT
Updates it.
Saves it.
Exceptions:
Invalid cargo fares
Post Conditions:
Admin has updated the Cargo Fares
Unresolved issues:
None
Authority:
Admin
Author:
1.0
Use Case Title:
Add new terminal in city
Use Case Id:
12
Requirement Id:
Description:
Pre-Conditions:
Task Sequence:
12
Admin add new terminal in city.
New Terminal position has checked.
Admin clicks on the new terminal
Admin selects the new terminal in city.
Page 20 of 25

SRS DOCUMENT
System saves it.
System creates new terminal.
Exceptions:
Invalid terminal
Post Conditions:
Admin has added the new Terminal in the city.
Unresolved issues:
None
Authority:
Admin
Author:
1.0
Use Case Title:
Reset password
Use Case Id:
13
Requirement Id:
Description:
Pre-Conditions:
Task Sequence:
13
Admin reset password.
Admin has login in the System.
Admin clicks on the reset password
Admin selects the User.
Page 21 of 25

SRS DOCUMENT
Updates the password
System saves it.
System sends email.
Exceptions:
Password is not valid.
Post Conditions:
Admin has reset the password on system;
Unresolved issues:
Authority:
None
Admin
Author: 1.0
Use Case Title:
Gets email/SMS for conformation
Use Case Id:
14
Requirement Id:
Description:
14
Customer gets email/SMS for confirmation.
Pre-Conditions:
Customer has login in the System.
Task Sequence:
Customer checks the inbox.

Gets email for confirmation.
Page 22 of 25

SRS DOCUMENT
System saves it.
Exceptions:
Invalid confirmation.
Post Conditions:
Customer has received email.
Unresolved issues:
None
Authority:
Customer
Author: 1.0
Use Case Title:
Pays for booking
Use Case Id:
15
Requirement Id:
Description:
Pre-Conditions:
Task Sequence:
15
Admin pays for booking.
Pays for booking system is running.
Admin clicks on the pays for booking.
Admin selects the pays for booking.
Page 23 of 25

SRS DOCUMENT
System saves it.
Exceptions:
Invalid payment
Post Conditions:
Admin has pays the booking;
Unresolved issues:
None
Authority:
Customer
Author: 1.0
Adopted Methodology
We have selected the VU process model. It is combination of water fall and
spiral model. The waterfall model is also called linear and sequential model because
the flow of activities in this model are rather linear and sequential. In this model the
software development activities move to the next phase only after the activities in
the current phase are over.
The most important advantage of the waterfall model lies in the fact that
there is minimum planning problem for the steps that are to follow. There is certain
amount of discipline that is enforced as one has to only look into one phase of the
process at any given point of time. In other models it is often difficult to nail the
start and end of the said phase which is not the case with the waterfall model. The
project does not slip on its schedule. The number of resources working on the
project does not keep on increasing with each passing day. In the waterfall model
none of the stages can be started off before the preceding stage is complete.
The original waterfall model designed by Royce consisted of the following
seven stages:
Specification of Requirements
Design
Construction
Integration
Testing and Debugging
Installation
Maintenance
The spiral model reflects the development approach in many industries much
better than the other process models do. It uses a stepwise approach which
maintains the number of hardware phases but also contains the development
of hardware. This way the developers and the customer can understand and
react much better to risks in the evolutionary process
Work Plan
Page 24 of 25

SRS DOCUMENT
Page 25 of 25

Bus Ticket Reservation System: Software Requirements Specification

Uploaded by

Copyright:

Available Formats

Bus Ticket Reservation System: Software Requirements Specification

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Bus Ticket Reservation System: Software Requirements Specification

Uploaded by

Copyright:

Available Formats

Software Requirements Specification