A PROJECT ON

“Remote SOS Application”

DEVLOPED BY:- GUIDED BY:-

RUTUJA N. MHASKE MS. R. B. GURAV

“ALL INDIA SHRI SHIVAJI MEMORIAL SOCIETY, SECOND SHIFT

POLYTECHNIC”,PUNE-01
Contents:
 Introduction ..03
 Requirements ..05
 Working ..07
 Working Diagram ..08
 Flowchart ..09
 System Diagram ..10
 Class Diagram ..11
 Use case
 Technical Aspect ..13
 Snapshots ..14
 Conclusion ..16
 Future Scope..17
Introduction
 The basic problem in the food service industry is that restaurants are not
realizing efficiencies that would result from better applications of technology
in their daily operations. Every fast food has counter where you can place
your order and then make the payment. So every fast food needs an employee
for taking the order and processing the payment. Labor rates are increasing
every now and then and it is difficult to find employees in the middle of the
highway, hence to solve this problem we plan to design a "Self Served Fast
Food System."
 This self-service fast food restaurant will be equipped with a user-friendly
touch screen, a credit/debit card reader, and software for completing the
process at the backend. For this system there will be a system administrator
who will have the rights to enter the menu with their current prevailing prices.
He/she can enter anytime in the system by a secured system password to
change the menu contents by adding or deleting an item or changing its price
Introduction (Cont..)
 Now when the customer enters the restaurant, he will place his order with the
help of the touch screen using the intuitive graphical user interface, right from the
selection of language till the payment confirmation.
 He will select from the food options according to his choice and the system will
display the payment amount he has to make once he has finished with his order.
 He will have the option of paying the bill by cash, debit card or a credit card.
 The user will slide his card and the system will check for the validity of the card
and the payment will be made. A receipt will be printed containing the order
number and the order will be sent in the kitchen for processing.
Requirements (For PC Module)
 Software Requirement's-

 Front end : Java and Android SDK tools

 Back end : MySQL
 Web Server : Apache Tomcat
 IDE : Eclipse
 Operating system : Windows XP/Vista/7
 Documentation : MS-office
  
 Hardware Requirements-
 Processor : Intel Pentium IV or above
 RAM : 1 GB
 HDD : 40 GB HD
 Network : Wi-Fi Network Interface Card
Requirements (For Android Module)

 Software Requirement's-
 Operating System : Android 2.0(Ginger Bread) to 4.4(Kit Kat)

 Hardware Requirements-
 RAM : 256 Mb at least
 Space on SD card : 20 Mb Memory or above
 Network : Wi-Fi Interface
Working
 We need to set up a wireless internet network.
 Install the Remote SOS application on the client smart phone.
 Install the server application on the users PC.
 After installing activate the server application installed on the PC.
 Now the server application will wait till an Android devices connects to it.
 Now user can enter his details like name gender dob and emailed and send it to the server for
account registration.
 The server then sends a verification code to the email id that user entered.
 The user should enter this verification code on the client device to verify the account.
 Now the device is ready to send SOS request to the server. At any time of emergency user just
needs to open this application and press the button for 5 seconds, an SOS request will be send
to the Server
 As soon as this request is received by the server an alert is displayed on the server and the
precise location is displayed on the map from where the sos request was send.
 Now a rescue mission can be deployed to that corresponding location.
Working Diagram
Wide Area Network

PC
(Server)

Mobile Device (Client)

DataBase

SOS
Alert Module
Server Application
Processing the
client request
Flow Chart

Start

Initialize the application and start the server

Client
Connected

Type of Request

Account Account SOS

Registration Confirmation Request

Verification SOS
Of Account Request
Client
Dis No
Conne
cted
yes
Stop
System Diagram.
INPUT
The user send a request to register his
account to the server with his email-id
The user send the request to verify his
registered account with the verification
code which was send thorough the
email-id
The user send a request to re-register
his account with the same email-id
The user sends an SOS request with the
current location details to the server
PROCESS
Checks if the email-id is already
registered or not and if not sends a
verification mail with a verification
code to that email-id
Checks whether the code is valid or
not.
Checks if the email-id is already
registered or not and if exists sends a
verification mail with a verification
code to that email-id
The server process this location data
and traces it on the map
OUTPUT
Result is displayed to the user and asks
the user for the verification code if
success on client side.
If the code is valid the account is
successfully registered and message is
displayed to the user
on client side.
Result is displayed to the user and asks
the user for the verification code if
success on client side.
A pop up message is displayed at the
server side with the name and location
details of the requesting user
 Class Diagram (Server/PC Module)
ServerManager ClientManager MapPanel GUI
ServerActive:boolean Rec-File(String,int) Latitude:String Name:String
setSOSAlert(String) RegUser(String,String,String, Longitude:String Age:String
String)
setServerStatus(Boolean) Initial:Boolean Gender:String
AccConfirm(String,String)
RefreshTable() setErrorMsg(Boolean) Lati:String
AlreadyReg(String)
getSOSLog() setLoadingMsg(Boolean) Long:String
ReconAcc(String,String)
SOSReg(String,String,String, setMap(String,String) Address:String
String) setPersonalDetails()
SOSServer sendVerificationEmail(String, setUserImage(String)
PORT:int String,String)
Alert setLocationDetails()
startServer() sendEmail(String,String,Strin
g) Name:String RequestMap()
stopServer() animate()
Class Diagram (Client/Android Module)
WelcomeScreen Registration GPSTracker ConnectionManager
PORT:int EmailID:String isGPSEnabled:Boolean Connectiontest:int
DateOfBirth:String sendRegRequest(String,S
IPADDRESS:String isNetwrokEnabled:Boolan
Month:String[] tring,String,String)
DisConnect() canGetLocation:Boolean
Gender:String sendConfirmAccReg(Stri
Notify(String,String) Lati:double ng,String)
setCurrentDate()
ConfirmExit(String) RegSuccess() Long:double sendReconfirmReg(Strin
getLocation() g,String)
RegFailed()
sendSOSReg(String,Strin
Error() getLocationAddress()
g,String,String)
Picture Notify(String,String) showSettingAlert() Send_file(String)
SelectPhoto:int stopUsingGPS()
Notify(String,String) AlreadyRegistered Confirmation
ConfirmExit(String) EmailID:String Code:String
RegSuccess() ConSuccess()
RegFailed() ConFailed()
Error() Error()
Notify(String,String) Notify(String,String)
Technical Aspect

 Here we have implemented a simple server - client architecture where the users
android device with the PC controller application installed acts as a client and the
PC with this application installed acts as a server.
 The Client and Server communicate using a simple message passing technique.
 When ever an error occurs in the network the client is automatically disconnected
from the server.
ScreenShots
ScreenShots
ScreenShots
ScreenShots
ScreenShots
ScreenShots
ScreenShots
ScreenShots
ScreenShots
Future Scope

 Although the application is efficient it still needs internet to work. In future

versions this can be implemented as an offline feature which will broadcast
his/her locations as well as to the server if internet is available.
 This application can further be improved for its performance and supporting more
type of devices.
Conclusion

 We developed this application hoping that this application can be used for saving
as many life as possible and also to understand the true potential of android
platforms which can be used for much greater purposes.
Thank You 