Software Requirements

Specification
for

Cab Share

Version 1.0 approved

1. Sharyar Anwer 1912130

2. Aniq Murad 1912105

SZABIST

10th Nov 2022

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
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
Software Requirements Specification for <Project> Page 1

1. Introduction

1.1 Purpose
The purpose of this application is to provide carpooling service to SZABISTians. As petrol is
getting expensive so it is difficult for students to pay high fare for transportation. Many students
are connecting to this service through WhatsApp groups, where there is a lot of mess and no one
is able to find a suitable partner to share ride with because of which we are making this App which
will help students and faculty to share rides among SZABISTians and there will be less hassle in
finding a suitable partner to share your ride with.

1.2 Document Conventions

 Regular – Times New Roman – font size 12
 Sub - Headings – Times New Roman – font size 12 (bold)
 Headings – Times New Roman – font size 14 (bold)

1.3 Intended Audience and Reading Suggestions

This project is for SZABIST students and faculty members.

1.4 Product Scope

The scope of this App is within the SZABIST and can be used by students and faculties. Users
will be able to login with their SZABIST ID. The App will ask if the user is driver or a passenger.
Both driver and passenger will be able to share the schedule, starting and destination points
which will help to find a suitable partner.

1.5 References
<List any other documents or Web addresses to which this SRS refers. These may include user
interface style guides, contracts, standards, system requirements specifications, use case
documents, or a vision and scope document. Provide enough information so that the reader could
access a copy of each reference, including title, author, version number, date, and source or
location.>

2. Overall Description

2.1 Product Perspective

This idea is derived from Uber Pool, but Uber Pool is not available in Pakistan. Secondly Uber
Pool is for all general public but in our application, it can only be used by SZABIST students and
faculties.
Software Requirements Specification for <Project> Page 2

2.2 Product Functions

 Sign In
 Sign Out
 Book a ride
 Accept a ride
 Select if user is a driver or a passenger
 Complain

2.3 User Classes and Characteristics

This application is suitable for SZABIST students and faculties who are willing to share rides due
to high fare of transportation, and also for the users who owns a bike or car and willing to share
their vehicle with other mates so that everyone can have easy and low-cost transportation.

2.4 Operating Environment

Software Preference: A stable internet connection is required to run this application.
Hardware Preference: A smart phone is required to run this application.

2.5 Design and Implementation Constraints

Project will be created on Visual Studio Code. For front-end we will use React Native and Java
Script. For back-end we will use Node.js.
The limitations of this application are we cannot include an e-wallet in our applications because
we do not have permission to collect money from anyone else’s bank account.
Another limitation of this application is that the amount is fixed by the owner of vehicle which
cannot be bargained.
Software Requirements Specification for <Project> Page 3

2.6 User Documentation

Software Requirement Specification (SRS) and Software Design Specifications (SDS) will be
included.

2.7 Assumptions and Dependencies

Since this is a mobile application some UI features may differ on android and IOS phones.
We will be using google sign in and google map in our application.
firebase database will be used in our application.

3. External Interface Requirements

3.1 User Interfaces

Software Requirements Specification for <Project> Page 4

Page1:
Software Requirements Specification for <Project> Page 5

Page2:
Software Requirements Specification for <Project> Page 6

Page3:

Page4:
Software Requirements Specification for <Project> Page 7

3.2 Hardware Interfaces

Only requires a mobile phone with a stable internet connection.

3.3 Software Interfaces

OS: android and IOS
Database: firebase
Tools: VS Code
Library: React Native and NodeJS. Node.js is an open-source, cross-platform, back-end,
JavaScript runtime environment that executes JavaScript code outside a web browser.
Integrated commercial components: google sign in and google map

3.4 Communications Interfaces

A good internet connection required to run this project on smartphones with SZABIST official
email ID.

4. System Features
The below are the use cases of our project:
4.1 Login
Use Case ID 1

Actors User

Pre-Condition A SZABIST Email is required to login.

Scenario

Step# Action Software Reaction

1 Take Inputs Check Validations

2 Login User gets logged in and proceeds to

next page
Post Condition

Step# Description

1 User provide valid credentials

2 User gets logged in

Use Case NA
Cross
Reference
Software Requirements Specification for <Project> Page 8

4.2 Select if user is a passenger

Use Case ID 2

Actors User

Features

Pre-Condition User must be signed in

Scenario

Step# Action Software Reaction

1 User clicks “I need a ride” User is guided to ride booking interface

button
2

Post Condition

Step# Description

1 User input details about

pickup and drop-off
location, timing etc.
Use Case NA
Cross
Reference

4.3 Select if user is a driver

Use Case ID 3

Actors User

Features

Pre-Condition User must be signed in

Scenario

Step# Action Software Reaction

1 User clicks “I am driving” User is guided to select passenger

button interface
2

Post Condition

Step# Description
Software Requirements Specification for <Project> Page 9

1 User input details about

pickup and drop-off
location, timing etc.
Use Case NA
Cross
Reference

4.4 Book a ride

Use Case ID 4

Actors User

Features

Pre-Condition User must be signed in

Scenario

Step# Action Software Reaction

1 User inputs the pickup and

drop off location.
2 User inputs the time at The software shows all the available
which they want the ride. drivers.
3 User selects a driver and A message is displayed “Your ride is
press ‘Book’ button. booked”
Post Condition

Step# Description

1 User clicks on Ok

2 User goes to homepage.

Will be reminded 20 mins
before the booking.
Use Case NA
Cross
Reference

4.5 Accept a ride

Use Case ID 5

Actors User

Features

Pre-Condition User must be signed in

Scenario
Software Requirements Specification for <Project> Page 10

Step# Action Software Reaction

1 User inputs the pickup and

drop off location.
2 User inputs the time at The software shows all the available
which they will be driving passengers
3 User selects a passenger A message is displayed “Your cab share
and press ‘accept’ button. partner is booked”
Post Condition

Step# Description

1 User clicks on Ok

2 User goes to homepage.

Will be reminded 20 mins
before the booking.
Use Case NA
Cross
Reference

4.6 Logout
Use Case ID 6

Actors User

Features

Pre-Condition User must be signed in

Scenario

Step# Action Software Reaction

1 User clicks Log Out Button User gets logged out

Post Condition

Step# Description

1 User clicks on Log Out

2 User gets logged out

Use Case NA
Cross
Reference
Software Requirements Specification for <Project> Page 11

4.7 Complain
Use Case ID 7

Actors User

Features

Pre-Condition User must be signed in

Scenario

Step# Action Software Reaction

1 User clicks Complain Goes to complain page

Button
2 User posts a complain App registers the complain

Post Condition

Step# Description

1 User goes to home page

Use Case NA
Cross
Reference

5. Other Nonfunctional Requirements

5.1 Performance Requirements

 Optimized code
 Stable Internet connection

5.2 Safety Requirements

The application will be updated so the users do not have to face any kind of issue such as bug in the
application while using it.

5.3 Security Requirements

Since the user is signed in using their google account so their information would be completely
secured by google.
Software Requirements Specification for <Project> Page 12

5.4 Software Quality Attributes

 Usability: The application has a user-friendly environment so that any user can easily use
it.
 Maintainability: The application is designed so that it can be maintained easily by any
developer.
 Security: To keep the safety of user’s sensitive information, security has to be maintained
to keep the user’s credentials and database safe.

5.5 Business Rules

N/A

6. Other Requirements
N/A

Appendix A: Glossary
N/A

Appendix B: Analysis Models

Appendix C: To Be Determined List

N/A