Software Requirements

Specification
For
AICTE- GRIVANCE PORTAL

Prepared by
Akash Khandelwal- 15EJCCS703
Ashish Sharma-15EJCCS705
Himang Singh Solanki- 15EJCCS717
Megha Sharma- 15EJCCS7
Purvi Mutha- 15EJCCS7
Yash Agarwal- 15EJCCS760

Department of Computer Science and Engineering

Jaipur Engineering College and Research Centre
<23-01-2019>

i
 Table of Contents

1. Introduction 3
1.1 Purpose 3
1.2 Intended Audience and Reading Suggestions 3
1.3 Product Scope 3
1.4 References 3
2. Overall Description 4
2.1 Product functions 4
2.2 User Classes and Characteristics 4
2.3 Operating Environment 4
2.4 Design and Implementation Constraints 4
2.5 User Documentation 4
3. External Interface Requirements 5
3.1 User Interfaces 5
3.2 Hardware Interfaces 5
3.3 Software Interfaces 5
4. System Features 6
4.1 Data analysis 6
4.2 Easy To Use 6
4.3 Secure Login 6
4.4 Privacy 6
5. Other Nonfunctional Requirements 7
6. Business Rules 7
7. Other Requirements 7

2
1. Introduction

1.1 Purpose
The purpose of this project is to help reduce the number of road accidents, by making the user
aware of the risks in a blind spot, so they drive keeping it in mind. Hence, Road Side is an
android web based application that can facilitate easy access for drivers to blind spot, or
accident prone areas on their route.

1.2 Intended Audience and Reading Suggestions

The intended audience of this project are the drivers who will be benefited with a warning
when they are driving through an accident-prone area. The consuming user would be able to
create an account, navigate through the application, get notified, mark an area (hence,
ultimately building the database). While a backend developer would help to maintain the
application, provide updates, apply modifications in the database like insertion or deletion.

1.3 Product Scope

The project is an android application with primary focus on the road accidents. The project is
developed with the intentions of reducing the accidents on road, that occurs because of rash
driving and absolute unawareness of the driver. We expect drivers to drive with caution when
notified, ultimately resulting in reduced number of clashes.

1.4 References
www.google.co.in
www.stackoverflow.com
www.wikipedia.org
developer.android.com
www.androidshare.com
www.androiddroid.com

3
2. Overall Description

2.1 Product functions

 Alert while in an accident-prone area
 user profile management
 analysis of user feedback
 calculating risks with feedback

2.2 User Classes and Characteristics

All users with basic understanding of operating a cell phone can use this app. Primarily, the
main concern of this project lies with the safety of user. No specific and
technical expertise needed to use this app.

2.3 Operating Environment

The operating environment of the emergency management system is as follows:
● Distributed database
● Client/Server system
● Operating system: Android
● Database: Firebase + SQLite
● Platform: android studio, java

2.4 Design and Implementation Constraints

 firebase database for managing user profile
 cloud messaging service for push notifications
 user preference based search

2.5 User Documentation

A step by step guidelines for using all services in app and basic landing tutorial will be
provided so that any user with minimal understanding can use this app.

4
3. External Interface Requirements

3.1 User Interfaces

Here the user will be able to interact with the android application. The user will open the app
and then he/she will register on it with their mobile number. A one-time-password will be
sent to the number and then it will be verified and the user will be registered on the
application. After this the user, will be asked some of the basic details like name, date of
birthetc. and after completing the profile they can be alerted, and can also add to the database.

3.2 Hardware Interfaces

The hardware interface requirement is used for the interaction between the user and the
android application where the application makes the use of the camera for video, image etc.
and microphone also for audio.

3.3 Software Interfaces

In case of software interfaces the android application interacts with the database (which can
be oracle, sql etc) for storing the media like audio, image, video etc. and also makes the use
of the languages php, java, kotlin etc. for the interaction of the various software.

5
4. System Features
Here as the name of the application is “Road Side”, there are some of the features of this
application:

4.1 Data analysis

Each user can contribute in building a database of areas, but for obvious reasons not each and
every area can be declared a blind spot. Only those areas would be declared as blind spots for
which the number crosses a threshold.

4.2 Easy To Use

This application is very easy to use. The application would be made with keeping in mind
that the user would be able to navigate through and provide contribution to the application
with minimum number of clicks.

4.3 Secure Login

The consumers are expected to create an account for the application. Therefore, a secure way
of login is a necessary feature. Hence, the customer would be sent a one-time-password while
they sign-up, and each further attempt to login would be authenticated with a password set by
the user itself while sign-up.

4.4 Privacy
We as developers understand the importance of privacy of consumer. Hence, all the personal
information of the consumer including contact numbers, passwords etc. would be hidden at
all costs.

6
5. Other Nonfunctional Requirements
 Performance:Well-structured database with minimal redundancy
 Safety:Backup of all the database helps in case of any catastrophic damage to the
servers and quick response to emergency service
 Security:Well managed virtual private servers and database prevents leaks of any
kind of vital information of the users.
 Reliability: the system is expected to notify the consumer each and every time they
pass a blind spot, without any failure.
 Maintainability: the database and application would be easy to maintain and update.

6. Business Rules
 The application will be provided to the user free of cost.
 The consumer would be able to contribute to build the data base.
 The consumer would not be able to access or insert changes in the database via
queries.
 The right to access database, insert changes or modify the application in any way
would only reside with the developers.

7. Other Requirements
● Sustainable servers capable of handling bulk requests
● Virtual private servers for securely handling of user information