2013

Kauri Dieback Disease System Proposal

Name : Alan Gabrelle Joville Cal Net ID : acal628 Student ID : 5481851 Name : Chang-hoon, Lee Net ID : lcha134 Student ID : ????????? Name : Kitt Huii,Leo Net ID : lhui972 Student ID : 5909774 Assignment : InfoSys 320 - Group Assignment 2013

Table of Contents PUT NO PAGE (ltr on)

Executive Summary ............................................................................................................... Background, Problems and Scope ........................................................................................
Components (Hardware and Software)

Use Case Diagram Overview ................................................................................................ Use Case Descriptions .......................................................................................................... Entity Relationship Diagram ................................................................................................. Wordpress based Knowledge base to support the Design .................................................... Assumptions and Design Decisions (Lightswitch) ...............................................................

MAYBE ADD THE BLEND ASSUMPTION(ltr on)

Non-functional Requirements ............................................................................................... Constraints ............................................................................................................................

2|Page

Executive Summary
Kauri dieback is a deadly fungus-like disease caused by Phytophthora Taxon Agathis (PTA) specific to New Zealand which is identified in 2008. This disease is spread through soil and water via spores. Almost thousands of infected kauri in New Zealand died. That is why we are creating an information system, aimed to fight against kauri dieback disease and possesses the potential to address similar situations. The information system created will be available to many different users (public, researcher, scientist and biosecurity officer). Information accessible will be unique based on the user type. Users authentication will be required to ensure information privacy and maintain the security of the system. The system can be access remotely via a mobile device or a local desktop depending on user needs. Public users can access background information of the kauri dieback disease and even share information such as how to prevent kauri dieback with their friends and family by simply registering as a member of the system. This is a great start to educate the public about the existence of the kauri dieback disease, its implication on the kauri tree, and ways to help prevent it from spreading. They also able to make donation to help fight against the disease. Furthermore, public who goes tracking in kauri forest can register themselves in the system to be able to view a before and after visiting the kauri forests to-do list showing recommended tasks to compete. Trackers can take or save pictures and bookmark GPS coordinates of suspected infected trees that they have come across in the forest into the system for verification by the biosecurity officers to conduct further investigation. Researchers and scientists are able to obtain information on kauri trees recorded in the system that has been infected, along with the disease symptoms to facilitate their research and investigation to develop a cure for the disease. They are also able to access the treatment information used on kauri tree to either eliminate the use ineffective drugs or mix around with the drugs to create a better cure. If there are any new findings, these findings can be stored in the system. Biosecurity officers use this system to record the findings of kauri tree during the inspection of the kauri forest. Officers are able to use a portable X-ray to scan the roots of the kauri tree to determine whether a tree is infected or not. Officers are also able to use the moisture reading scanner to determine the moisture of the tree. High moisture tree may have high risk of having kauri dieback. If an infected tree is detected, the X-ray image and the moisture reading with image of it will be stored directly in the system alongside with the GPS coordinates of the tree, tree image, picture of the symptoms (available in the system for look up to double confirm the diagnostic) for future references. Upon every forest inspection, officers are provided with tracking route (with past recorded location of the kauri tree) on maps and a before and after inspection to-do list to complete. In conclusion, this new system is designed to make use of technologies to fight against kauri dieback or any similar situations in future. The new system will be able to provide a better future for kauri trees.
3|Page

Background, Problems and Scope

Background of the current system
The current system for kauri dieback is mainly for the biosecurity officer, scientist and researcher. The main purpose of this system is to store data about kauri trees that are infected as well as findings from lab analysis. Automated code for some data is used in the system to increase the accuracy of the data.

Problems or Potential Changes on the Current System

In the new system, we have added public as one of the users because the public forms an important role to combat the kauri dieback. By having public to be a part of the system, public awareness for the disease will increase and the public can assist in reducing disease spread. For example, forests tracker can help identify infected trees which may be overlooked by the biosecurity officers. This improves early stage disease detection, which in the long run will be beneficial for kauri trees. Furthermore, public can make donation to the kauri dieback foundation to help in fighting against the disease. There is a pressing need to improve the data storage of the current system because the way that the current system stores data is confusing and hard to understand. Providing a better data storage method with the new system would be beneficial for the users ease of accessing data for future reference. The existing automated code may be fast and accurate but the users do not actually know how to obtain it. This is not always a good practice as users should know where and how does all the data come from instead of having to rely on the automated code. The new system will allow the biosecurity officers to upload the data directly to the system during inspection instead of having to enter the data collected once they have returned from the forest. Old data uploading method poses the risk of losing important data during the lag period between data collection and data upload. This improved system function will be very useful, effective and efficient for data collection. In the current system, we have noticed that there is no specified way to identify each tree from one another. This is why we have introduced the use of GPS coordinates to locate the exact position of the trees and the date of record which can be used to uniquely identify each tree in the new system.

Scope
Our designed system will mainly focuses on recording the data of infected kauri trees with the help of external mobile devices and technologies. The system also expects to improve awareness of the kauri dieback disease among the public which in turn encourages them to play a part in helping to fight against it. These are the scope that we are working on in creating a new and better system for the kauri dieback disease.

4|Page

Components of the New System

Hardware
Public Non-trackers Basic mobile device or desktop with internet access. Trackers Mobile device with camera and GPS function with internet access. Scientist and Researcher Desktop with internet access would be sufficient. Biosecurity Officer Mobile device with camera, GPS, 3g (mobile broadband) and portable X-ray and moisture reading scanner (both built into the device) function. Extra battery will be needed.

Software
The new system will work on an operating system program for more control and support for the operations needed to be executed by users. The system will use Google Map for the GPS coordination for the trees.

5|Page

Use Case Diagram Overview

6|Page

Use Case Diagram descriptions

We have chosen 2 by ranking most important use case to describe them below. The normal flow of events is based on the Microsoft Blend. USE CASE # 1 Goal in Context Trigger event Type Primary, Secondary actors Related use cases Maintain Kauri Dieback Tree Priority: High

Allow the biosecurity officer to make new record on kauri dieback tree. A biosecurity request to make a new record. External. Biosecurity Officer Researcher, Scientist Include : Maintain X-ray , Maintain GPS Coordination, Maintain Picture, Maintain Moisture Reading

Preconditions

Biosecurity officer enrolled in the system as a biosecurity officer else this cannot work because only biosecurity officer can add new record of kauri tree to the system. The new record is recorded in the system.

Success post condition Failure post condition NORMAL FLOW OF EVENTS

The new record is not recorded in the system.

Step

Action

1 2 3 4 5

Biosecurity officer request to enter a new record. Biosecurity log into the system. System display several options for biosecurity officer to choose. Biosecurity officer clicks on add new record. System display add new record interface.

7|Page

Biosecurity officer records the information about the tree into the specific columns. When biosecurity officer wants to add a new picture into the specify column, this invoked use case : Maintain Picture Biosecurity officer upload the picture. When biosecurity officer wants to add a new X-ray into the specify column, this invoked use case : Maintain X-ray Biosecurity officer upload the X-ray. When biosecurity officer wants to add a new moisture reading into the specify column, this invoked use case : Maintain Moisture Reading Biosecurity officer upload the Moisture Reading. When biosecurity officer wants to add a new GPS coordination into the specify column, this invoked use case : Maintain GPS Coordination Biosecurity officer entered the GPS coordination. Biosecurity officer clicks save. New record is made. If the user log in and does not have add new record to kauri dieback system, then the user (not biosecurity officer) does not have permission to do so.

8 9

10 11

12 13

14 15 16 Exceptions 3.1

8|Page

USE CASE # 2 Goal in Context

Develope New Cure

Priority: High

Scientist develops a new cure for kauri dieback disease and wants to add it in the system. Scientist has an idea of a new cure. External Scientist User has to be a scientist. New cure record is made.

Trigger event Type Primary, Secondary actors Related use cases Preconditions Success post condition Failure post condition NORMAL FLOW OF EVENTS

No new cure record is made.

Step

Action

1 2 3 4 5 6 7 8 Exceptions 3.1

Scientist request to make a new cure record. Scientist logs into the system. System displays several options for scientist to choose. Scientist clicks on make new cure record. System display the make new cure record interface. Scientist enters the information needed. Scientist clicks save. New cure record has been saved into the system If the user log in and does not have make new cure record, then the user (not scientist) do not have permission to do so.
9|Page

Entity Relationship Diagram (ERD)

10 | P a g e

Wordpress based Knowledge base to support the Design

All research has been done before actually doing this proposal. On the groups and individuals Wordpress, all posts record all our researches. The posts on the blog show the process of our work done for this proposal.

11 | P a g e

Assumptions and Design Decisions (Lightswitch)

Assumption on HTML Client For all the screens, only authorise user can access to certain screen and buttons. So, a log in interface will appear first of all to check for authentication. The edit and add buttons are only for user that has permission for them. Design Decisions for HTML Client and Desktop Client Authentication user and roles had been added. Limitation on HTML client Permission for view of data works very well in HTML client and desktop client but adding, deleting, editing task work better in the desktop client than html client for our lightswitch prototype.

12 | P a g e

Assumptions and Design Decisions (Microsoft Blend)

13 | P a g e

Non-functional Requirements.
Usability
The new system is easy to use. Public users just have to register themselves as a member with a few clicks. After that, they can easily obtain information needed that is all ready for sharing or for printing. Researcher and scientist can get the information they need by just clicking on the buttons or icons available on the system. Biosecurity officers are able to take picture, locate GPS coordinates of the tree, get the moisture reading of the tree and have an X-ray image of tree roots taken simply by going to respective applications that is installed on the device. All information can be recorded from the device itself to the system by clicking on the save button.

Reliability
The new system will be reliable. Maintenance will be done once a month to ensure the system works as intended. Frequent backing up of data to an off-site location will be carried out to ensure that the data is not lost permanently if anything happens to the main data storage. If any error occurs, the errors will be sent to the syst ems management to look into it and resolve.

Performance
The new system will perform much efficiently compared to the old system. However, biosecurity officers may suffer from low bandwidth when they are connecting to the system through mobile devices in the forest. This is caused by bad signal transmission from within the forest areas. This does not mean that systems performance is affected; just that data transmission may be slow at times.

Supportability
In the new system, there will be help available for the users if they encounter any problems. This allows the users to be able to continue their task even when they got stuck. Software updates will be available when needed to keep the software of the system up to date. This reduces potential bugs in the system.

Security
The new system has a high security feature because information accessible will be unique based on the user type. Users authentication will be required to access the data in the system to ensure information privacy and maintain the security of the system.

14 | P a g e

Constraints on the New System Design

One of the constraints we are facing with the new system design is the 3G (mobile broadband) function needed for biosecurity officers during the inspection of kauri tree in the forest to enable direct storing of data into the system. We are concerned that in the forest there will be limited 3G coverage which may affect the actual functionality of the system. Another constraint is battery power supply. We are concerned about the battery life on the devices used by biosecurity officers. Since the officers will have to operate functions on the device that is rather power consuming, this is quite a concern as most mobile batteries can only last up to a few hours. However, this can be solved by using portable power bank to recharge the battery if required. Implementing the portable X-ray and moisture reading scanner function into the mobile devices for biosecurity officers are a new challenge. There are portable X-rays and moisture reading scanner available in the market right now, but not portable X-rays and moisture reading scanner designed to work on mobile devices. So, we are concerned whether this will ultimately work out as expected or not. GPS service on mobile device may fail users sometimes if the satellite signal could not reach the mobile device. Especially within forest areas, where tall growing trees may disrupt signal transmission. This might happen but not very often, so we are just a little concerned about this constraint.

15 | P a g e