CANRI Project Plan 2001-2002: Project # 04DIY Manual

CANRI Project Plans 2001-2002

Return to: [Summaries] [Brief List] [Project Plan Guidelines] [Project Roles]

Project # 04DIY Manual

Go to: [Schedule & Costs] [Deliverables] [Organisational Chart]

1 DOCUMENT CONTROL

2 SHORT NAME OR ACRONYM

3 ABSTRACT

4 TARGET AUDIENCE

5 PARTICIPATING ORGANISATIONS

6 CONTACTS

7 PROJECT DEFINITION

8 DELIVERABLES

9 SCHEDULE AND COSTS

10 PROJECT ORGANISATION AND CONTROLS

11 OTHER INFORMATION

12 EXECUTIVE SIGNOFF

[Back to top]

1 DOCUMENT CONTROL

1.1 Revision History

Version

Revision Date

Summary of Changes

1 27/08/2001 Incorporate input from EoIs and meeting held 23/8/01.

2 28/08/2001 Add schedule & costs. Revise Deliverables and Interdependencies.

1.2 Distribution

This document has been distributed to:

Name

Position

Version

Date Issued

Daniel Large Manager Environmental Information & Statistics, EPA 1 27/08/2001

William Leader CANRI Project Officer 1 27/08/2001

Wim Brinkhof Snr Internet Integrator, DLWC 1 27/08/2001

1.3 Approvals

This document requires the following approvals:

Role

Name

Position

Approved (Initials)

Date Approved

Version Approved

Project Manager William Leader CANRI Project Officer

Senior User Daniel Large Manager Environmental Information & Statistics, EPA

Senior Supplier Wim Brinkhof Snr Internet Integrator, DLWC

[Back to top]

2 Short name or acronym
DIY Manual
3 Abstract

High-quality documentation explaining how to contribute data to CANRI and use CANRI resources in your own website.

[Back to top]

4 Target audience

Primary audience:
Local government

Secondary audience:

State government
Commonwealth government
Students/academics
Environment/community groups
Industry

Main regional audience:

All of NSW

Other comments:

The documentation will be targeted mainly at people performing three roles, as described below.

Role

Example

IT Skills

Wants to

Data custodian

Council environment officer

MS Excel, MS Access

See his/her data on a web map

Web programmer/ developer

Steve Hayes, Ian van der Poel

Web scripting eg PHP, ASP, JSP, JS

Use components to incorporate maps in his/her web application

Web content person

Tim Pullen (EPA web coordinator)

FrontPage, Dreamweaver, HTML coding

See a map in his/her webpage, showing data from own organisation over a base map

[Back to top]

5 Participating organisations

5.1 Lead agency or organisation

Organisation: Department of Land and Water Conservation
Postal address: GPO Box 39 Sydney NSW 2001
Web site: http://www.dlwc.nsw.gov.au

5.2 Other agencies or organisations

Organisation: (none)
Role:
Contact:

Organisation:
Role:
Contact:

Organisation:
Role:
Contact:

Organisation:
Role:
Contact:

[Back to top]

6 Contacts

Author

Name: Jonathan Doig
Position: CANRI Program Director
Phone: 9228 6278
Fax: 9228 6433
Email: jdoig@canri.nsw.gov.au
Organisation: Department of Land and Water Conservation

Project manager

Name: William Leader
Position: CANRI Project Officer
Phone: 9895 7296
Fax: 9895 7834
Email: wleader@canri.nsw.gov.au
Organisation: Department of Land and Water Conservation

Project Steering Committee

Project sponsor

Name: Jonathan Doig
Position: CANRI Program Director
Phone: 9228 6278
Fax: 9228 6433
Email: jdoig@canri.nsw.gov.au
Organisation: Department of Land and Water Conservation

Senior supplier

Name: Wim Brinkhof
Position: Snr Internet Integrator
Phone: 9895 6193
Fax: 9895 7834
Email: wbrinkhof@dlwc.nsw.gov.au
Organisation: Department of Land and Water Conservation

Senior user

Name: Daniel Large
Position: Manager Environmental Information and Statistics
Phone: 9995 5849
Fax:
Email: larged@epa.nsw.gov.au
organisation: Environment Protection Authority

[Back to top]

7 Project definition

7.1 Project description and objectives

Although CANRI has expanded through the progress of funded projects during 2000-2001, the expected expansion in the number of datasets served has not yet eventuated. On the other hand, the CANRI technical workshop held in June 2001 was very well-attended, indicating considerable interest in contributing to the CANRI framework. Feedback received suggests that one reason this interest is not being translated into increased data on the CANRI framework is the lack of technical documentation explaining how to do so. There has been an attempt to redress this with documentation developed in June 2001, however insufficient effort went into this documentation and it is still inadequate.

This project will address this problem with documentation aimed at three different roles able to contribute to CANRI: custodians of natural resources data; website content managers; and web developers/programmers.

7.2 Inclusions and exclusions

Includes documentation of systems to be developed during 2001-2002.

Excludes any new software development, other than possibly software to run a tutorial, demonstration or online help.

Excludes end-user documentation for applications. It is the responsibility of application developers and managers to provide any user documentation needed.

7.3 Related initiatives and interdependencies

This plan assumes a number of deliverables will be developed by the Vector Plus, Catalog Plus, Partner Plus and open Apps projects. However, if any of these deliverables are not forthcoming, it will simply reduce the scope of operations documented in this project.

Project

Deliverable

Vector Plus

WMS- or WFS-compliant data servers including DSLite.

Catalog Plus

Online user interface for ANZLIC metadata entry.

User interface to discover connection details for WMS- or WFS-compliant data servers.

Ability to register a non-spatial web resource in the CANRI catalog.

Open Apps

Ability to call applications with an initial map extent and layers specified in the URL.

Partner Plus

Ability to upload a point flat-table dataset to a centrally-hosted CANRI data server and enter a metadata record for it.

7.4 Technological environment

May be integrated with use case documentation in the UML model managed in Rational AnalystStudio. Could incorporate Web-based bug-tracking and enhancement requests using Rational ClearQuest Web.

7.5 Prerequisites and assumptions

Simple Generic User Interface is completed by early October 2001.

[Back to top]

8 Deliverables

8.1 Details of deliverables

Click here to see list of deliverables in pdf format.

8.2 Environmental theme

Air (atmosphere)
Not applicable

8.3 Type of deliverables

Other
Documentation.

8.4 Additional information

The documentation will include:

Intended audience, which differs for different parts of the documentation (see target audience above)

Overview of what CANRI is for, and its place with respect to whole-of-government IT infrastructure

Overview of the CANRI technical framework

Description of architectural components

"How to" guides for a number of use cases

Other sources of information
Use cases include:
Metadata

create a metadata record;

edit and delete a metadata record.
Data serving

establish a free vector GIS data server – (install and) configure MapServ on the web, register it and serve to the Natural Resources Atlas;

create and register a data layer in an existing DSLite or MapServ installation;

edit (update, restructure) and remove a data layer in an existing DSLite or MapServ installation;

upload a point flat-table dataset to a centrally-hosted CANRI data server and enter a metadata record for it¹;

establish a free point data server – wrap OGC-compliant DSLite on an existing database on the web, register it and serve to the Natural Resources Atlas¹;

contact a commercial software supplier to establish a vector GIS data server;

register a commercial GIS/database data server in the CANRI catalog;

register a non-spatial web resource in the CANRI catalog¹.
Applications

save a map image locally and use it as a static GIF in one’s own web page;

link from one's own web page to a saved session in a CANRI application;

link from one's own web page to a CANRI application with a URL specifying the map extent and layers¹;

use an <img> tag to link to an image created on-the-fly by a CANRI application²;

call a CANRI JavaScript application from one’s own web page using a page-serving technology (ASP, JSP, PHP, CFM, etc)²;

create a new application using the CANRI application builder;

discover and use OGC-compliant CANRI data servers in one’s own application¹.
^{1Requires additional development under Vector Plus, Catalog Plus or Partner Plus projects as described in Section 7.3 Related initiatives and interdependencies above.
^{2Feasibility to be checked.}}
[Back to top]

9 Schedule and costs

9.1 Schedule and cost details

Click here to see project schedule and costs in pdf format.

9.2 Additional information

[Back to top]

10 Project organisation and controls

10.1 Organisation Chart

Click here to see organisation chart in pdf format.

10.2 Risk

Project or business risk

Proposed response

Technology won’t stay still long enough to be documented. Require developers of enhancements to document their own work to a set standard.

Can’t find contractor with required skills and knowledge. Establish a working group to bring the required skills/knowledge together.

Exploring documentation requirements may uncover need for additional software development not resourced. Provide stop-gap documentation for this area and specify required software for development in next financial year.

10.3 Quality management
Progress reports will be provided to the CANRI coordination team every two months or otherwise as required. A representative of the lead agency or organisation will attend CANRI Program Implementation Group meetings to discuss progress on the project.
Other quality management measures to be adopted:
Will investigate use of Rational AnalystStudio software to manage documentation.

[Back to top]

11 Other information

[Back to top]

12 Executive signoff

The Project and its outcomes are consistent with the business policies and strategies of this organisation as its sponsor. Resources are available to adequately supplement those provided by CANRI funding for the substantial delivery of expected project outcomes and for the realisation of described benefits.

This project plan has been prepared in accordance with the 2001/02 CANRI Project Plan guidelines

Signature:

Name:

Jonathan Doig

Position:

CANRI Program Director

Date:

[Back to top]

Return to: [Summaries] [Brief List] [Project Plan Guidelines] [Project Roles]