ALEG
Stage 3 Implementation Plan

Introduction

Stage 3 of the ALEG Implementation is the development of a prototype system.

Tasks

StepTaskDescription Effort
(range)
Dates
(from - to)
Effort
(best guess)
1Database design Convert the logical design to relational database tables. 2 - 4 days 7 Aug - 11 Aug3.5 days
2Install hardware/software Install + configure hardware, operating system, database, web server, application server environment, Java,... 2 - 4 days 9 Aug - 15 Aug3.5 days
3Get basic infrastructure working JDBC, simple servlets, XML/XSL 1 - 2 days 16 Aug - 18 Aug1.5 days
4Trial AUSTLIT Data load Load the current AUSTLIT data 3 - 4 days 16 Aug - 22 Aug3 days
5Trial BAL Data load Load the current BAL data, perform some automated matching with AUSTLIT 2 - 3 days 22 Aug - 28 Aug3 days
6Design and implement basic server-side application infrastructure client communication (explicit HTML and hidden XML), security, logging, database access & update 10 - 15 days 24 Aug - 15 Sep13 days
7Design and implement basic client-side application infrastructure data maintenance UI framework, data caching, server communication, editting, basic UI design and page structure 10 - 12 days 11 Sep - 29 Sep10 days
8Implement basic agent maintenance add/edit/delete 3 - 5 days 25 Sep - 3 Oct4 days
9Implement basic topic-map/thesaurus maintenance add/edit/delete 2 - 3 days 3 Oct - 6 Oct3 days
10Implement basic work/expression/manifestation maintenance add/edit/delete 4 - 6 days 6 Oct - 13 Oct5 days
11Implement basic browsing and searching Yahoo/Open Directory style browsing and searching 5 - 8 days 13 Oct - 26 Oct6 days
12Consolidate above work, incorporate feedback Ready for Stage 3 evaluation, signoff 3 days 20 Oct - 27 Oct3 days

This timetable can be graphically represented as:


Note: the above image was taken from a simple (and naive) Gantt chart stored here at Blox.com. The spreadsheet does not allow you to represent part-time spent on a task, so the duration column in the image above is 'elapsed' not 'worked' days.

What won't be implemented

Significant tasks/functionality not included in the Stage 3 prototype:

  1. Extensive AUSTLIT/BAL data matching. Simple (obvious) automated matching will be attempted, but the effort required and possible automated/manual approaches to be persued will be an outcome of the early part of Stage 3.
  2. external holdings processing of any type
  3. Lu Rees data load
  4. EAD retrieval or maintenance
  5. update logging
  6. user management


Home > Implementation
Kent Fitch
k.fitch@adfa.edu.au
2 August 2000