Designdoc Predpol
Designdoc Predpol
Team LocP
Sherelien Haase
Connor Leary
Chris Miller
Eduardo Trejo
Table of Contents
1. INTRODUCTION
1.1 Purpose
1.2 Scope
1.3 Overview
1.4 Reference Material
1.5 Definitions and Acronyms
2
2
2
2
2
2
2. SYSTEM OVERVIEW
PredPol GPS
Software Design Document
3. SYSTEM ARCHITECTURE
3.1 Architectural Design
3.2 Design Rationale
3
3
3
4. DATA DESIGN
4.1 Data Dictionary
3
3
3
3
4
4
6. REQUIREMENTS MATRIX
1. INTRODUCTION
1.1 Purpose
Create a simple Android app that Police officers will use on patrol which continually
sends the GPS location of the officer to their agency's database.
1.2 Scope
Law enforcement Agencies around the world are always looking for a way to improve
how they protect their citizens. Our approach to help them is to develop a way for them
to see when high crime areas develop to help improve the overall coverage of their
patrol routes.
1.3 Overview
Our application for android devices will allow the officer to connect to a secure server
where there location will be logged every 15 feet the officer moves while walking or
driving. The application will show the officer where there is a need for police presence,
giving them information about the crimes at risk in that location.
PredPol GPS
Software Design Document
Android Studio
SourceTree
GitHub
3. SYSTEM ARCHITECTURE
3.1 Architectural Design
The app is divided into two activity screens: The login, and the map. The login screen
will handle user identification with the server and will only be executed with a successful
login. The map screen will handle location services with the secure connection and will
continue to track location data until the app is logged out.
3.2 Design Rationale
There is no need for any user verification to occur while an officer is holding the device,
so a secure connection should be created outside the scope of data transmission.
Likewise, there is no reason to track the location of a device that is not currently logged
in.
4. DATA DESIGN
PredPol GPS
Software Design Document
4.1 Data Description
Field
Notes
Type
Id
int
adress
varchar
longitude
double
latitude
double
Effective date
Date that the district was added to the the patrol history
date
PredPol GPS
Software Design Document
6. REQUIREMENTS MATRIX
Requirement
ID
Requirement Type
Requirement Description
Source
001
Chore
002
Chore
003
Functionality
004
Functionality
005
Functionality
006
Functionality
Toolbar
007
Non-Functionality
PredPol GPS
Software Design Document
5
token
008
Non-Functionality
009
Functionality
010
Non-Functionality