Software Requirements Specifications

<Project Title>

Project Code:

Internal Advisor:

Shahbaz Siddiqui

External Advisor:

Project Team:

Reshail alvi k132180

Rohan Mahesh k132042
Umer Khalid k132048
Agha zarwali k132054

Submission Date: 28-12-16

_____________________
Project Advisors Signature

_____________________
Project Coordinators Signature Document
<Project code> Software Requirements Specifications <Version x>

Document Information

Category Information

Customer FAST-NU
Project Auto Expert and Road guide
Document Requirement Specifications
Document Version 1.0
Identifier KSPZS01-2003-RS
Status Draf
Author(s) Reshail alvi,Rohan Mahesh,Umer Khalid,Agha zarwali
Approver(s) Shahbaz Siddiqui
Issue Date 26-12-16
Document Location
1. Advisor
Distribution
2. Project Coordinators office (through Advisor)

Definition of Terms, Acronyms and Abbreviations

Term Description
AI Artificial intelligence

GPS Global Positioning System

Page 2 of 2
18
<Project code> Software Requirements Specifications <Version x>

Page 3 of 3
18
<Project code> Software Requirements Specifications

Table of Contents

1. INTRODUCTION...............................................................................................................................5
1.1 Purpose of Document..............................................................................................................................5
1.2 Project Overview.....................................................................................................................................5
1.3 Scope.......................................................................................................................................................5

2. OVERALL SYSTEM DESCRIPTION..................................................................................................5

2.1 User characteristics.................................................................................................................................5
2.2 Operating environment...........................................................................................................................5
2.3 System constraints..................................................................................................................................5

3. EXTERNAL INTERFACE REQUIREMENTS......................................................................................6

3.1 Hardware Interfaces...............................................................................................................................6
3.2 Software Interfaces.................................................................................................................................6
3.3 Communications Interfaces.....................................................................................................................6

4. FUNCTIONAL REQUIREMENTS......................................................................................................6
5. NON-FUNCTIONAL REQUIREMENTS...........................................................................................6
5.1 Performance Requirements.....................................................................................................................6
5.2 Safety Requirements...............................................................................................................................6
5.3 Security Requirements............................................................................................................................6
5.4 User Documentation...............................................................................................................................7

6. ASSUMPTIONS AND DEPENDENCIES...........................................................................................7

7. REFERENCES......................................................................................................................................7
8. Appendices...................................................................................................................................7

Page 4 of 18
<Project code> Software Requirements Specifications

Section 1

1.0 Introduction

1.1 Purpose of Document

The purpose of this document is to specify the Sofware Requirements
Specification (SRS) for Auto-Expert and road guide. It describes the scope of the system,
functional requirements, non-functional requirements, constraints and interfaces of the
system.

1.2 Project Overview

1.2.1 Significance of the Project

The problem of being stranded road side with no help and no knowledge of any
mechanical help in the area is what prompted the idea of an application that would
help you with all problems regarding travelling. Consider a scenario where your car
breaks down in an unknown area, what would you do? Our application would help you
get help from the various service stations around the city; it will let you set an
appointment with them which will then be catered by the service station.
if the service stations are unavailable the option of automated solution via
troubleshooting will be available for the user. A series of yes and no questions will help
the user identify his problem and come to a solution. The application will also have a
chat service with an expert (later module). Once this application is ready for use
anyone with a faulty car will never have to go through the hassle of being troubled into
finding help road side

1.2.2 Description of the Project

This project revolves around the problems we face regarding our automobiles and other
aspects of travelling. The main purpose of this application will be to help you in your time
of distress; consider a scenario where your car breaks down in an area unfamiliar to you,
this application will allow you to send out your location via GPS and a list of the service
stations in Karachi will be at your disposal along with the distance to each one of them. You
can also set an appointment with one of these service stations by filling up a small form,
once thats done your request will be forwarded to the service center in your vicinity . If no
service station is available at that hour you can use the in-built smart system of the
application to find a solution to your problem by answering a few questions about your
problem. Other features will include chat with an expert.

Page 5 of 18
<Project code> Software Requirements Specifications

1.3Scope

Get Mechanical help(set-appointment)

Once your car breaks down road side all you have to do is access internet on your
phone and ping your location using your gps. Now with the list of all the nearby
service stations available you can fill up some details which will include the nature of
your problem. The request will be sent to the service station who will then decide if
they can cater your problem and accept or reject your request accordingly.

Automated help(trouble-shooting)
Consider a scenario where its late and all service centers and local mechanics are
unavailable. Our smart system will allow the user to pick a certain category of issues
from a limited list. Which will be followed by a series of questions which will be
answered with a YES or NO a pre-defined smart system will then give you an
appropriate solution.
Search Nearby Friend (fyp-2)
While our smart system resolves your problem and finds you a suitable service center
it will also look for any friends (who also have the application) using information from
your contacts and if any friend is found nearby the application will notify him with
your location so he can help you if possible.

Search Nearby Service station

Looking for a nearby service station and knowing exactly how close or far away you are
from it is the primary task of our android application. This will be done with the current
location of the user using his GPS and the distance to every service station will be
calculated and displayed to the user in an order.

1.3.1Not In Scope
Development for other platforms (iOS)

Page 6 of 18
<Project code> Software Requirements Specifications

2.Overall System Description

The objective of this project is to create an android application which will be for the citizens
of the Karachi, Which will provide details about nearby service stations, setting an
appointment with one of them, chatting with an expert or using the automated
troubleshooting section of the application for solutions on the go. No such is there in the
market for the people of Karachi.

2.1 User characteristics

Stakeholders

Every citizen of Karachi who owns a car will be a stakeholder.

Service stations.

2.2 Operating environment

USER: Android with minimum requirement of 6.0 or higher.
SERVICE STATION: Any environment which allows java applications.

We will be using JAVA programming language for our project implementation.

Android Studio will be our primary tool.

Net Beans: For the service station desktop application

2.3 System constraints

Following are the constraints related to our project:

The user should have the smart phone supported by the Android platform to use this
application.
The GPS of the mobile should be turned on while using the application.

Page 7 of 18
<Project code> Software Requirements Specifications

GPS is necessary for updating of data and for using this application.
Anyone who has the basic knowledge of English language can easily understand the
provided instructions and can easily use it.
If the server crashes the user will not have any data, nor will he be able to send out a
request to the service station.

2.4 Assumptions & Dependencies

The user willing to use the system will have to have a smart phone having Android Operating
System and it will be assumed that the user has the basic knowledge of using the smart phones:

Operating system:
Mobile App: must have android
Internet availability.
Working GPS.

3. External Interface Requirements

This section is intended to specify any requirements that ensure that the new system will connect properly to
external components. Place a context diagram showing the external interfaces at a high level of abstraction.

3.1 Hardware Interfaces

The hardware requirements are simple:
USER: The user will need a smart phone
SERVICE STATION: A computer system with the basic hardware like mouse, keyboard printer .

3.2 Software Interfaces

Sofware used for development Android studio, net beans
Operating System Android 6.0 or higher and windows xp or
higher.
Database SQlite and mySQL
For development Windows 7 and higher

Page 8 of 18
<Project code> Software Requirements Specifications

3.3 Communications Interfaces

USER: Internet
GPS
Working Phone number

SERVICE STATION: Internet

Working phone number

4 Functional Requirements

Diagrammatic Representation of the Overall System

A detail diagram of the overall system is needed on a separate (preferably the last) page of
this proposal. However, the in-text figures should be provided in the format as given below.

Page 9 of 18
<Project code> Software Requirements Specifications

Use Case Name: Find Service Station

Actors: Customer
Interest and Customer: Find Nearby Service Stations
Stakeholders:
Pre-condition: Customer has created an account and logged in
Post Condition: System shows all nearby Service Stations
Success Scenario: 1. Login using username and password.
2. Press on button Find Service Station.
Alternative path: 1. No internet access
2. Invalid username/password.
3. GPS location not on.

Use Case Name: Set Appointment

Actors: Customer
Interest and Customer: Set Appointment for Car checkup
Stakeholders:
Pre-condition: Customer has created an account and logged in and inserted
information about car
Post Condition: Request has been submitted to service station
Success Scenario: 1. Login using username and password.
2. Press on button Find Service Station.
Alternative path: 1. No internet access
2. Invalid username/password.
3. GPS location not on.

Use Case Name: Quick Troubleshoot

Actors: Customer
Interest and Customer: Troubleshoot the problem by answering FAQs
Stakeholders:
Pre-condition: Customer has created an account and logged in
Post Condition: System shows all nearby Service Stations
Success Scenario: 1. Login using username and password.
2. Press on button Quick Troubleshoot.
3. Answer FAQs
Alternative path: 1. No internet access

Page 10 of 18
<Project code> Software Requirements Specifications

2. Invalid username/password.
3. GPS location not on.

Use Case Name: Respond to Appointment

Actors: Service Station
Interest and Service Station: Respond to Appointment, generated by
Stakeholders: customer
Pre-condition: Service Station should be logged in
Post Condition: System shows all the appointment requests
Success Scenario: 1. Login using username and password.
2. Press on button Accept Request.
Alternative path: 1. No internet access
2. Invalid username/password.
3. GPS location not on.
4. System could not refresh the lists

Page 11 of 18
<Project code> Software Requirements Specifications

Page 12 of 18
<Project code> Software Requirements Specifications

Page 13 of 18
<Project code> Software Requirements Specifications

Page 14 of 18
<Project code> Software Requirements Specifications

Page 15 of 18
<Project code> Software Requirements Specifications

5 Non-functional Requirements

5.1Performance Requirements
We will measure the performance of our system using the following criteria
Efficient: The response in time of distress for a user needs to be quick.
Reliable: The data needs to be correct and the user can trust it blindly
Up-to-date: The data needs to be up to date with all the valid service stations and
locations.
Consistent: The output to user queries needs to be consistent.

5.2 Safety Requirements

User should not use the application while driving.

5.3Security Requirements
Location of the user should not be disclosed to any other user/service station
unless the user wants it to. Because this can be a major security concern for
the user other sensitive data like phone number of user and registration
number of car needs to be kept hidden from others.

5.4User Documentation
Feedback within the application
Along with a tour of the application which will be like a walkthrough for a new user.

6 Assumptions and Dependencies

ASSUMPTIONS:
The user needs to have an android phone. He is also expected to know the basic knowledge of
how android phones work. The user is expected to have a working internet as well.
The user is expected to read and understand English language.

DEPENDENCIES:
The system is depended on the working of google maps if in the future it ever crashes our
application will face problems as well.
Secondly the modules which are part of fyp-2 will be added to the work done so far(fyp-1)
which includes chat with an expert etc,
Page 16 of 18
<Project code> Software Requirements Specifications

1 References

[1].The Technological Hybrid of Geo fencing Engineering

Link:http://www.iaeng.org/publication/IMECS2010/IMECS2010_pp1004-1008.pdf
[2]. Spatial Dimensions of Big Data
Link:http://link.springer.com/chapter/10.1007/978-3-319-05029-4_6
[3].Trade area analysis using user generated mobile location data
Link:http://dl.acm.org/citation.cfm?id=2488480
[4].Scalable Processing of Geo-tagged Data in the Cloud
Link:http://www.nec.com/en/global/techrep/journal/g12/n02/pdf/120220.pdf
[5]. social media crawling

Link:https://www.promptcloud.com/social-media-networking-sites-crawling-service/

[6]. Using Object Concepts to Match Artificial Intelligence Techniques to Problem Types

Link:https://ucalgary.ca/bnault/files/bnault/using-object-concepts-to-match-artificial-
intelligence-techniques-to-problem-types_manu_0.pdf

Page 17 of 18
<Project code> Software Requirements Specifications

Page 18 of 18