Kauri Dieback Disease System Proposal

7/30/2019 Kauri Dieback Disease System Proposal

1/21

Kauri DiebackDisease System

Proposal

Name : Kitt Huii , Leo

Net ID : lhui972

Student ID : 5909774

Assignment : InfoSys 320 - Individual Assignment 2013

2013


2/21

2 | P a g e

Table of Contents

Executive Summary .............................................................................................................3

Background, Problems and Scope ......................................................................................4

Use Case Diagram Overview ..............................................................................................5

Use Case Descriptions ................................................................................................ 6 - 11

Entity Relationship Diagram for Lightswitch ...................................................................12

Entity Relationship Diagram .............................................................................................13

Wordpress based Knowledge base to support the Design ................................................14

Assumptions and Design Decisions (lightswitch) .................................................... 15 - 18

Non-functional Requirements ...........................................................................................19

Constraints ........................................................................................................................20

The End .............................................................................................................................21


3/21

3 | P a g e

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 isspread through soil and water via spores. Almost thousands of infected kauri in New

Zealand died. That is why I am 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 mobiledevice 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 familyby 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 listshowing 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 furtherinvestigation.

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 accessthe 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, thesefindings can be stored in the system.

Biosecurity officers use this system to record the findings of kauri tree during theinspection 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. If an infected tree is detected,

the X-ray image 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 todouble confirm the diagnostic) for future references. Upon every forest inspection,

officers are provided with tracking route (with past recorded location of the kauri tree) onmaps 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.


4/21

4 | P a g e

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 inthe system to increase the accuracy of the data.

Problems or Potential Changes on the Current System

In the new system, I 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 inreducing 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. Providinga 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 goodpractice 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 havereturned 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 systemfunction will be very useful, effective and efficient for data collection.

In the current system, I have noticed that there is no specified way to identify each

tree from one another. This is why I have introduced the use of GPS coordinates to locatethe exact position of the trees and the date of record which can be used to uniquely

identify each tree in the new system.

Scope

My designed system will mainly focuses on recording the data of infected kauritrees 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 I amworking on in creating a new and better system for the kauri dieback disease.


5/21

5 | P a g e

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) andportable X-ray (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 GoogleMap for the GPS coordination for the trees.


6/21

6 | P a g e

Use Case Diagram Overview


7/21

7 | P a g e

Use Case Diagram descriptions

I have chosen 3 by ranking most important use case to describe them below. The normal

flow of events is based on the next prototype not the lightswitch. I would prefer to do it

on Microsoft Blend.

USE CASE # 1 Maintain Kauri Dieback Tree Priority: High

Goal in Context Allow the biosecurity officer to make new record on kauri dieback tree.

Trigger event

Type

A biosecurity request to make a new record.

External.

Primary,

Secondary actors

Biosecurity Officer

Researcher, Scientist

Related use cases Include : Maintain X-ray , Maintain GPS Coordination, Maintain Picture

Extend : Maintain Concern

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.

Success post

condition

The new record is recorded in the system.

Failure post

condition

The new record is not recorded in the system.

NORMAL FLOW

OF EVENTSStep Action

1 Biosecurity officer request to enter a new record.

2 Biosecurity log into the system.

3 System display several options for biosecurity officer to choose.

4 Biosecurity officer clicks on add new record.

5 System display add new record interface.


8/21

8 | P a g e

6 Biosecurity officer records the information about the tree into the

specific columns.

7 When biosecurity officer wants to add a new picture into the

specify column, this invoked use case : Maintain Picture

8 Biosecurity officer upload the picture.

9 When biosecurity officer wants to add a new X-ray into the

specify column, this invoked use case : Maintain X-ray

10 Biosecurity officer upload the X-ray.

11 When biosecurity officer wants to add a new GPS coordination

into the specify column, this invoked use case : Maintain GPS

Coordination

12 Biosecurity officer entered the GPS coordination.

13 Biosecurity officer clicks save.

14 New record is made.

Exceptions 3.1 If the user log in and does not have add new record to kauri

dieback system, then the user (not biosecurity officer) does nothave permission to do so.


9/21

9 | P a g e

USE CASE # 2 Maintain Concern Priority: High

Goal in Context The tracker sends their concern about the kauri tree they encounter to the

system.

Trigger event

Type

A tracker wants to send a concern.

External

Primary,

Secondary actors

Tracker

Biosecurity Officer

Related use cases Include : Maintain GPS Coordination

Preconditions User has to be a tracker.

Success post

condition

Tracker sent his or her concern to the system.

Failure post

condition

Tracker unable to send his or her concern to the system.

NORMAL FLOW

OF EVENTSStep Action

1 Tracker request to send a concern(s).

2 Tracker logs into the system.

3 System displays the several options for tracker to choose.

4 Tracker clicks on make a concern message.

5 System displays the selected interface.

6 Tracker enters the information into the specific columns.

7 When biosecurity officer wants to add a new GPS coordination

into the specify column, this invoked use case : Maintain GPS

Coordination


10/21

10 | P a g e

8 Tracker entered the GPS coordination.

9 Tracker clicks send.

10 The message has been sent.

Exceptions 3.1 If the user log in and does not have send concern, then the user(not tracker) do not have permission to do so.


11/21

11 | P a g e

USE CASE # 3 Develope New Cure Priority: High

Goal in Context Scientist develops a new cure for kauri dieback disease and wants to add

it in the system.

Trigger event

Type

Scientist has an idea of a new cure.

External

Primary,

Secondary actors

Scientist

-

Related use cases -

Preconditions User has to be a scientist.

Success postcondition

New cure record is made.

Failure post

conditionNo new cure record is made.

NORMAL

FLOW OF

EVENTS

Step Action

1 Scientist request to make a new cure record.

2 Scientist logs into the system.

3 System displays several options for scientist to choose.

4 Scientist clicks on make new cure record.

5 System display the make new cure record interface.

6 Scientist enters the information needed.

7 Scientist clicks save.

8 New cure record has been saved into the system

Exceptions 3.1 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.


12/21

12 | P a g e

Entity Relationship Diagram (ERD) for Lightswitch

Made the ERD below suitable or easier for the building of Lightswitch. User canbe model in different ways like User (People)Biosecurity Officer, Scientist, Researcher,

Public, Tracker and Manager. I did not do it that way because it would be very confusing

in the Lightswitch development.


13/21

13 | P a g e

Entity Relationship Diagram (ERD)

This is the ERD where I use the Anybody structure for the user. This is not done

in lightswitch as it will get all complicated with the screen display.


14/21

14 | P a g e

Wordpress based Knowledge base to support the Design

All research has been done before actually doing this proposal. On Wordpress,previous post (Second post) records all my researches. There are some notes in the post

saying what I have achieved from the web links that I visited. Those references really

helped me a lot for this proposal.


15/21

15 | 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.

Desktop Client

Authentication user and roles had been added.

Below are a few screenshot of HTML Client interface and a little description:

I am going to demonstrate one of the users for this prototype here. The role I am choosing

is Biosecurity Officer.

This is the home page when the prototype opens up. As you can see, you can

click on the show view user to see information about the user and their corresponding

information about them.


16/21

16 | P a g e

When you click on one of the KauriTree above, you will get the information

about it and the corresponding information (in tabs) that are related to the tree.

When you click on the User tab, you will see the information of the person who

recorded this tree. You can click on it to see his tracking route that the user took.


17/21

17 | P a g e

This is the tracking route, I am taking about above. Biosecurity officer can add or

edit this information.

This screen appears when user clicks the show view user button on the

homepage. User can search for the users role to see their information.


18/21

18 | P a g e

When the biosecurity officer clicks on his or her profile, user can edit his or her

details or add any other information that he or she are allowed to. For this example,biosecurity officer can only add or edit tracking route.

Conclusion, other users have different accessibility to the tabs, buttons and screenfor security purpose for the system. Above is my small demonstration on how my system

works with one of the user.


19/21

19 | 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 officersare able to take picture, locate GPS coordinates 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 thesave 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 locationwill 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 systemsmanagement 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 gotstuck. 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 beunique 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.


20/21

20 | P a g e

Constraints on the New System Design

One of the constraints I am 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. I am concerned thatin the forest there will be limited 3G coverage which may affect the actual functionality

of the system.

Another constraint is battery power supply. I am 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 usingportable power bank to recharge the battery if required.

Implementing the portable X-ray function into the mobile devices for biosecurity

officers is a new challenge. There are portable X-rays available in the market right now,but not portable X-rays designed to work on mobile devices. So, I am 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 I am justa little concerned about this constraint.


21/21

THE END.

Kauri Dieback Disease System Proposal

Documents

Transcript of Kauri Dieback Disease System Proposal