PRAKASH

TEAM LEADER: JAIDEEP KUMAR SINGH

TEAM MEMBER 1: MAYANK CHAUDHARY
TEAM MEMBER 2: MEGHA DWIVEDI
TABLE OF CONTENT
• Problem Statement
• Abstract
• Introduction
• System requirement specification (SRS) and Analysis
• Proposed System Design
• Technology Stack (Hardware/Software)
• Result and Conclusion
• References
PROBLEMS STATEMENT

• “ Inconvenience due to Non-Functional Street

Light in the rural areas of Central India ”
ABSTRACT
• Street lighting provides a number of important benefits. It can be used to promote security in urban areas
and to increase the quality of life by artificially extending the hours in which it is light so that activity can
take place.

• Street lighting also improves safety for drivers, riders, and pedestrians. Driving outside of daylight hours
is more dangerous – only a quarter of all travel by car drivers is between the hours of 7pm and 8am, yet
this period accounts for 40% of fatal and serious injuries to the same group.
• Pedestrians and vulnerable road users suffer from decreased visibility in the dark too. For this reason,
ways of reducing the risk to all road users during the hours of darkness must be found.
 INTRODUCTION

• Our idea is to create an application through which we can know the exact location of non-functional streetlight
and then file complaint for it.

• Initially we are going to connect the street light application “ PRAKASH ” to our database . When any user sees
a non-functional streetlight, he/she uses the app to extract his current location and then file a complaint for the
streetlight.

• The streetlight data is now received by the Prakash website an can be viewed by the government officials.

• Then the officer who is responsible, will assign a technician who will fix the street light and the user who filed
the complaint will be rewarded
SOFTWARE REQUIREMENT
SPECIFICATION
CONTENTS

1. INTRODUCTION 2.3 USER INTERFACE

1.1 PURPOSE 2.4 ADMIN INTERFACE

1.2 INTENDED AUDIENCE AND READING 2.5 OPERATING ENVIRONMENT

SUGGESTION 2.6 ASSUMPTION DEPENDENCIES
1.3 PROJECT SCOPE 3. SYSTEM FEATURES AND
2. OVERALL DESCRIPTION REQUIREMENTS

2.1 PRODUCT PERSPECTIVE 3.1 FUNCTIONAL REQUIREMENTS

2.2 PRODUCT FEATURES 3.2 EXTERNAL INTERFACE REQUIREMETNS

3.3 NON-FUNCTIONAL REQUIREMENTS

1.INTRODUCTION

1.1 PURPOSE
The purpose of this document is to build an feedback system to know the exact location of non-
functional streetlight in rural areas. This will help the electricians who find it difficult to locate the non-
functional streetlights. And as these non-functional streetlights are fixed, there will be enough light on
the road and hence accidents can be prevented.

1.2 INTENDED AUDIENCE AND READING SUGGESTIONS

This project is a prototype for the feedback system for non-functional streetlights and it is restricted
within the college premises. This has been implemented under the guidance of college professors. This
project is useful for the government agencies responsible for streetlights management.
1.3 PROJECT SCOPE

The purpose of this feedback system is to ease streetlight management and to create a convenient
and easy-to-use application for common people, trying to report a non-functional streetlight. The
system is based on a firebase database and its has location extracting functions and complaint
form support. Above all, we hope to provide a comfortable user experience to our users.
2. OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVE
Our feedback system database contains the following information.

1.Customer details
It includes customer Id, name, address and phone number. This information may be used for keeping
the records of the customer for any emergency or for any other kind of information.

2.Complaint details
It includes complaint form details like the customer who has launched the complaint, the HSN code of
the pole, image of streetlight, landmarks etc.
2.2 PRODUCT FEATURES
(ER DIAGRAM)
2.2 PRODUCT FEATURES (ER DIAGRAM)
2.3 USER INTERFACE

Users will be able to give their current location anytime they want. This will help them to see whether they are
giving the exact location of streetlight or not.
Users will be able to launch a complaint if they see any non-functional streetlight. The complaint form is
provided in the app itself. Complaint form consists of name of user, phone number, user has to provide HSN code
of streetlight(optional) and landmark near the streetlight.
The user of the app also has to provide an image of the streetlight. This image should be clear and should be
taken in daylight.
In order to maintain accuracy of streetlight images we have installed a ML model using object detection which
would only allow user to upload an image if it contains a streetlight
Otherwise the image will be rejected.
2.4 ADMIN INTERFACE
•The website consists of login page. So, the officer is going to need an certain id and password to login . After
login , the data would be fetch through java script API and a page will appear in which all the location of non-
functional street light will appear on google maps.

•When officer will click the location of non-functional streetlight then a form will appear in which the details of
the in charge of that area will appears and the details and exact location will be shared via e-mail .

•Then In charge can send the location of non-functional street light to the electrician through mail or SMS.

•When electrician will click the link shortest path from the electricians and street light will appear on the screen.
2.5 OPERATING ENVIRONMENT

• Operating system – Android (for app)

• Database – Firebase real time database, Firebase cloud storage

2.6 ASSUMPTION DEPEDENCIES

It is assumed that Google Maps API which is used in the app to provide the current location of the user,
provides true location of the user. It may have a precision error of 3-5m only.

We also assume that the user provides valid information regarding the streetlight hence it would be easier for
the electrician to search for it.
3. SYSTEM FEATURES AND REQUIREMENTS

3.1 FUNCTIONAL REQUIREMENTS

1. The user needs to login into the app. If user does not have an account then he has to register
onto the app.
2. After logging into the app the user sees a navigation slide by which he can navigate through
different parts of the app.
3. If user wants to launch a complaint then he can simply click on the ‘Register Complaint’ tab
and after providing location access he can move onto the ‘Complaint Tab’ to fill the form.
4. The user can also see how many rewards he has gained by reporting non-functional
streetlights, this can be done by going into ‘Rewards’ tab.
3.2 EXTERNAL INTERFACE REQUIREMENTS

• Software used – React.js , Node.js

• Database used – Firebase real time database, Firebase cloud storage
• Operating system – Windows
• Communication interfaces – This project supports all types of web browsers.
3.3 NON-FUNCTIONAL REQUIREMENTS
• Safety requirements: -
• The safety of data is completely managed by firebase which stores its data on cloud. Hence
data is completely safe.
• Security requirements:-
• Security of database is managed by firebase hence it is completely secure. No one can access it
without a key (id). Whereas app is also completely secure as it only communicates with
firebase and no any third party site or application.
USE CASE DIAGRAM
PROPOSED SYSTEM DESIGN
TECHNOLOGY STACK
• Android Studio • Python
• Kotlin • React.js
• Android Jet pack
• Firebase Realtime Database
• Firebase Authentication
• Firebase Cloud storage
• TensorFlow Lite
RESULT AND CONCLUSION

• The app and website is currently in development

REFERENCES
• Google