Phase3

1. Software Architecture Block Diagram:
Sign in /
Sign up
Module
Trips
Module
Business
Logic
Push
Notifications
About
Module
GPS
Module
Help
Module
Settings
Module
Each module in this block diagram is detailed below with the interactions between components within
each module separately.
Sign in/Sign up Module:
The application user using the smart phone has two options.
1.) Sign In : The user logs into the SmartDriver application with his credentials which gets validated in
the background with the Mobile Database. If the user entered the proper credentials the user gets the
access to use the application otherwise he is restricted from accessing the application.
He is also shown a hyperlink which asks him to sign up to the application if he is a first time user.
2.) Sign Up: The user is treated as a new user and therefore he needs to provide genuine details such as
personal information, official information and answer security questions. These are the checks which
prevent miscreants or software attacks that stall the application’s performance.
Request Authenticatio
n request
Mobile DB response
Sign in /
Sign up

2. GPS Module:
This Module deals with fetching location data and speeds of the vehicle using GPS API from GPS.
Requests location
data and speeds Fetches from
GPS API GPS
GPS
Settings Module:
Whenever the user changes his settings, modified settings are updated in the mobile database and
corresponding changes are reflected on the device.
Settings Mobile DB Request
Push Notifications Module:
Business Logic determines when to trigger notifications. It is based on hard breaking and rapid
accelerations. Whenever the required conditions are met, push notifications are triggered and delivered to
the device by APNS server(in Apple) or corresponding push notifications services in other devices.
Push Noti-fications
Business
Logic
Delivers
notifications
Triggers
notifications
modifications
Update
settings
Updated
Response settings

3. Trips Module:
Trips are periodically updated into the mobile database and are shown when user taps trips from menu
item.
Mobile DB
Request trips
Response
Sample User Screens:
Trips Screen - When user taps on a trip, it is taken to next screen where the trip is shown on a map. Hard
breaks and rapid acceleration points are marked on the map.

4. Menu Screen:

5. Managing Changes:
Change
Request
Details
(to
be
filled
by
the
customer)
Change Request Number
Project Name
Location of the existing
problem
User Interface ( Front end )
Database ( Back end )
Report generation ( Email )
Related to GPS Tracker
Others
Priority Low Medium High Mandatory
Module Affected
Brief Description of
Change Request
Reason for Priority
Request Submitter’s Name Email
Phone Date
Project
Impact
(to
be
submi>ed
by
the
project
team)
Investigator’s Name Email
Release Patch Version
Estimated Schedule
Change
Estimated Budget Change
Assumptions and Notes
Comments for
implementing the change
Attachments / References Link:
Project Manager Email

6. Approval Signature Signoff Date