CP5046 Project October 16, 2008 SAL-I - Cycle Report

unalaskaweepingInternet and Web Development

Jul 19, 2012 (5 years and 3 months ago)

284 views

CP5046 Project
October 16, 2008
SAL-I - Cycle Report
Scott Messner, Xu Du, Jörg Seifert, Marc Hammerton
Project Overview
The SAL-I Project Team has been working to produce a graphical interface to SAL. The SAL Interface

(SAL-I) will provide permitted users
with
an easily accessible, and easy to use web interface to sensor

networks connected to the SAL system. The hope is to provide good representation of data retrieved

from unique sensors connected to the SAL network. This will include textual, video, and audio data.
Document Scope
This document will summarize the current progress of the SAL-I project over the past 9 weeks. It will

discuss what portions of the system have been implemented, what has been done to mitigate previously

determined risks,
what progress has yet been made
, and what are the remaining risks involved.
Progress Summary
Progress on the SAL-I system has been steady on both front and back-end. We have established an

Apache Geronimo application server. Java EE Beans is being used for providing the back-end business

logic. Currently a connection to the SAL-agent can be made, and sensor information can be retrieved.

Our current back-end prototype demonstrates the following functionalities:

Connection to the SAL-agent

Receive events from the SAL-agent

Sensor Management
o
List sensors
o
Add sensor
o
Remove sensor

Retrieval of command list for individual sensor

Execution of command for individual sensor

Display of textual sensor data
1

Retrieval of list of protocols
Google Web Toolkit (GWT) has been used to create the client-side environment. GWT has a great

number of tools to incorporate Java Servlet technology in creating a dynamic interface. We
have
used

GWT’s Remote Procedure Call (RPC) packages to send AJAX requests to our web service. The result is

interactive content without the constant refreshing of the browser page. We
have
also been

coordinating with the client (Gilles Gigan) in order to provide streaming video content. We
have
a few

demonstrations on the use of html objects to display streaming content. The current front-end

capability is as follows:

Display list of sensors

Display details of sensors

Retrieve/Display command list for individual sensor

Display of textual output for individual sensor

Display of static jpeg images
The compilation of front-end and back-end is slowly being combined to match the SAL-I system

structure demonstrated in
Figure 1
.
2
Figure
1
: SAL-I Architecture Overview
APPLICATION
SERVER
GWT
SAL AGENT
Web-UI
Web-UI
Beans
(Backend)
Beans
(Backend)
GWT
Servlet
(frontend)
GWT
Servlet
(frontend)
GWT
Servlet
(frontend)
Connection to SAL Agent:

data transfer, exception
handling, provides Servlets easy
interfaces to access SAL
Interface for web gui:

bridge between UI and backend
(part of GWT), prepares data
for UI
Interface for user:

displays data, receives
user commands
Risk Analysis
So far, the SAL-I project team has done considerably well at managing project risks. There are however,

some persisting risks as well as some newly identified ones. The
blue part in Table 1
below summarizes

the well-managed risks. The red part in Table 1 following addresses the continuing risks and the

appearance of new risks ranked by severity.
Managed Risks
Action Taken
Choosing the wrong web API
We have researched the capabilities of the Google Web

Toolkit to ensure it is appropriate for our use. The

provided libraries have also greatly improved the speed

at which we are able to produce the interface.
Insufficient team cooperation and

communication
Communication via email has allowed us to stay

connected as a team even though we are not regularly

able to meet as an entire group. We’ve also found a way

to split up project responsibilities so there are minimal

conflicts during implementation.
Clients request for added features
As of now, our client has not requested many changes.

This is due to the effective communication by both the

project team and the client on what is considered

feasible in the development of SAL-I.
Malicious users of SAL-I exploit the system
The SAL-I server has been decided to be kept within the

JCU network. This means the security offered is as good

as that provided through the campus network.
Establishment of LINUX environment takes

longer than expected
Having project member with previous experience with

LINUX allowed for the installation and setup of Ubuntu

and the necessary resources with no major problems.
Remaining Risks
Countermeasures
Cannot finish the project within time

limitation (November 30
th
)
With the projected completion quickly approaching it

will take the dedication of all SAL-I team members to

invest an extra amount of time and effort that may have

been lost in past weeks.
The implementation of streaming jpeg data

via GWT (javascript) could slow down the

performance of the GUI
Finding the appropriate balance between image quality

and GUI performance will be important. Prototypes will

be created to test the effects of providing specific

quality image streams.
System may lose flexibility as more devices

are added
Providing the flexibility for new devices seems to be

mostly dependent on the addition of protocols. As long

as we are able to provide an effective way to manage

device protocols we will be able to eliminate this risk.
Table
1
: Risks
3
Agenda
Within the next two weeks we hope to achieve the following milestones. There are a large number of

requirements still needed to be accomplished, but it will be important to prioritize the following agenda

over other requirements. A new agenda will be created within the next two weeks.

Add/Remove sensors on front-end

Management of sensor protocols on both back-end and front-end
o
List of current protocols
o
Add/Remove protocols

Added jpeg support
o
Display of static images
o
Streaming video capability
SAL-I User Interface Prototype
Figure 2 is a snapshot of the current look and feel and capabilities of the SAL-I user interface. The

displayed data is test data and not representative.
4
Figure 2: SAL-I - User Interface Prototype