Project Report

A PROJECT REPORT ON

MULTI-TRACKING SYSTEM submitted in partial fulfilment of the requirements for the award of the degree of

Bachelor of Engineering in INFORMATION TECHNOLOGY by

SAMEE SAMEER R DAREKAR AREKAR

B84385 B8438514 14

ATUL TUL CHI HIK KANE ANE

B843 B84385 8506 06

AMOL AMOL DESH DESHAMU AMUKH KH B84385 B8438516 16 RUTUJ RUTUJIT IT DIWA DIWATE

B84385 B8438518 18

Under the guidance of

Prof. A. S. SHINDE

DEPARTMENT DEPARTMENT OF INFORMATION INFORMATION TECHNOLOGY

SINHGAD ACADEMY OF ENGINEERING PUNE-48 2011-2012



CERTIFICATE This is to certify that the Preliminary Project Report entitled

MULTI-TRACKING MULTI-TRACKING SYSTEM submitted by SAMEER DAREKAR ATUL CHIKANE AMOL DESHAMUKH RUTUJIT DIWATE for the partial fulfilment of the requirement for award of a degree Bachelor of Engineering in Information Technology, to University of Pune; is a bonafide work carried out during academic year 2011-2012.

(Prof. A. S. Shinde) Guide Departmen Departmentt of Informatio Information n Tec Technology hnology

(Prof. A.N.Adapanwar) Head Departmen Departmentt of Information Information Technolog echnology y



CERTIFICATE This is to certify that the Preliminary Project Report entitled

MULTI-TRACKING MULTI-TRACKING SYSTEM submitted by SAMEER DAREKAR ATUL CHIKANE AMOL DESHAMUKH RUTUJIT DIWATE for the partial fulfilment of the requirement for award of a degree Bachelor of Engineering in Information Technology, to University of Pune; is a bonafide work carried out during academic year 2011-2012.

(Prof. A. S. Shinde) Guide Departmen Departmentt of Informatio Information n Tec Technology hnology

(Prof. A.N.Adapanwar) Head Departmen Departmentt of Information Information Technolog echnology y

Acknowledgements Prof. A.S. A.S. Shinde Shinde, for her First and foremost, we would like to thank our guide, Prof. guidance and support. We will forever remain grateful for the constant support and guidance extended extended by guide, in making this project pro ject successf successful ul till now. Through Through our many discussions, she helped us to form and solidify ideas. The invaluable discussions we had with her, the penetrating questions she has put to us and the constant motivation, has all led to the development of this project till now with great passion. We wish to express our sincere thanks to External guide, Mr.Sandip Mr.Sandip Madiwal Madiwal and Mr.Sharad P. their invaluable guidance to us and their constant motivation has not let our spirit die. We also thank all the supporting staff of Sands Technologies who has helped us in one or the other way and for their extended support. We would also like to thank to our friends for listening to our ideas, asking questions and providing feedback and their suggestions for improving our ideas and last but not the least we would like to thank our technical assistance staff in college for solving the critical problems we got till now.

Contents 1 Introduction

1

1.1 Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1

1.2 Need of GPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1

1.3 Basic concepts

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2

1.4 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3

2 Literature Survey 2.1 2.1 Techn hnol olog ogie iess availa ailabl blee to cate caterr the the same same serv servic icee . . . . . . . . . . . . . .

5 5

2.1.1

Automotive Navigation System . . . . . . . . . . . . . . . . . . .

5

2.1.2

GPSylon system . . . . . . . . . . . . . . . . . . . . . . . . . . .

6

2.1.3

Open GTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8

2.2 Review of existing System . . . . . . . . . . . . . . . . . . . . . . . . . .

9

3 Pro ject Statement

11

3.1 Purpose b ehind the Pro je ject . . . . . . . . . . . . . . . . . . . . . . . . .

11

3.2 Decision of Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11

3.3 Market Survey . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12

3.4 Uniqueness in the pro je ject: . . . . . . . . . . . . . . . . . . . . . . . . . .

12

3.5 Methodo odology for solving this propos posed theme . . . . . . . . . . . . . . . .

12

3.5.1

Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12

3.5.2

Working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13

4 System requirement and specification 4.1 Software requirements spec pecifications . . . . . . . . . . . . . . . . . . . . .

14 14

4.1.1

Intro duction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14

4.1.2

User Classes and Characteristics . . . . . . . . . . . . . . . . . . .

14

4.1.3

Operating Environment . . . . . . . . . . . . . . . . . . . . . . .

15

CONTENTS

CONTENTS

4.1.4

External Interface Requirements . . . . . . . . . . . . . . . . . . .

15

4.1.5

Other Non functional Requirements . . . . . . . . . . . . . . . . .

16

4.2 UML Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17

4.2.1

Use case Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . .

17

4.2.2

Sequence Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . .

25

4.2.3

Communication Diagram . . . . . . . . . . . . . . . . . . . . . . .

31

4.2.4

Activity Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . .

34

4.2.5

Class Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . .

35

4.2.6

Package Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . .

36

4.2.7

Interaction Overview Diagrams . . . . . . . . . . . . . . . . . . .

37

4.2.8

State Chart Diagram . . . . . . . . . . . . . . . . . . . . . . . . .

38

4.2.9

Entity Relationship(ER) Diagram . . . . . . . . . . . . . . . . . .

39

4.2.10 Data Flow Diagrams . . . . . . . . . . . . . . . . . . . . . . . . .

40

5 Planning and Scheduling the prop osed Pro je ject Work

42

5.1 Implementation Details . . . . . . . . . . . . . . . . . . . . . . . . . . . .

42

5.2 Gantt Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

43

List of Figures 2.1 The Automotive Navigation System in Car.(The Main Window) . . . . .

6

2.2 Location Markers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7

2.3 Open GTS Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8

3.1 Architecture of Multi-tracking system . . . . . . . . . . . . . . . . . . . .

13

4.1 Context level Use Case Diagram. . . . . . . . . . . . . . . . . . . . . . .

17

4.2 Use Case Diagram for Login . . . . . . . . . . . . . . . . . . . . . . . . .

18

4.3 Use Case Diagram for control vehicle . . . . . . . . . . . . . . . . . . . .

19

4.4 Use Case Diagram for create geofence . . . . . . . . . . . . . . . . . . . .

20

4.5 Use Case Diagram for create logs . . . . . . . . . . . . . . . . . . . . . .

21

4.6 Use Case Diagram for create reports . . . . . . . . . . . . . . . . . . . .

22

4.7 Use Case Diagram for get details . . . . . . . . . . . . . . . . . . . . . .

23

4.8 Use Case Diagram for trace location . . . . . . . . . . . . . . . . . . . .

24

4.9 Sequence Diagram for Login . . . . . . . . . . . . . . . . . . . . . . . . .

25

4.10 Sequence Diagram for Create reports and alerts . . . . . . . . . . . . . .

27

4.11 Sequence Diagram for Trace Location . . . . . . . . . . . . . . . . . . . .

29

4.12 Communication Diagram for Login . . . . . . . . . . . . . . . . . . . . .

31

4.13 Communication Diagram for Create reports and alerts . . . . . . . . . .

32

4.14 Communication Diagram for Trace Location . . . . . . . . . . . . . . . .

33

4.15 Overall Activity Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . .

34

4.16 O verall Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . .

35

4.17 Overall Package Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . .

36

4.18 Overall Interaction Overview Diagram . . . . . . . . . . . . . . . . . . .

37

4.19 Overall State Chart Diagram . . . . . . . . . . . . . . . . . . . . . . . .

38

4.20 Entity Relationship(ER) Diagram . . . . . . . . . . . . . . . . . . . . . .

39

4.21 Level 0 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . .

40

LIST OF FIGURES

LIST OF FIGURES

4.22 Level 1 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . .

41

5.1 Implementation detail diagram . . . . . . . . . . . . . . . . . . . . . . .

42

5.2 gantt chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

44

List of Tables 4.1 Use case Description Table for Login . . . . . . . . . . . . . . . . . . . .

18

4.2 Use case Description Table for control vehicle . . . . . . . . . . . . . . .

19

4.3 Use case Description Table for Create Geofence . . . . . . . . . . . . . .

20

4.4 Use case Description Table for Create Logs . . . . . . . . . . . . . . . . .

21

4.5 Use case Description Table for Create Reports . . . . . . . . . . . . . . .

22

4.6 Use case Description Table for Get Details . . . . . . . . . . . . . . . . .

23

4.7 Use case Description Table for Trace Location . . . . . . . . . . . . . . .

24

4.8 Event Flow Table for Login . . . . . . . . . . . . . . . . . . . . . . . . .

26

4.9 Event Flow Table for Create reports and alerts . . . . . . . . . . . . . . .

28

4.10 Event Flow Table for Trace Location . . . . . . . . . . . . . . . . . . . .

30

Chapter 1 Introduction 1.1

Motivation The motivation for Multi-Tracking System is the desire for advanced features in

an inexpensive receiver. Currently, all OEM GPS receivers i.e., the single GPS receiver boards with no case, display, etc, proprietary firmware which makes certain assumptions on the system dynamics or application which may not be appropriate. Currently there is no single system that integrates all tracking and tracing of any movable objects, there are applications but all of them are separate so to integrating all of them was the source of motivation for our team.

1.2

Need of GPS Trying to figure out where you are is probably mans oldest pastime.

You may think that you only need a GPS tracking device to get you from point A to point B if you are unsure of where you are driving, but did you know that there are many other tracking systems that you may have a use for? GPS tracking systems are used to track anyone and anything these days. Technology has rapidly advanced in the past few years and it has become very easy for the average person to use a tracking system. If you have a vehicle, then you will want to place a GPS tracking system under your dash or in your glove compartment. This way, if your car ever gets stolen, you will be able to locate it within seconds. If you have a small child, you will want to have a tracking system in place in case 1

Multi-Tracking System

Group No. 14

they get lost or wander off. Every second counts with a lost or abducted child, so a tracking device is imperative to avoid a possible disastrous and heartbreaking outcome. If you have valuable items in your home like jewelry, or electronics you will want a GPS tracking system in case they are ever stolen. There are also various tracking systems that can locate items inside buildings and parking garages. If you have a teenager, you will want to use a GPS tracking system to make sure that they are driving responsibly and they are going where they told you they were going. If you suspect your spouse or significant other of cheating, a good tracking system will be able to confirm or absolve your suspicions.

1.3

Basic concepts A GPS receiver calculates its position by precisely timing the signals sent by GPS

satellites high above the earth. Each satellite continually transmits messages that include •

The time the message was transmitted

•

Precise orbital information the general system health and rough orbits of all GPS satellites. The receiver uses the messages it receives to determine the transit time of each

message and computes the distance to each satellite. These distances along with the satellites’ locations are used with the possible aid of trilateration depending on which algorithm is used, to compute the position of the receiver. This position is then displayed, perhaps with a moving map display or latitude and longitude; elevation information may be included. Many GPS units show derived information such as direction and speed, calculated from position changes. Three satellites might seem enough to solve for position since space has three dimensions and a position near the Earth’s surface can be assumed. However, even a very small clock error multiplied by the very large speed of light the speed at which satellite signals propagate results in a large positional error. Therefore receivers use four or more satellites to solve for the receiver’s location and time. The very accurately computed time is effectively hidden by most GPS applications, which use only the location. A few specialized GPS applications do however use the time; these include time transfer, traffic SAE Dept of Information Technology

2

2011 12


Group No. 14

signal timing, and synchronization of cell phone base stations. Although four satellites are required for normal operation, fewer apply in special cases. If one variable is already known, a receiver can determine its position using only three satellites. For example, a ship or aircraft may have known elevation. Some GPS receivers may use additional clues or assumptions (such as reusing the last known altitude, or including information from the vehicle computer) to give a less accurate (degraded) position when fewer than four satellites are visible. Global Positioning System (GPS) is a satellite-based radio-positioning and timetransfer system designed, financed, deployed, and operated by the U.S. Department of Defense. GPS has also demonstrated a significant benefit to the civilian community who are applying GPS to a rapidly expanding number of applications. What attracts us to GPS is: •

The relatively high positioning accuracies, from tens of metres down to the millimetre level.

•

The capability of determining velocity and time, to an accuracy commensurate with position.

•

The signals are available to users anywhere on the globe: in the air, on the ground, or at sea.

•

Its is a positioning system with no user charges, that simply requires the use of relatively low cost hardware.

•

It is an all-weather system, available 24 hours a day.

•

The position information is in three dimensions, that is, vertical as well as horizontal information is provided

1.4

Application The application of GPS Technology is very vast it is currently used in many fields

in the advanced countries but in countries like India the use of GPS is improving. GPS can be used in following technologies:


Group No. 14

•

For tracking of Car, Person or any other movable objects

•

GPS device can be used to give other parameters like latitude, longitude, altitude, and other parameters like temperature and pressure can also be found out.

Chapter 2 Literature Survey 2.1

Technologies available to cater the same service

In the literature survey we did the survey of certain systems which are common used in vehicle tracking systems worldwide, we just studied their working and tried to find unique features and disadvantages about them and tried to learn something new from each system. Following are some systems we studied.

2.1.1

Automotive Navigation System

An automotive navigation system is a satellite navigation system designed for use in automobiles. It typically uses a GPS navigation device to acquire position data to locate the user on a road in the unit’s map database. Using the road database, the unit can give directions to other locations along roads also in its database. Dead reckoning using distance data from sensors attached to the drivetrain, a gyroscope and an accelerometer can be used for greater reliability, as GPS signal loss and/or multipath can occur due to urban canyons or tunnels. The portable GPS devices have helped increase and enhance safety for our citizens. In addition, the GPS system is a phenomenal navigational tool that is vital to every traveller.


Group No. 14

Figure 2.1: The Automotive Navigation System in Car.(The Main Window)

Disadvantages of Automotive Navigation system: •

It is a stand-alone application being used by the driver alone

•

It is kept in the Car and the driver gets assistance to the street view

•

It cannot help the owner of the car to monitor the vehicle

2.1.2

GPSylon system

GPSylon is able to show maps downloaded from the expedia map servers. It may connect to a gps device and track your position on the maps. At the moment, it is able to read gpsdata in the NMEA standard from a serial gps device, a file or a gps daemon across a network. The main feature is the display of various maps. GPSylon allows the user to navigate around like in a digital atlas. It shows maps of different scales, so missing maps of one scale do not result in a black screen, but show the next larger scale. It allows the download of a single map or for a given location or for multiple maps in a given rectangular area from mapblast or expedia map servers. In the download mouse mode the user may choose a single map or by dragging a rectangle with the mouse, the user may choose to download maps for a larger area. This functionality allows the user to download maps in a given scale for a larger area. Please only download maps you need and be careful not to download thousands of maps, as the map providers will discontinue


Group No. 14

their service when it is misused!

Figure 2.2: Location Markers

Disadvantages of GPSylon: •

It is a desktop Application not web based so it requires installing on machine.

•

It needs to download maps from the servers now and then which in turn affects in performance.

•

It uses expedia maps which are not much efficient as the google maps.

•

It cannot be used on devices like i-pad or mobile phones as it is desktop application

•

We cannot control sub parts of the vehicle by this system.


2.1.3

Group No. 14

Open GTS

OpenGTS (”Open GPS Tracking System”) is the first available open source project designed specifically to provide web-based GPS tracking services for a ”fleet” of vehicles. To date, OpenGTS has been downloaded and put to use in over 90+ countries around the world to track many 1000’s of vehicles/assets around all 7 Continents. The types of vehicles and assets tracked include taxis, delivery vans, trucks/trailers, farm equipment, personal vehicles, service vehicles, containers, ships, ATVs, personal tracking, cell phones, and more. While OpenGTS was designed to fill the needs of an entry-level fleet tracking system, it is also very highly configurable and scalable to larger enterprises as well. Open GTS is entirely written in JAVA, using technologies such as Apache Tomcat for web service deployment, and MySQL for the datastore.

Figure 2.3: Open GTS Demo


Group No. 14

Disadvantages of Open GTS: •

It supports only vehicle tracking and not personal tracking and other features.

•

OpenGTS comes with support for OpenLayers/OpenStreetMap which are still not as efficient as the Google maps.

•

It does not support tracking of multiple vehicles.

•

We cannot control sub parts of a vehicle via SMS from remote location.

•

It uses only GPS network not GSM network so there is no communication with the user.

2.2

Review of existing System Thus we studied all of the above GPS Tracking and Tracing systems. We noted

all the drawbacks of each system and also noted their salient features and tried to make improvements in our system as follows The Automotive Navigation system is present in the vehicle only so if the owner of the car wants to keep a watch on the Car or the Driver it is not possible via this system, So we decide to make a web application that can be accessed from any where and any time round the world The GPSylon System is a stand alone desktop application so it needs installation on any computer before using it also there could be problems of platform or the OS while installing it. It downloads the maps every time when the vehicle enters the location this in turn affects the performance but instead if a web application is used we can avoid the problem of the installation and downloading maps. The Open GTS system is one of the most efficient of all the three systems but the problem with this system is, it only supports vehicle tracking and not others also it can track only a single vehicle at a time. This system uses only the GPS network so we cannot communicate with the vehicle also we cannot control the vehicle sub parts, so to overcome this we decided to use GPS as well as GSM network so that we can communicate with the AVL in the car via SMS and also give commands to it. Seeing all this we came to a conclusion that we have to develop a system which tries to implement almost all the salient features of the existing system and try to remove


Group No. 14

the most drawbacks of the existing system so as to get a completely different system. We also met the customers using this services and tried to take their review

Chapter 3 Project Statement 3.1

Purpose behind the Project There are some companies which has many vehicles to handle and to handle such

a large number of vehicles is a very hectic task, keeping the track of all the vehicles, their drivers, performance of their drivers, performance of their cars these are all very important task which requires lots of money and manpower GPS can also be used to track the school going children the old people and where there is always a risk of loss of the person or property. We studied all the major GPS systems used for vehicle and other assets tracking and came up with the idea of new this multi tracking system. We will try to implement all the salient features of the other systems and try to eliminate the drawbacks. We experienced the main thing in almost all of the applications that we could not communicate with the vehicle in any of the circumstances so we did market survey for the device which are available.

3.2

Decision of Scope As the project was to track and trace multiple objects so the scope could have been

very vast, so to narrow down the scope initially we decided to implement this system for Vehicle and Personal Tracking only.


3.3

Group No. 14

Market Survey The market survey for various devices available for GPS tracking was done with the

help of our external guide. We selected two three devices from that the device of Teltonika FM 4200 was selected on account of its features, ease of use and cost effectiveness for vehicle tracking. For personal tracking the company ARGUS was to prepare a device as per the specifications given by the company.

3.4

Uniqueness in the project: As we had done the survey of various GPS tracking and tracing system we had a

brief idea of their working, we also knew their disadvantages of inconvenience of communication so we decided to use two networks i.e. GPS and GSM network We could communicate with the device with the help of mobile via a GSM network as we could configure both of the devices to be triggered via a single SMS. Also the device communicates with the tracking server via a GPRS network. Also we can control the triggerable events in the Car such as controlling of ignition, Switching ON/OFF AC, closing and opening of the doors etc.

3.5

Methodology for solving this proposed theme

3.5.1

Architecture

The components of system are as follows •

GPS Satellite

•

GPS Devic (AVL)

•

Local GSM Service Provider

•

Tracking server (Having Static IP)

•

Client PC


Group No. 14

Figure 3.1: Architecture of Multi-tracking system

3.5.2

Working

The GPS satellite gives the exact position of the device which is situated in the Car. This device is in turn which is connected to the local GSM service provider via a GSM network as it has SIM card present in it thus the GPS parameters which the device has are send to the tracking server which has a Static IP address via a GPRS network. The tracking server consists of a Socket listener application running in the background which listens at a particular port. The GPS parameters recieved by the port listener are given to the Parser and converter for proper conversions and this data is stored in the database. These values from the database are fetched and are manipulated to get the reports in proper format.

Chapter 4 System requirement and specification 4.1

Software requirements specifications

4.1.1

Introduction

Document Conventions The requirements are arranged in the order in which they are required.

Intended Audience and Reading Suggestions The intended audience includes all stakeholders as mentioned below •

Developers

•

Users/Designers

•

Testers

•

Documentation Writers

4.1.2

User Classes and Characteristics

The functionalities of the system being developed are divided according to the role of the user. The roles may be divided as •

Super Admin

•

Admin administrator the system


•

User

•

Demo User

4.1.3

Group No. 14

Operating Environment

The system is a web based application it can work on any Operating System with a well equipped web browser. It just requires internet connection to view report, to see the current position of a vehicle or person and other related activities.

4.1.4

External Interface Requirements

User Interfaces User interface will be web page integrated with google maps to show the proper location. User will choose various reports from the list of reports to be generated.

Hardware Interfaces •

Client PC with Internet Connection.

•

Server with Static IP.

•

AVL (Advance Vehicle Locator) Device.

•

GSM SIM Card with GPRS activated.

Software Interfaces •

FM42xx Configurator (for configuration of AVL)

•

Microsoft Visual Studio 10.

•

.Net framework 3.0 or greater.


4.1.5

Group No. 14

Other Non functional Requirements

Performance Requirements •

System should take minimum time for report generation.

•

The system performance must not affect by the number of vehicles present.

•

The web pages should not take much time to load the pages.

Security Requirements •

System should not grant authentication to any unauthorised person.

•

The system should not be vulnerable to the security attacks.

•

Information related to Admin password should be confidential.

Software Quality Attributes The system ensures the following software quality attributes •

Reliability

•

Efficiency

•

Security

•

User-friendliness

•

Flexibility


4.2 4.2.1

UML Diagrams Use case Diagrams

Here are Use case diagrams of the project

Context level use case diagram

Figure 4.1: Context level Use Case Diagram.

Group No. 14


Group No. 14

Use case Diagram for Login

Figure 4.2: Use Case Diagram for Login

Table 4.1: Use case Description Table for Login Actors User, Admin and SQL server Description

Login

Trigger

Giving Username and Password

Preconditions

Username and password should be predefined

Postconditions

If password and username is correct grant access

Normal Flow

Allows to access the feature

Alternative Flows

Displays error message

Priority

High

Frequency of Use

High


Group No. 14

Use case Diagram for Control Vehicle

Figure 4.3: Use Case Diagram for control vehicle

Table 4.2: Use case Description Table for control vehicle Actors User and AVL Description

Controlling vehicle via Mobile

Trigger

Sending message in proper format

Preconditions

messages for proper operations are defined

Postconditions

-

Normal Flow

Vehicle behaves as per message

Alternative Flows


Priority

High

Frequency of Use

High


Group No. 14

Use case Diagram for Create Geofence

Figure 4.4: Use Case Diagram for create geofence

Table 4.3: Use case Description Table for Create Geofence Actors User, SQL server and Google map web service Description

Creating Geofence

Trigger

Drawing Geofence

Preconditions

Specify the centre and radius of Geofence

Postconditions

The Geofence is created and visible on map

Normal Flow

when vehicle enters geofence it is displayed

Alternative Flows


Priority

High

Frequency of Use

High


Group No. 14

Use case Diagram for Create Logs

Figure 4.5: Use Case Diagram for create logs

Actors

Table 4.4: Use case Description Table for Create Logs User, SQL server, AVL, Parser and Converter and Port Listener

Description

Creating Logs

Trigger

Receiving Data from AVL

Preconditions

Specifying the span of receiving logs

Postconditions

Logs are saved

Normal Flow

Log files are Created

Alternative Flows


Priority

High

Frequency of Use

Very High


Group No. 14

Use case Diagram for Create Reports

Figure 4.6: Use Case Diagram for create reports

Table 4.5: Use case Description Table for Create Reports Actors User and SQL server Description

Creating Reports

Trigger

Request for creation of reports

Preconditions

Specifying the the type of reports

Postconditions

Reports are created and saved

Normal Flow

Report files are Created

Alternative Flows


Priority

High

Frequency of Use

High


Group No. 14

Use case Diagram for Get Details

Figure 4.7: Use Case Diagram for get details

Table 4.6: Use case Description Table for Get Details Actors User and SQL server Description

Getting various details

Trigger

Details entered by person or given by device

Preconditions

-

Postconditions

-

Normal Flow

Save Details

Alternative Flows


Priority

High

Frequency of Use

High


Group No. 14

Use case Diagram for Trace Location

Figure 4.8: Use Case Diagram for trace location

Table 4.7: Use case Description Table for Trace Location Actors User, AVL, Port Listener, SQL server and Google map web service Description

Tracing location of any moving ob ject

Trigger

Whenever the vehicle moves from one position to another

Preconditions

The Vehicle is configured with AVL

Postconditions

-

Normal Flow

Store in database

Alternative Flows


Priority

Very High

Frequency of Use

Very High


4.2.2

Group No. 14

Sequence Diagrams

Sequence Diagram for Login

Figure 4.9: Sequence Diagram for Login


Group No. 14

Event Flow table for Login

Msg No.

Table 4.8: Event Flow Table for Login Source Destination Message

1

Admin

Login Page

Login by Admin

1.1

Login Page

Login Controller

Validate Login of Admin

2

Login Controller

User Details

Check Username Password

3

User Details

SQL Server

Check into Server

4

SQL Server

Login Controller

Boolean Reply

4.1

Login Controller

Admin

Authenticate and Redirect

5

User

Login Page

Request Username and Password

5.1

Login Page

Login Controller

Notify Admin

6

Login Controller

Admin

give proper details

7

Admin

Login Controller

give Username and Password

7.1

Login Controller

SQL Server

Store Username and Password

8

User

Login Page

Enter Username and Password

8.1

Login Page

Login Controller

Validate Login

8.1.1

Login Controller

User Details

give Username and Password

9

User Details

Sql Server

Check into Server

10

SQL Server

Login Controller

give boolean reply

10.1

Login Controller

User

Authenticate and Redirect


Group No. 14

Sequence Diagram for Create reports and alerts

Figure 4.10: Sequence Diagram for Create reports and alerts


Group No. 14

Event Flow table for Create reports and alerts Table 4.9: Event Flow Table for Create reports and alerts Msg No. Source Destination Message 1

User

Viewing Page

Request for reports

1.1

Viewing Page

Viewing Controller

Give Parameters

Viewing Controller Reports and Alerts

Check into Table

2 2.1

Reports and Alerts

SQL Server

Request

3

SQL Server

3.1

Reports and Alerts

Viewing Controller

Get Data

4

Viewing Controller

Viewing Page

Show to user

5

Alert Controller

SQL server

Check Exceptions

6

SQL server

Alert Controller

Respond to Request

6.1

Alert Controller

User

Send Alerts

Reports and Alerts Respond to Request


Sequence Diagram for Trace Location

Figure 4.11: Sequence Diagram for Trace Location

Group No. 14


Group No. 14

Event Flow table for Trace Location

Msg No.

Table 4.10: Event Flow Table for Trace Location Source Destination Message

1

User

Location Page

Request for tracing

1.1

Location Page

Location Controller

Give Parameters

1.1.1

Location Controller

AVL

Request Co-Ordinates

2

AVL

Port Listener

Send Data

3

Port Listener

Location Details

Convert Data

4

Location Details

SQL Server

Store to Database

5

Location Details

Location Controller

Give Co-Ordinates

6

Location Controller

Google map API

Send Co-Ordinates

7

Google map API

Location Page

Trace on Map


4.2.3

Communication Diagram

Communication Diagram for Login

Figure 4.12: Communication Diagram for Login

Group No. 14


Group No. 14

Communication Diagram for Create reports and alerts

Figure 4.13: Communication Diagram for Create reports and alerts


Communication Diagram for Trace Location

Figure 4.14: Communication Diagram for Trace Location

Group No. 14


4.2.4

Group No. 14

Activity Diagrams

Overall Activity diagram

Figure 4.15: Overall Activity Diagram


4.2.5

Group No. 14

Class Diagrams

Overall Class Diagram

Figure 4.16: Overall Class Diagram


4.2.6

Group No. 14

Package Diagrams

Overall Package Diagram

Figure 4.17: Overall Package Diagram


4.2.7

Interaction Overview Diagrams

Overall Interaction Overview Diagram

Figure 4.18: Overall Interaction Overview Diagram

Group No. 14


4.2.8

State Chart Diagram

Overall State Chart Diagram

Figure 4.19: Overall State Chart Diagram

Group No. 14


4.2.9

Entity Relationship(ER) Diagram

Entity Relationship(ER) Diagram

Figure 4.20: Entity Relationship(ER) Diagram

Group No. 14


4.2.10

Group No. 14

Data Flow Diagrams

Level 0 Data Flow Diagram

Figure 4.21: Level 0 Data Flow Diagram


Group No. 14

Level 1 Data Flow Diagram

Figure 4.22: Level 1 Data Flow Diagram

Chapter 5 Planning and Scheduling the proposed Project Work 5.1

Implementation Details

Figure 5.1: Implementation detail diagram


Group No. 14

The Implementation of the Multi-Tracking system consists of the following steps

•

Port Listener Creation

•

Parser Creation

•

Database Creation

•

Development of GUI

•

Preparation of Reports as Requested by User The Implementation diagram shows the current status of the project the first 3 steps

that are Port Listener, parser and Database are done the remaining parts that are GUI development and Reports are to be done the timeline which is followed is shon in the next section.

5.2

Gantt Chart The Gantt Chart shows the time line which is followed for the development of the

project and their predicted dates of completion the timeline for our project is as shown in the gant chart given.


Group No. 14

Figure 5.2: gantt chart

Project Report

Recommend Documents