lOMoARcPSD|40623461

ONline Cab Booking Sytem SRS template

Software Engineering (Vellore Institute of Technology)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university

Downloaded by Dura (dura80441@gmail.com)
 lOMoARcPSD|40623461

Software Requirements
Specification
for

Online Cab Booking System

Version 1.1 approved

Prepared by Amal John Kachapilly

Car-Go

22-02-2022

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.

Downloaded by Dura (dura80441@gmail.com)

 lOMoARcPSD|40623461

Software Requirements Specification for <Project> Page ii

Table of Contents
Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions..................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Product Scope.................................................................................................................................1
1.5 References.......................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective........................................................................................................................2
2.2 Product Functions...........................................................................................................................2
2.3 User Classes and Characteristics.....................................................................................................2
2.4 Operating Environment...................................................................................................................2
2.5 Design and Implementation Constraints.........................................................................................2
2.6 User Documentation.......................................................................................................................2
2.7 Assumptions and Dependencies......................................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces................................................................................................................................3
3.2 Hardware Interfaces........................................................................................................................3
3.3 Software Interfaces.........................................................................................................................3
3.4 Communications Interfaces............................................................................................................3
4. System Features.......................................................................................................................4
4.1 System Feature 1............................................................................................................................4
4.2 System Feature 2 (and so on)..........................................................................................................4
5. Other Nonfunctional Requirements.......................................................................................4
5.1 Performance Requirements.............................................................................................................4
5.2 Safety Requirements.......................................................................................................................5
5.3 Security Requirements....................................................................................................................5
5.4 Software Quality Attributes............................................................................................................5
5.5 Business Rules................................................................................................................................5
6. Other Requirements................................................................................................................5
Appendix A: Glossary....................................................................................................................5
Appendix B: Analysis Models.......................................................................................................5
Appendix C: To Be Determined List............................................................................................6

Revision History
Name Date Reason For Changes Version
Initial 10-02-2022 Initial Document 1.0
User Classes 13-02-2022 Modifying User Classes 1.1
Interface UI 14-02-2022 Adding Pictures of sample UI 1.2
System Feature 16-02-2022 System Features Entry 2.0

Downloaded by Dura (dura80441@gmail.com)

 lOMoARcPSD|40623461

Software Requirements Specification for <Project> Page 1

1. Introduction
Transportation plays an important role in both our personal life and in global economy. Proper
system of transportation could have a great impact in industrial development. This project will
make the system of accessing means of transportation much more simple and efficient. The
alternative system requires the client to call up a company which then allocates a driver to the
client. This can be further automated using an app to save time for both client and the company.
First the client will book for service in the app, then the customer will be indicated on the map
provided in drivers app, a driver can choose between multiple customers in different locations in a
manner that minimizes un-fared travelling. After completing the service a fare amount will be
calculated and provided to client, which they would be required to pay through means of e-wallet or
cash.

1.1 Purpose
The purpose of this SRS document (version 1.0) is to specify the software requirements of the
Online Taxi Booking platform. It will be a complete specification of what this system provides at
both client and driver end.

1.2 Document Conventions

Every requirement is given its own priority. Font Size 12, Times New Roman, Line spacing 1.0.

1.3 Intended Audience and Reading Suggestions

The SRS document is intended to be read by every department (HR, Marketing, Technical and
other) to provide a clear idea of the features provided in this project. To make the ideas conceivable
for employee in different department, the report would use basic language without going into
detailed technical details.

1.4 Product Scope

The projects aim is to automate the system of hiring a driver by calculating and collecting fare by
the means of the app. The app also to collect and process information regarding the client to
optimize quality of service. The app would also collect and store data of registered users in database
.It transforms current system to a centralized.

1.5 References

Downloaded by Dura (dura80441@gmail.com)

 lOMoARcPSD|40623461

Software Requirements Specification for <Project> Page 2

2. Overall Description

2.1 Product Perspective

The product described in the SRS document is an automated and centralized alternative to
traditional cab booking system. The product will replace the call and book feature in traditional
system with an online booking feature, In additional the closest driver will be assigned based on
availability and distance.

2.2 Product Functions

Client end indicates features allowed for client, product function are abstracted functions of the
software and service provider is the driver that provides service.

 Register and create account (client end and service provider)

 Book taxi (client end)
 Payment of fare (client end)
 Select Service type( Client End )
 Assigning a driver (Product function)
 Calculating fare (Product function)
 Storing client Data (Product function)
 Selecting customers (Service provider)
 Collecting fee (Service provider or product function)

2.3 User Classes and Characteristics

Daily Basic User: These users use our services on a daily basis(4-7 per week) to get to work and
back home. These users prefer basic and cheap mode of transportation.

Daily Luxury User: These are the users who prefer luxury rides with additional facilities on a daily
basis (4 -7 per week).

Committed Basic User: This category users our basic cab service for every travelling need on a
daily basis(12+ per week).

Committed Luxury User: This category users our luxury cab service for every travelling need on
a daily basis(12+ per week)..

Weekly Basic Users: This category of users apply for our basic service (1 -3 per week)

Weekly Luxury Users: This category of users apply for our basic service (1 -3 per week).

Occasional Users: These are the users that uses our services very less for their special or
emergency needs.

Weekly Basic Users: This category of users apply for our basic service (1 -3 per week)

Basic Service Provider: These are the drivers with basic rides.

Luxury Service Provider: These are the drivers with luxury rides.

Downloaded by Dura (dura80441@gmail.com)

 lOMoARcPSD|40623461

Software Requirements Specification for <Project> Page 3

2.4 Operating Environment

The software is designed to run in android devices. It requires a device with Android 4.4 or higher
with a stable internet connection and GPS access.

2.5 Design and Implementation Constraints

Lack of GPS access on device would make it harder to locate user and driver. Unstable internet
connection will interfere with the operation of the app.

2.6 User Documentation

Tutorial for using the app will be provided within the app for both drivers and users.

2.7 Assumptions and Dependencies

Assumption is made that there is a daily market saturated with customers. If this assumption fails to
hold up number of our drivers would outweigh the number of users in a timespan and hence
decreasing profits.

Assumption is made that there is enough number of drivers within a reasonable distance to most
locations.

Assumption is made that users have a stable Internet and GPS connection.

3. External Interface Requirements

3.1 User Interfaces

Authentication Screen will have Username and password text box and a
login button(register option provided).

Registration Screen will have textboxes to enter details to register as a

user.

Home page will have a carousel of ads and services and a Book Ride
Button.

Booking Page will have an option to choose pickup and drop off
location. It will show optimal route to minimize costs.

Downloaded by Dura (dura80441@gmail.com)

 lOMoARcPSD|40623461

Software Requirements Specification for <Project> Page 4

Later the user will be given an option to choose type of service.

After the completion of service the user will be required to pay either by
cash or E-wallet.

3.2 Hardware Interfaces

The software would need basic access to memory, processors and other such components required
to run any Application on a Smartphone. Other than that the app would require access to GPS and
Internet.

3.3 Software Interfaces

The product runs in Android 4.4 or higher. The personal data of user and his/her travel history will
be stored as cached data to optimize the App. Data regarding the booking and location will be sent
to the server which marks the customer on the providers map.

Downloaded by Dura (dura80441@gmail.com)

 lOMoARcPSD|40623461

Software Requirements Specification for <Project> Page 5

4. System Features

4.1 Authentication
This includes login and register feature that allows user to gain access into app

4.1.1 Description and Priority

Before providing access to our services the user has to be recognized for both security and
performance concerns. Login would allow the user to enter his/her Id and Password to gain
access. If he/she does not have an active account the client would be allowed to register as a
new user.

4.1.2 Stimulus/Response Sequences

On the event of opening the app for the first time the user would be shown a login screen,
from here the user can enter his/her login id and password and click login button to gain
access. If they do not have an active account they may click register button and submit their
details.

4.1.3 Functional Requirements

Login.ID.Box : A text field will be provided for the entry of login ID of user.
Login.Key.Box : A text field will be provided for the entry of login password of user.
Login.Submit.Button: A button will be provided to Submit login info.
Register.Redirect.Button: A button will be provided to redirect to register page.
Register.Name.Box: A text field to enter name of user.
Register.ID.Box: A text field to enter ID of user.
Register.PasswordA.Box: A text field to enter password of user.
Register.PasswordB.Box: A text field to confirm password of user.
Register.Date.Drop: A drop down menu to choose Birth Date
Register.Email.Box: A text field to enter email id of user.
Register.Submit.Button: A button will be provided to submit registration info.

4.2 Home View

4.2.1 Description and Priority

The home view displays the home page including advertisements, new features and popular
offers.

4.2.2 Stimulus/Response Sequences

After authentication the user will be redirected to home page where they can view features and
offers and have an option to book a ride.

4.2.3 Functional Requirements

Downloaded by Dura (dura80441@gmail.com)

 lOMoARcPSD|40623461

Software Requirements Specification for <Project> Page 6

Home.View.Carousel : At the top of the home page a carousel will be provided which displays new
features and news.
Home.Features.List : A horizontal list of popular offers will be displayed.
Home.Book.Button : This allows user to redirect to booking page.
Home.Profile.Button : This allows user to redirect to profile page.

4.3 Book View

4.3.1 Description and Priority

This screen allows the user to enter the detail regarding his/her booking.

4.3.2 Stimulus/Response Sequences

After clicking the Home.Profile.Button user is directed to booking page where he/she can enter ride
details including locations and type.

4.3.3 Functional Requirements

Book.Map.Window : The map allows the user to select both pickup location and destination.
Book.Ride.List : This offers a list of rides types that the user will be allowed to select for his/her
booking.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

<If there are performance requirements for the product under various circumstances, state them here and
explain their rationale, to help the developers understand the intent and make suitable design choices.
Specify the timing relationships for real time systems. Make such requirements as specific as possible. You
may need to state performance requirements for individual functional requirements or features.>

5.2 Safety Requirements

<Specify those requirements that are concerned with possible loss, damage, or harm that could result from
the use of the product. Define any safeguards or actions that must be taken, as well as actions that must be
prevented. Refer to any external policies or regulations that state safety issues that affect the product’s
design or use. Define any safety certifications that must be satisfied.>

5.3 Security Requirements

<Specify any requirements regarding security or privacy issues surrounding use of the product or protection
of the data used or created by the product. Define any user identity authentication requirements. Refer to

Downloaded by Dura (dura80441@gmail.com)

 lOMoARcPSD|40623461

Software Requirements Specification for <Project> Page 7

any external policies or regulations containing security issues that affect the product. Define any security or
privacy certifications that must be satisfied.>

5.4 Software Quality Attributes

<Specify any additional quality characteristics for the product that will be important to either the customers
or the developers. Some to consider are: adaptability, availability, correctness, flexibility, interoperability,
maintainability, portability, reliability, reusability, robustness, testability, and usability. Write these to be
specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various
attributes, such as ease of use over ease of learning.>

5.5 Business Rules

<List any operating principles about the product, such as which individuals or roles can perform which
functions under specific circumstances. These are not functional requirements in themselves, but they may
imply certain functional requirements to enforce the rules.>

6. Other Requirements
<Define any other requirements not covered elsewhere in the SRS. This might include database
requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so
on. Add any new sections that are pertinent to the project.>

Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You
may wish to build a separate glossary that spans multiple projects or the entire organization, and just
include terms specific to a single project in each SRS.>

Appendix B: Analysis Models

<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-
transition diagrams, or entity-relationship diagrams.>

Appendix C: To Be Determined List

<Collect a numbered list of the TBD (to be determined) references that remain in the SRS so they can be
tracked to closure.>

Downloaded by Dura (dura80441@gmail.com)