SWE2004 - M.Tech: Vehicle Tracking System Architecture and Design

This project report details the design and architecture of a vehicle tracking system. It begins with a comprehensive problem statement, outlining the system's functionality, including customer registration, order acceptance, location tracking, and detail sharing. The report then describes the overall architecture, which includes customer, administrative, and driver modules. Further, it develops a state chart diagram for each module, illustrating the system's states and transitions. The project also includes structure diagrams using JSD (Jackson System Development), detailing entity relationships. Finally, the report performs a transaction analysis using SSA/SD (Structured Systems Analysis/Structured Design) up to level 3, including data flow diagrams and structured charts for each module, effectively mapping the system's processes and data flow.

School of Information Technology and Engineering
(J- Component) -Fall 2018-19
REVIEW -1
PROGRAM: M.Tech
BRANCH: Software Engineering
COURSE CODE: SWE2004
COURSE TITLE: SOFTWARE ARCHITECHTURE AND DESIGN
Team members:
17MIS0191 – POOVILA.DK
17MIS0300 - PREETHI.L
17MIS0099- SANDHYA.K
TOPIC GIVEN: VEHICLE TRACKING SYSTEM
Submitted to:-
Dr. S. sreedharanya
SLOT: D1

1. Give the detailed description about the problem statement and specify the
overall architecture with the modules?
OVERALL PROBLEM STATEMENT:
The software has to design for hiring the vehicles. This project describes about vehicle
tracking system. The customer will send the location to the app/web administrator.
From here only our process will get started .the administrator will confirm the
customer’s current and destined location. Then he should find the respective drivers
who are all present around the customer current location. The administrator will send
the order details to the nearest driver by knowing who are not in any order. After that
the administrator will send the driver details to the customer and the customers
confidential person. While travelling the administrator should get the details from the
satellites about the vehicles (GPRS tracking).each and every detail like place, speed
and the surrounding details should be updated and stored by the administrator. At
there we are including the additional option like the confidential person should also
able to track and update the travelling details. Then after reaching the message should
be sent by driver to the administrator and also by the administrator to driver by
showing task completion. Then the tracking will be disconnected.
1. REGISTRATION
2. ORDER ACCEPTION
3. LOCATION TRACKING
4. DETAILS SHARING
REGISTRATION:
Registration is process of logging into the entire process it suits to both driver and the
user. It is the first step for all. From this the admin can get the details of the customer.
ORDER ACCEPTION:
After getting the information from the user, the admin used to send the order for the
order. If the order is being accepted by the user then the admin will send the present
location details of the customer to the driver. In the exceptional case, if the driver
refuses to get the order then the admin will search for another drivers.
LOCATION SHARING:
In the location sharing process, the present location and the destination location is
being shared with the admin by the customer. This is important process of all because
the main process of our project (vehicle tracking system) is being demonstrated at
here. At here admin is not tracking the customer. Admin is not tracking the customer;
he/she is tracking the car tracking the car (car’s VIN number) which is being travelled

by the customer for the customer protection and also to check the drivers working
performance
DETAILS SHARING:
After gathering the tracking information from GPS, the admin will get the information
about the vehicle which is updated and stored in the database. Rather than, while in
the login phase the customer used to give information (example ,mail ID, phone
number) about the confidential person. Then the details can be send to the confidential
person where they can also be able to locate the customer.
ARCHITECHTURE DIAGRAM:
Customer Register
Login
Digital view
Share location Admin
Search for drivers
nearby
View current
location
Share details
to the
confidential
person
Driver
Task
accomplished
Send
order
Order
accepted
Order
rejected
Send present
location details
Send driver
details
Track the
driver location
Satellites

2. Develop the state chart diagram
MODULES:
We are separating this into three modules:
 Customer module
 Administrative module
 Driver module
STATE CHART DAIGRAM FOR THREE MODULES:
CUSTOMER MODULES
ADMIN:
REGISTER LOGIN FILL DETAILS &
CONFIDENTAL
PERSON DETAIL
SHARE
LOCATION
N
GET
DRIVER
DETAILS
SERVICE
DETAILS
Get the customer
details
Search for
drivers
Send orders to
drivers
Share
location to
drivers
Send driver
details to
customers
Find the car
VIN
Track the car
via satellite
Update the
location
Store the
location
Share the location with
the confidential person

DRIVER MODULE:
3. Develop the structure diagram JSD
JACKSON SYSTEM DEVELOPMENT (JSD)
JSD contains
• Modeling
• Networking
• Implementation
It is already known that :-
JSD=ESD+SSD
ESD- Entity structure diagram
SSD – system specification diagram
REGISTER
CAR& DRIVER LOGIN
GET ORDER
FROM
ADMIN
CHOICE OF
ACCEPTAN
CE
ACCEPT
REJECT
GET
LOCATION
INFO
TASK
COMPLETION
DETAILS
NOT
COMPLETEDD
COMPLETED
YET TO
COMPLETE
SEND MESSAGE
TO ADMIN

ENTITY RELATIONAL DIAGRAM:
CUSTOMER MODULE:
Login
REGISTER
DRIVER
DETAILS
Name
Phone
number
Address
Mail id Password
Username Customer id
Confidential
number Customer
number
Destina
tion
Current
location
Driver id
Driver
number Driver
name
Vehicle
number
Book
FILL
DETAILS

ADMIN MODULE:
GET
DETAILS
LOCATION
SEARCH
DRIVER
Customer
number
Customer
id
Destination
Confidential
number
Current
location
Vehicle
number
VIN Area
Driver id
Present
location
Order
acception

DRIVER MODULE:
Login
REGISTER VEHICLE
ORDER
Driver id
Driver
number
Driver
name Password
License
number
Vehicle
number VIN
Insura-
nce
Customer
number
Current
location
Customer
id
Destination

4. Perform the transaction analysis using SSA/SD up to level 3.
TRANSACTION ANALYSIS USING SSA/SD UP TO LEVEL 3
Step 1: Initial level DFD
LEVEL 0 OR CONTEXT LEVEL DAIGRAM:

Step 2: Elaborate into layerd hierarchyof DFD
LEVEL 1:

Step 3: use transaction analysis to divide the DFD into tactable unit
LEVEL 2:

Step 4: Perform a transform analysis on the DFD created for each transaction in
order to modify the structure chart for transaction &
Step 5: Merge the structure chart
STRUCTRED CHART- JSP
CUSTOMER MODULE
INPUT STREAM:
OUTPUT STREAM:
CUSTOMER
LOGIN *
SHARE
LOCATION
FILL DETAILS
AND
CONFIDENTIAL
PERSON DETAIL
CUSTOMER
LOGIN *
SHARE
LOCATION
DRIVER
DETAILS
SERVICE
DETAILS