I-MAN Information Manager



	Mailing Lists

Users

Developers

Announcements



	Who's Who

WSCC Developers

Project Partners


About the Project
	Strategy
	Project Initiation
	Project Detail
	Detailed Outcomes
	Deployment
	Review & Conclusions
	Appendices


For Developers
	SourceForge Project
	CVS
	I-Man Wiki
	Concept Diagram
	UML Diagrams

Detailed Table | Communication | Consultation
Vendor Selection | Risk Log

Project Plan

A project plan must be defined to give the project structure, and to highlight and accommodate key dependencies. Splitting the overall goals into smaller sub-projects, enabled estimates and therefore project milestones to be extrapolated. These will form the project quality plan

Detailed Table

TASK	RESOURCE
Taxonomy
Gather categories and processes (taxonomy)	Information Management Officer
Construct synonym data store	Information Management Officer
Design/planning	Information Management Officer
Collate available synonyms	Information Management Officer
Enhance management tool to allow synonyms	Developers
Data entry of synonyms into synonym store	Developers/IMO
Deliver WSCC metadata draft
Build sample reference document	Developers
Build test harness	Developers
Evaluate – link or include Dublin core	Developers
External constraints or schemas for processes/ categories	Developers
Build sample schema	Developers
Gather GIS layer	Developers
Enhance schema	Developers
Repository prototype
Design/ planning	Developers
Enhance Jena design	Developers
XML based I/O to repository	Developers
Management interface to repository
Design/ Planning	Developers
RDF Schema tool evaluation	Developers
Web site draft	Developers
Build RDBMS Tables	Developers
Configure security	Developers
Beta test web solution	Developers/All
Develop categories management GUI	Developers
Enter constraint list	Developers
Tagging interface
Add modify metadata	Developers
Query Interface
Design/planning	Developers
Evaluate search tools	Developers
Prototype own search tool	Developers
Implement search tool	Developers
Build web interface to search tool	Developers
Sub system
Verify Sub system/tagging	Developers
Data capture tool prototype (word and HTML)
Design/planning	Developers
Evaluate available filter software	Developers
Specify and prototype bespoke template solution	Developers
Beta test	Developers/All
Initial population
Scanning in leaflets	Project Support
Load 50 leaflets	Developers
Publish work for peer review
GovTalk publication	Information Management Officer
Partner feedback	Information Management Officer
Rework/redesign prompted by peer review	Developers
Publish metadata standard
Design/planning	Developers
Publish WSMDS	Developers
Provide web services
Design/planning	Developers
Web service infrastructure	Developers
Query web service	Developers
TASK	RESOURCE
Result web service	Developers
Hardware preparation
Build production server	Technical Support/Developers
Deploy to production server	Technical Support/Developers
Go live	Developers
Code wash	Developers
Acceptance testing	Developers
Post go live
Broken links tool	Developers
Data capture tools	Developers
Enhance visualisation tools	Developers
Statistics tool	Developers
Navigation tool	Developers
Project completion
Creation and sign-off of End of Project Report	Project Leader, Project Manager, Information Management Officer

Note: Due to the size of the project, a detailed project plan was key to ensure that all the deliverables were met.

Communication

As part of the plan, I-Man ensured that there was a detailed communications plan.

This was as follows:

Weekly email updates between design/development and project owner. This will allow communication of project progress changes in a timely manner.
Change control sessions via email or in a more formal meeting as soon as requirements are known to require modification
Provision of a collaboration tool, where all interested parties may contribute to the design and also find all documentation regarding the project. Lotus Quickplace was used prior to the development of our own project website

Consultation

The peer review and consultation ensured that the metadata schema conformed to government standards.

Vendor Selection

West Sussex County Council utilised existing servers to 'store' the information repository
JDO is a Java standard
The Libelis Lido tool was chosen as it also included (free of charge) Navilis which was first thought to satisfy the needs of the category graphical user interface (GUI). However, the functionality was not sufficiently complex or flexible the work was contracted out to a Java Swing specialist
RoboHelp was the best technical authoring tool available at the time within the budget parameters
Jena (a Hewlett Packard product) was selected, as it provided the best RDF modelling API. Additionally, it was free and open source to allow for future development

Risk Log

A risk log should be maintained to allow the Project Leader and other organisations involved to monitor and action them. An example of a Risk Log can be found in the Appendix.