Book
Book
PROJECT REPORT
ON
“TITLE OF PROJECT”: Road Rescue-vehicle breakdown
assistance
By
Name of Student
Nikita Avchar
(Enrollment No.:2207110678)
Name of Student
Nikita Panchal
(Enrollment No.:2207110678)
Guided by:
(Name of guide)
CERTIFICATE
(External Examiner)
ACKNOWLEDGEMENT
This has been the light of the day due to invaluable contribution of certain individuals
whose constant guidance, support and encouragement resulted in the realization of our project.
We are grateful to our Guide Guide Name, Project Coordinator Mrs. S.A.Kaulage,
Vice principal and Head of Computer Department, Mr. M. S. Kalbande for providing us the
necessary help and encouragement whenever we needed, which has resulted in the success of our
project.
We would also like to thank all the staff members of our department without whose
constructive suggestions and valuable advice, the simple idea, which had born by us, would not have
Last but not the least we are grateful to all our friends, and our parents for their direct or
indirect constant moral support throughout the course of this project. Thanking You,
(Name/s of Student)
(ENROLLMENT NO: )
PO-PSO Mapping
1 INTRODUCTION 1
2 LITERATURE SURVEY
3 SCOPE OF PROJECT
4 REQUIREMENT ANALYSIS (HARDWARE
AND SOFTWARE REQUIREMENT)
Users:
Drivers and Vehicle Owners:
- Primary users who request roadside assistance services through the
mobile application.
- Provide details about the breakdown and communicate with the
service provider.
Roadside Assistance Service Providers:
- Skilled technicians and towing services responsible for providing on-
site assistance to stranded vehicles.
- Access breakdown details, navigate to the location, and perform on-site
repairs or towing as necessary.
Stakeholders:
Users and Vehicle Owners:
- Stakeholders who directly benefit from the efficient and reliable
roadside assistance services.
- Rely on the service for quick resolution of vehicle breakdowns, ensuring
their safety and convenience.
Roadside Assistance Service Companies:
- Stakeholders who provide assistance services, benefiting from
increased business opportunities and positive user feedback.
- Utilize the platform to expand their customer base and improve
service efficiency.
1
2. User Mobile Application:
- Interface for users to request assistance, provide details about the
breakdown, and track the arrival of the assistance team.
- GPS integration for real-time location tracking and mapping.
- Feedback and rating system for service evaluation.
Service Provider Dashboard:
- Dispatching and route optimization tools for service providers.
- Access to user information and breakdown details.
- Communication tools to update users on arrival times and progress.
Users:
Drivers and Vehicle Owners:
- Primary users who request roadside assistance services through the
mobile application.
- Provide details about the breakdown and communicate with the
service provider.
Roadside Assistance Service Providers:
- Skilled technicians and towing services responsible for providing on-
site assistance to stranded vehicles.
- Access breakdown details, navigate to the location, and perform on-site
repairs or towing as ne
2
SCOPE OF PROJECT
Integration of AI and IoT:
- Predictive Maintenance: AI algorithms can predict vehicle breakdowns by analyzing data from sensors,
providing proactive assistance before an actual breakdown occurs.
- Smart Roadside Assistance: IoT devices can communicate real-time data to service providers, enabling
quicker response times and more accurate issue diagnosis.
1) Hardware Requirement: -
Processor: 2.5 gigahertz (GHz) frequency or above.
Input Device: High resolution camera Monitor: Minimum Resolution 1024 X 768.
3.1.1 : Plan
This is the first step of the agile methodology. It where the vision of the project is created and involves gathering
relevant data, mapping processes and coming up with the scope. The data in this phase is analyzed to ensure
they are realistic and achievable. In the proposed system, the data being collected and analyzed is the number of
people who are faced with emergencies that require rescue services, the issues that can be solved within the time
period given and also the features that can be built in the application.
3.1.2:Design
This phase uses the data gotten from the planning phase to come
up with the design of the system to optimize it with the right
technology. The tools and technologies to be used are also listed
here. According to the data gotten, the system being mobile
based and having features like the access to GPS and location
services makes it suitable to solve the problem.
3.1.2: Develop
This phase involves the actual creation and coding of the system
based on the designs gotten from the design phase. The system
will be created with java programming language which is
suitable for mobile applications.
3.1.2: Test
This is the phase where the developed system is put into testing
to find out if there are any bugs or vulnerabilities in it. Some
testing techniques are:Black box testing - The testers here will
not have access to the code or have any knowledge of the system
but will interact with the user interface.Security testing - It
involves testing whether one can access the data in the system
using wrong credentials or without logging in.Compatibility
testing - The system is put to run in different environments or
operating systems like android or IOS (iPhone operating
system).
3.1.2: Deploy
This is the phase that involves installation, configuration, testing
and making changes to optimize the performance of the
software. This is usually done to a smaller population before
being officially launched to the public.
3.1.2: Review
This is the phase where the data gotten from the deployment is
carefully examined to validating the quality, functionality and
other vital features and components of the software. With this
data, the team can know whether to make further improvements
to the system or launch it.
3.1.2: Launch
This is the final phase of the methodology where the system is
officially opened to all the population. This is usually done
after closely examining the reviews gotten earlier.
DETAILS OF DESIGN WORKING AND PROCESS
7.1.1 Labellmg
import android.content.DialogInterface
import android.content.Intent
import android.content.SharedPreferences
import androidx.appcompat.app.AppCompatActivity
import android.os.Bundle
import android.text.TextUtils
import android.widget.EditText
import androidx.appcompat.app.AlertDialog
import com.google.android.gms.tasks.OnCompleteListener
import com.google.android.material.dialog.MaterialAlertDialogBuilder
import com.google.firebase.auth.FirebaseAuth
import com.google.firebase.database.FirebaseDatabase
import com.google.firebase.messaging.FirebaseMessaging
import com.google.firebase.storage.FirebaseStorage
import com.guruprasad.roadresuceadmin.Activities.HomeActivity
import com.guruprasad.roadresuceadmin.Constants.Constants
import com.guruprasad.roadresuceadmin.Constants.CustomDialog
import com.guruprasad.roadresuceadmin.R
import com.guruprasad.roadresuceadmin.databinding.ActivityLoginBinding
auth = FirebaseAuth.getInstance()
storage = FirebaseStorage.getInstance()
database = FirebaseDatabase.getInstance()
loadData()
binding.etEmail.setText(mail)
binding.etPassword.setText(pass)
binding.btnLogin.setOnClickListener {
val email : String = binding.etEmail.text.toString();
val password :String = binding.etPassword.text.toString();
savedata(email,password)
dialog.show()
auth.signInWithEmailAndPassword(email,password).addOnCompleteListener{task->
if (task.isSuccessful)
{
val user = auth.currentUser
if (user!=null && user.isEmailVerified)
{
FirebaseMessaging.getInstance().token.addOnCompleteListener(
OnCompleteListener { task ->
if (!task.isSuccessful) {
return@OnCompleteListener
}
database.reference.child("Admin").child(auth.currentUser!!.uid).updateChild
ren(map)
.addOnCompleteListener{task->
if (task.isSuccessful)
{
Constants.success(this@LoginActivity,"Login Successful")
startActivity(Intent(this@LoginActivity, HomeActivity::class.java))
finish()
dialog.dismiss()
}
else {
Constants.error(
this@LoginActivity,
"Failed to update token try again : " + task.exception!!.message
)
dialog.dismiss()
}
}
}else{
Constants.error(this@LoginActivity,"Failed to login :
"+task.exception!!.message)
dialog.dismiss()
}
})
}
else
{
Constants.error(this@LoginActivity,"Please verify the email and Login")
dialog.dismiss()
}
}
else
{
Constants.error(this@LoginActivity,"Failed to sign in the user")
dialog.dismiss()
}
}
}
binding.btnSignup.setOnClickListener {
startActivity(Intent(this@LoginActivity,RegisterActivity::class.java))
finish()
}
binding.tvForgotPassword.setOnClickListener {
if (email.isEmpty())
{
Constants.error(this@LoginActivity,"Please enter your register email")
loading.dismiss()
return
}
else
{
resetpassword(email , loading)
}
}
dialog.setPositiveButton("YES",yes)
dialog.setNeutralButton("CANCEL",cancel)
}
}
auth.sendPasswordResetEmail(email).addOnCompleteListener{task->
if (task.isSuccessful)
{
Constants.success(this@LoginActivity,"Email has sent to your registered email
address")
loading.dismiss()
}
else
{
Constants.error(this@LoginActivity,"Failed to send email :
"+task.exception!!.message);
loading.dismiss()
}
}
10.1 Result:
appears there might be a typo in your request. If you meant "road rescue app result," it
could refer to the outcome or performance of a road rescue application.Here's a
hypothetical explanation:A road rescue app typically serves as a platform for users to
request assistance in various roadside emergencies such as vehicle breakdowns, accidents,
or flat tires. The "result" of such an app would depend on its effectiveness in providing
timely and appropriate assistance to users in distress.Some key aspects of a successful road
Some key aspects of a successful road rescue app result might include:
1.Efficiency: The app quickly connects users with nearby roadside assistance providers or
emergency services.
3.User Experience: The app provides an intuitive interface for users to request help easily,
possibly including additional features like tracking the arrival time of assistance.
4.Reliability: It ensures that the assistance dispatched is reliable and capable of addressing
the specific emergency situation effectively.
5. Feedback and Reviews: Users' feedback and reviews play a crucial role in determining
the app's result, as positive experiences lead to increased trust and usage, while negative
experiences could indicate areas for improvement.
Overall, the "result" of a road rescue app would be measured by its ability to efficiently
and effectively assist users in their time of need, thereby enhancing safety and peace of
mind for travelers.
10.2 Application:
3. Insurance Companies:
- Value-Added Service: Providing breakdown assistance as a value-added service
to insurance policyholders, enhancing customer satisfaction and loyalty.
- Claims Processing: Quick roadside assistance can prevent accidents, reducing
the number of claims and associated processing costs.
4. Auto Manufacturers:
- Customer Support: Offering complimentary or subscription-based roadside
assistance services as part of the vehicle purchase, enhancing the brand's customer
support.
Remote Diagnostics: Using connected car technology to diagnose issues remotely and
offer assistance or schedule maintenance appointments.
FUTURE WORK
1.Integration of AI and IoT:
- Predictive Maintenance: AI algorithms can predict vehicle breakdowns by
analyzing data from sensors, providing proactive assistance before an actual breakdown
occurs.
- Smart Roadside Assistance: IoT devices can communicate real-time data to
service providers, enabling quicker response times and more accurate issue diagnosis.