CyberGIS ECY6489 Group Project (Final report ...

ohiofulvousSoftware and s/w Development

Aug 15, 2012 (5 years and 3 months ago)

340 views



CyberGIS








ECY6489

Group

Project

(Final report)





Department of Electrical & Computer Engineering

Faculty of Engineering Technology

The Open University of Sri Lanka



September
2011





CyberGIS









Undergraduate Final project Report

Submitted

in partial fulfillment of

the requirements for the

Degree of Bachelor of Software Engineering

in

Department of Electrical & Computer Engineering

The Open University of Sri Lanka








Supervisor
s






Project Group

Dr.
L.S.K Udugama



M.S.R Perera<209087374>

Dr. Uditha Ratnayake



D.S Kulasuriya<709087412>







W.M.D Jeewantha
<
509087436
>




September 2011


i


Acknowledgement

We
would

like to
thank our head of department
Dr.L.S.K
Udugama
and our project
supervisor

Dr
. (Mrs.
) Uditha Rathnayake for their
valuable
guidance & advic
e.

Also we
would like to
thank our parents for their support, encouragement and belief. We highly
appreciate the support given by our employers and
project heads by providing the
ind
ustry exposure and study leaves. Finally we would like to thank all other parties for
their support at least by a encouraging word.





ii


Abstract

The main purpose of this project was to fulfill
the credit requirement

of

ECY6489
module
under the Bachelor of Software Engineering
Degree
.

The goal of this project was
to take the existing GIS based solution to the next level

by providing more features and
make more beneficial for
potential geographically distributed domains
. I
n this CyberGIS
system we achieved this goal by introducing customizable domain maps, reporting and
analysis features, and mobile based capabilities.



iii


Table of Contents


CHAPTER NO.



TITLE


PAGE NO.




ACKNOWLEDGEMENT

I

ABSTRACT

II

LIST OF TABLES

V

LIST OF FIGURES

VI

LIST OF ABBREVIATION
S

VII

INTRODUCTION

1

LITERATURE SURVEY

2

2.1 Similar
Systems

2

2.2 Theoretical Background

2

2.3 Required Components

2

PROPOSED METHOD

3

3.1 Introduction

3

3.2 System R
equirements

3

3.3 Main Components and Flow

6

3.4 Project Plan and Approach

7

DESIGN OF SOFTWARE

10

FABRICATIO
N OF SOFTWARE

11

TESTING AND IMPLEMEN
TATION

12

RESULTS

13

CONCLUSION AND FUTUR
E WORK

14

8.
1 CyberGIS GUI Module.

14

8.2 CyberGIS Mobile Component.

15


iv


8.3 CyberGIS Service Module.

15

PROJECT CONTRIBUTION
S

16

9.1 Pr
oject Contribution by: M.S.R Perera <209087374>

16

9.2 Contribution by: D.S Kulasuriya<709087412>

17

9.3

Contribution by: W.M.D.R Jeewantha<509087436>

18

APPENDIX

19

Appendix A


Use cas
e Diagrams

19

Appendix A1


CyberGIS Admin User Use Case Diagram

19

Appendix A2


CyberGIS Operative User Use Case Diagram

20

Appendix B


Class Diagrams

21

Appendix B1

CyberGIS Mobile Service Class Diagram

21

Appendix B2


CyberGIS Service Module Class Diagrams

22

Appendix B3


CyberGIS Service Business Logic Class Diagrams

23

Appendix C


ER Diagram

24

Appendix D

Screen Designs

25

Ap
pendix D1


CyberGIS Admin Main Screen

25

Appendix D2


CyberGIS Admin Report Screen

26

Appendix D3


CyberGIS Mobile Login

27

Appendix D4


CyberGIS Mobile Main Screen

28

Appendix D5


CyberGIS Mobile Task List

29

Appendix D6


CyberGIS Mobile Task Details

30

Appendix D7


CyberGIS Mobile Task Notification

31

Appendix D8


CyberGIS Mobile Task Status Update

32





v


List of T
ables


Table ID

Table Description

Page No.

Table 3.1

Functional Requirements

4

Table 3.
2

Project Deliverable
s

7

Table 3.
3

Actual vs. Planned

8






















vi


List
of F
igures


Figure

ID

Figure

Description

Page No.

Figure 3.
1

CyberGIS System

6

Figure

4.1

General Architecture

9





















vii


List of
Abbreviations


Abbreviations

Description

AJAX

Active JavaScript And XML

API

Application Programming Interface

DB

Data Base

GIS

Geographic Information System

GUI

Graphical User Interface

IDE

Integrated Development Environment

J2ME

Java 2 Mobile Edition

JMS

Java Messaging Services

JPA

Java Persistent API

JSF

Java Server Faces

ORM


OS

Operating System

QA

Quality Assurance

RMI

Remote Method Invocation

SRS

System Requirement Specification

UI

User Interface

URL

Universal Resource Locator

WTK


XML

Extensible Markup Language










1


CHAPTER 01

INTRODUCTION


The CyberGIS
system
is

designed
based on the

vision

make use of existing GIS data
providers and

expand that technology into new levels,
that the

society can make more use
of it in

their domains
.”

So

we proposed and developed a
web based
system that users of
this system can
tag

their geographically distributed
domain entities on a map, customize
these entity details
and, store and share them only among other required and authorized
parties within the domain
.

At the time w
hen we were proposing the CyberGIS
sys
tem there were GIS Systems either
that required high GIS and mapping knowledge which bit complex (ESRI ArcGIS) or
very simple with few functionalities (Google Map).

Very Complex GIS Systems avoided
the wide and genera
l use by many potential domains as high costs, requirement of GIS
professional and less usability. On the other hand very simple

GIS Systems did the same
thing by not providing authorized and secure data access, less customizability and
no
reporting and an
alysis features.


As a solution to this problem we developed the CyberGIS system

with capabilities
as
mapping entities, manipulating entity data, mobile operative command, reporting and
analysis while ensuring
customizability,

usability, security and perf
ormance.

So we would like to believe the CyberGIS is a concept rather than a system
that will
grow into higher levels that will
help potential geographically distributed domain to
store,
track and

coordinate
their distributed entities and facts. Also this
concept will assist
decision making and planning by providing reporting and analysis capabilities
.





2


CHAPTER 02

LITERATURE SURVEY

2.1
Similar Systems

During our literature survey of similar systems we found out that Microsoft Map Point
(
http://en.wikipedia.org/wiki/Microsoft_MapPoint
) is an enterprise level system that is
having the similar functionalities like the CyberGIS system. And provide the following
functionalities.



Pin
point data relationships



Identify business trends



Highlight opportunities

One of the main advantages of using the CyberGIS system over the Microsoft map point
system is that the CyberGIS system will be available as a freeware system to the users
and the bu
siness domains will not be charged for using the system but only for the
Customer Support functionality related to the system.

2.2
Theoretical Background

During the literature survey of the theoretical background we did look into mainly two
GIS information

providers and they are:

1. Open Street Map:
http://www.openstreetmap.org/

2. Google Maps:
http://maps.google.com/


After reviewing the above two external GIS providers
we decided to go with Google
Map due to their reliability, quality of map imagery /choices of different map image types
as : hybrid ,satellite and their array of functions provided by them Free or charge.

2.3
Required

Components

During the literature surve
y of the required software components of the project we’ve
decided to choose the spring framework as our base enterprise we framework for building
our business logic on. Other than spring we will be using the Java Persistence API (JPA)
and Oracle (toplink)

ORM for database access and data
base manipulation.
For the mobile
operative end user component of the CyberGIS system we’ve used the Java J2ME
technology.


3


CHAPTER 03

PROPOSED METHOD

3.1
Introduction

The CyberGIS system is basically provides the GIS
solution with extended
functionalities.

The system will provide customizable web based
domain maps.

The
system creates domains for separate users which are working with controlled and highly
secured access to the CyberGIS web service. So a particular user
can only access to their
domain and view maps for their domain. Users can manage their domains as they want
using granted access rights and customized capabilities. As any other GIS system,
CyberGIS will provid
e the basic map operations like
Search for lo
cations
,
Find location
using latitude and longitude
,
Zoom In and Zoom Out
,
Scroll the map
,
View location
names and tags
,
Show Roads and Railways.

Other than to these, users can create any
tags, markers and locations as related to their business requirement
s. Those remarks are
only visible to those particular domain users only.

Past records are kept with the system
for each user and can be retrieved as statistics in any situation. Those details are highly
secured and provide controlled access. Those statisti
cs are available to management
decision making and planning processes of the clients.

3.2
System Requirements

System requirements for the CyberGIS system basically divided into two categories as
functional requirements and non functional requirements.
More details can be found in
CyberGIS System Requirements Specification document.






4


Functional requirements:
-

Title

Description

System Customization.

User of the CyberGIS system will have
private
domain
s
.
So the users should be able
to customize these
domains as they want by
defining data within it.


Provide Map Information.

CyberGIS system should provide

basic map
information as map details, marker details.

Live and Updated Information.

CyberGIS system should
display

live data
feed by the domain
users and mobile
operatives as well as updates from map data
providers.

Stati
sti
cs and Historical Data Analysis.

CyberGIS system should support statistical
analysis of stored data in the domain
databases.

Data Archival and Retention.

Data input by the d
omain users as well as
mobile operatives should be stored within the
domain databases. Also transaction history
should keep in the DB.

User Profiles, Roles and Privileges.

Domain user should be divided into several
access levels on their roles and
privilege.
These access levels should be authenticated in
order to access to the system.

Reporting
.

CyberGIS system should support generation
of reports based on stored data in the domain
databases.

Mobile Operative Command

CyberGIS system should be capa
ble of
communicating with mobile operative using
CyberGIS mobile component via internet
.

5



Table 3.
1


Functional Requirements

Non Functional Requirements:
-


Non functional requirements are discussed under following categories. Please
refer
CyberGIS

System Requirements Sp
ecification document.



Performance and Load Requirements.



Compatibility Requirements.



External Interface Requirements.



User Interfaces Requirements.



Communications Interfaces Requirements.



Security and Authentication requirements.



Quality Assurance
Requirements



Development Requirements.



Deployment Requirements



Special Documentation Requirements



Applicable Standards Requirements.



Usability Requirements.



This includes sending messages with map
data to the operatives as well as gets
feedbacks from them.

Real
-
time Operative Tracking
.

CyberGIS system should be capable of

tracking mobile operatives using built
-
in GPS
devices on their mobiles.


6


3.
3

Main Components and Flow



The work flow of the CyberGIS system i
s illustrated in the following

F
igure

3.
1
.
According to that
there are main two components of the system.

1.

Main console.

2.

Mobile Device.



The main console will get the map data by an existing map data provider like Google
Maps. Those map data are displayed on the main console. Users can add customized
domain markers on the map by specifying marker details. Those markers represent
some domain

entity or fact and marker data are saved on a database.

So users can view saved markers on the map, manipulate marker details
, generate

historic trend
reports and
pattern
analysis using stored data.




There are registered domain operatives with the system and as they login with their
mobile devices main console users can retrieve
details of those operatives on the main
map. This also allows the users to send messages to a selected operative via web with

map instructions. So operatives can view those messages and send response
feedbacks to main console that can be view by the users.





Figure
3.
1



CyberGIS
System


GIS Map
provider

Main
Console

Mobile
Device

GPS Device

User

Operative

DB

WEB


7


3.
4

Project Plan

and Approach

The project approach
is

based on the agile methodology and MSF (Microsoft
Framework) and
it

allow
s

requirement, environment and technological changes to reflect
within product releases.

CyberGIS

is

developed using the various tools
chose

by us and we consider free and open
source
software

and tools. These tools include Eclipse

and NetBeans

IDE
s

for
development,
Tomcat

server technology for deployment, MySQL for DB deployment and
various 3
rd

party java tools, plug
-
ins and web services as required. Also JAVA
and JSF
with Primefaces API are

used as the programming
technologies
. Then Google Map API
and services
are

used for GIS manipulation. Also SVN
is

used for release management
and version
control. The

project team

consists of 3 members with initial roles but all
were

working on each role as required
.

Project plan consists all the project activiti
es, schedule and deliverables of the project.
Project activities are basically encapsulated as project deliverables and delivered in
several phases. Also project plan is subdivided into several sub plans for each category.

More details on this topic can be

found
in

CyberGIS Master Project Plan document.



Development Plan.



Test Plan.



Communication plan.



Deployment plan.



Training plan.



Support plan.



Purchasing & Facilities Plan.



Budget plan.




8


Code

Deliverable

Phase

CG1.1.1

Vision document

Envision

CG1.1.2

Project structure document

‘’

CG1.1.3

Milestone review report

‘’

CG1.1.4

Current state infrastructure assessment

‘’

CG1.2.1

Master project plan

Plan

CG1.2.2

Functional specification

‘’

CG1.2.3

Deployment plan

‘’

CG1.2.4

Feature proposal

‘’

CG1.2.5

Test plan

‘’

CG1.2.6

Test specification

‘’

CG1.3.1

Develop internal releases

Build

CG1.3.2

User manual

‘’

CG1.3.3

Traceability Audit document

‘’

CG1.4.1

Functional testing

Stabilize

CG1.4.2

UI stabilizing

‘’

CG1.4.3

System testing

‘’

CG1.4.4

Pre
-
production testing

‘’

CG1.4.5

Release candidates

‘’

CG1.4.6

User acceptance testing

‘’

CG1.4.7

Testing and Bug Report

‘’

CG1.5.1

Project Close
-
Out Report

Close out

CG1.5.2

Post Project Analysis document

‘’

Table 3.
2



Project
Deliverable
s





9


Code

Deliverable

Planned
(hr.)

Actual
(hr.)

Variance
(hr.)

CG1.1.1

Vision document

5

6

+
1

CG1.1.2

Project structure document

15

13

-
2

CG1.1.3

Milestone review report

5

6

+1

CG1.2.1

Master project plan

15

14

-
1

CG1.2.2

Functional specification

120

100

-
20

CG1.2.3

Deployment plan

10

8

-
2

CG1.2.
4

Test plan

5

4

-
1

CG1.2.
5

Test specification

40

44

+4

CG1.3.1

Develop internal releases

520

535

+15

CG1.3.
2

Traceability Audit document

15

13

-
2

CG1.4.1

Functional testing

40

43

+3

CG1.4.2

UI stabilizing

30

38

+8

CG1.4.3

System testing

40

29

-
11

CG1.4.6

User acceptance testing

5

3

-
2

CG1.4.7

Testing and Bug Report

20

16

-
4

CG1.5.1

Project Close
-
Out Report

10

31

+21

Totals

895

903

+8

Table 3.
3



Actual vs. Planned








10


CHAPTER 04

DESIGN OF SOFTWARE


Figure
4.1



General Architecture

When

designing the CyberGIS System we’ve decided to choose the spring framework as
our base enterprise we framework for building our business logic on. Other than spring
we will be using the Java Persistence API (JPA) and Oracle (toplink) ORM for database
acce
ss and database manipulation. For the mobile operative end user component of the
CyberGIS system we’ve used the Java J2ME technology.




11


CHAPTER 05

FABRICATION OF
SOFTWARE

For the development of the software we’ve used java as the core development languag
e.
All the components & technology frameworks used are mainly core java based
implementations. The UI design framework used: “PrimeFaces”
(
http://www.primefaces.org/
) is mainly based on Java,

JQuery & AJAX Design
frameworks.

When writing the software the 03 main software components of the system was
developed using two main integrated software development environments. They
are:

i. Netbeans (with Sun Java WTK 3.0 Integrated for J2ME).

ii. MyEclipse.

For developing
& maintaining the system database we’ve used the
MySQL

database
server and the
MySQL

GUI
tools for administrating the system database backend. The
application is hosted in the Tomcat 7.0.12 application server,

which was embedded with
the ActiveMQ 5.5.x fo
r the system related enterprise message queuing (JMS
)
functionality
.




12


CHAPTER 06

TESTING AND IMPLEMENTATION

The objective
of testing the system is to assure that the system meets the full
requirements, including
non
-
functional requirements.

To accomplish the above goal we
have carried out the Unit testing, System Testing, Regression Testing, Performance
Testing, Compatibility Testing and Security Testing.

Unit testing was carried out for each component in the CyberGIS GUI application and
Mob
ile Client Application and for each service module in the web service. After
integrating the above there core modules of the application integration testing (System
Testing) was done to test the integrated system functionality. Every time when we make
bug
fix we did the regression testing to all the system components. Those are related to
the testing of functional requirements of the application.

Performance testing, Compatibility Testing and Security testing are carried out to test all
other non
-
functional

requirements of the application.

Test cases are written and executed manually for the GUI and Mobile applications and
automated test cases are used to test the service module. As results of the testing phase
we generated the Test Case documents with the
results and identified bugs.

Implementation of the system mainly focuses on database implementation and
application implementation. We used MySQL server as our database engine. So we need
to implement the database in either the application server or a sep
arate server.
Application server needs tomcat server service to implement the Cyber GIS application.
For the mobile clients we provide a separate executable .jar file to install in to the mobile
device which may implement the CyberGIS application in the de
vices. When the tomcat
server which contains the application and web service started, Users are imposed to the
CyberGIS application. They can access the application console through any web browser
through a provided URL.
(
i.e
. http
:// 127.0.0.1:8080/gis
-
app/
)




13


CHAPTER 07

RESULTS

As the results we include the test results here.

In all the test cases conducted through the testing phase about 85% are succeeded and
only 15% of the tests come up with bugs. Expected results of the test cases are appeared
as the actual results. So the status of the test is ‘Pass’. Out of the 15% of the

bugs we
have immediately fixed 80% (12% of bugs) of bugs which are related to functional and
performance indices of the application. We are more focused on test results which are in
‘Fail’ status with having high test priority when resolving the bugs imme
diately. The
remaining 20% we need to address as future works since those are currently not affected
to the system performance.

At the end we completed all Unit testing, System Testing, Regression Testing,
Performance Testing, Compatibility Testing and Se
curity Testing with having 97%
success. With the test results we can come to a conclusion that system’s functional and
non functional requirements are addressed properly.




14


CHAPTER 08

CONCLUSION AND FUTURE WORK

8.1 CyberGIS GUI Module.

The following featu
res and functionalities have been identified as future works under the
CyberGIS GUI module.



Marker Proximity Ruler and Alerter :
-

By the "Ruler" feature CyberGIS main console users will be able to measure the
distance to each marker (including mobile mark
ers) from a specified central origin
point. So CyberGIS main console users will be able to specify the central point and
get updated proximity measurement according to that. By the "Alerter" feature
CyberGIS main console users will be able to view the deta
ils of markers, within a
specified proximity circle from a specified central origin point. Both these features
will work as a single unit.



Automatic Real Time Operative Tracking :
-

Currently operative tracking is not fully automated and the CyberGIS main
console
users have to refresh the operative location in order to get the update location. By this
proposed feature operative tracking will be fully automated and updated locations
will be refreshed on the CyberGIS main console map in a specified time inter
vals.



Hardware Sensor Based Real Time Telemetry :
-

By this functionality it is proposed to gather various data required by domain users
through hardware sensors, attached to CyberGIS Mobile component and send them to
the CyberGIS main console for real time

monitoring. So the CyberGIS GUI module
will
include a
dashboard component in order to support this feature.




15


8.2 CyberGIS Mobile Component.

In the future the system is expended to be expanded by porting the J2ME client software
to newly available high
end mobile phone operating systems like: Android & iPhone.
Currently it supports all Symbian OS based mobile phones like S40 6
th

Edition & S60 3
rd

Edition Phones. Other than this we wish to expand the service end by adding a
dashboar
d for live monitoring

services
where the user will be able to monitor live
statistics about the current functionality of the system.

8.3 CyberGIS Service Module.

As a conclusion we can say that, CyberGIS Service Module maintains the connectivity
between Cyber GIS application and database. All user requests and operations are
addressed through service methods provided in this module.

Code optimization and further e
xpansions of the available services can be done as the
future works. The objective of this is to reduce the resources usage by the application
during the execution. More code level validations can be implemented to provide
additional security to the system
.

We are focusing to make the system available with live statistics with the use of service
module improvements
.



16


CHAPTER 09

PROJECT CONTRIBUTIONS

9.1

Project Contribution
by:

M.S.R Perera <209087374>

As the architect of the entire project I’ve contributed to the CyberGIS project in doing the
following:

1.

Using the business scenarios /requirements given by Roshan (The person pl
aying
the project
manager role
) come up with a suitable architecture for the en
tire
system.

2.

Decide a suitable Java Based Technology stack for the
C
yber
GIS

system.

3.

Create the initial 03 projects using the decided technology stacks by
configurations and ensure the Spring based web flow between the initially created
03 projects. (
i.e.
: As the project is distributed system with 03 modules to make
sure
the request

response flow works correctly via RMI &
Web service

interfaces
between the modules)

4.

Contributed in designing and implementing the CyberGIS Mobile Client Software
from ground up
.

5.

Contributed in designing and implementing the GUI parts related to sending
CyberGIS
operative messages and receiving responses.

6.

Contributed in writing all the Web Service Methods and exposing them via
correct document + literal s
t
y
l
e web services to be c
alled by the mobile client.

7.

Provided Technical support and guidance for the team members (Roshan &
Sanjeewa) in configuring the application server, implementing various business
logic related GUI/Service parts & technical advice on the used Java Related
te
chnology stack.

8.

Documented the CyberGIS project related architecture design diagrams (general
architecture,

ER
-
diagrams &
C
lass diagrams)
.



17


9.

Did Integration testing & bug fixing on all 03 modules upon various commits on
different modules by the other two te
am members & ensured that the system was
working smoothly as a whole

10.

Facilitated the stream line distributed development process by creating the project
in the
G
oogle
SVN

and providing software and support for the team to work with
the SVN.

11.

Prepared necess
ary project documents under the software architect role for each
milestone
.

9.2
Contribution

by:

D.S Kulasuriya<709087412>

I have contributed to the CyberGIS project as the QA lead for my main role in the project
and as a developer in following areas.

1.

Contributed to develop the Login, password resetting and User Administration
parts of the CyberGIS GUI module.

2.

Design and implement the changes done to the basic database according to the
Project Architecture’s requests and generate RMI objects to which ar
e used to
maintain the communication between Web Service and other modules.

3.

Implement the service methods according to the requests of the GUI and Mobile
Client developers. Services are developed on demand
separately
to access the
database and feed or retr
ieve data according to the user
request

or operation.

4.

Implement test cases to unit test each service methods to verify the operation
results before releasing the service method for use by developers.

5.

Improve the session tracking mechanism developed by
Shehan, to maintain user
login and domain details. Use the same session tracking mechanism to allow
direct access the password reset component.

6.

Completed the project documents related to QA. (Test Plan, Test Specification)
Also contributed to document the
SRS document, Functional Specification and
Deployment Plan.

7.

Test all the components of the CyberGIS GUI module for unit testing, security
testing, & performance testing and includes the results as the Test Case

18


Document. All the service methods in the Cybe
rGIS Service module are gone
through unit testing before release for use.

8.

Contribute to system development
and bug fixing
activities with Project
Manager’s request.

9.3

Contribution
by:

W.M.D
.R

Jeewantha<509087436>

As the Project Manager I’ve contributed to
the CyberGIS project in doing the following:

1.

Played the Project manager role.

2.

Proposed the main concept of the CyberGIS system.

3.

Developed the vision and goals that the CyberGIS
s
ystem based on.

4.

Designed the conceptual level components and the main workflow of the
CyberGIS system and refined it with system architect’s technical opinions.

5.

Designed GUI Interfaces for both CyberGIS mobile and CyberGIS main console
(CyberGIS GUI module) components an
d fine
-
tuned the all GUI
implementations.

6.

Developed CyberGIS main console (CyberGIS GUI module) GUI framework
using JSF (Java Server Faces) with Primefaces component library.

7.

Implemented the map and marker manipulation functionalities, and reporting and
an
alysis functionalities on CyberGIS main console as Java Backing Beans and
helper classes.

8.

Developed Unit Test cases and performed unit testing for CyberGIS GUI module
class methods using JUnit.

9.

Implemented RMI Service module methods for reporting functiona
lities.

10.

Developed Test cases and performed unit testing for RMI Service module
methods for reporting functionalities using JUnit.

11.

Prepared necessary project documents under the project manager role for each
milestone.





19


APPENDIX

Appendix A


Use case
Diagrams

Appendix A1


CyberGIS Admin User Use Case Diagram



20


Appendix A2



CyberGIS
Operative

User Use Case Diagram



21


Appendix B


Class Diagrams

Appendix B1


CyberGIS Mobile Service Class Diagram






22


Appendix B2


CyberGIS Service Module Class Diagrams




23


Appendix B3


CyberGIS Service Business Logic Class Diagrams




24


Appendix C


ER Diagram


25


Appendix D

Screen Designs


Appendix D1


CyberGIS Admin Main Screen











26



Appendix D2


CyberGIS Admin Report Screen








27


Appendix D3



CyberGIS
Mobile

Login













28


Appendix D4



CyberGIS
Mobile

Main Screen









29


Appendix D5



CyberGIS
Mobile

Task List






30


Appendix D6



CyberGIS
Mobile

Task Details






31


Appendix D7



CyberGIS
Mobile

Task Notification










32


Appendix D8



CyberGIS
Mobile

Task
Status Update