Project Name	Virtual Ledger Project, Phase 2
Project Manager	vacant

Money, money, money, aahh, could be funny - in a rich man's world!

Project Definition

The virtual ledger is a prominent part of the open contract we have between us as a Society and us as individual members. It will detail every single financial transaction and will be available to any member. There will be 3 sets of users for this system and they will require different sets of functions and utilities. Please remember that this is only a phase 2 project and as such will only provide the next level of minimum functionality. Further projects will be expected to significantly enhance this sub-system.

Treasurer - The treasurer will require a suite of data entry functions to allow him/her to enter transactions, open and close ledgers. Remember that no transaction can be changed or deleted - there will be a full audit trail, and if a mistake is made, a second transaction must be entered to correct the mistake.
Auditor - Each ledger sheet has to be audited and this is done by someone other than the treasurer. This function only allows audit data to be entered in the control block of each sheet.
Members - A suite of functions to allow them to see multiple sheets, move backwards and forwards,maybe some statistical functions.

It will be up to the project manager to add to and refine this Project Definition by consulting with each of the three groups above. This is a phase 2 project however and the most important part is to get a form based entry system up and running as quickly as possible.

A separate security project has been defined. Until it is in place, this project should provide data entry security via its own security/password authentication script.

Team member list

Not currently assigned.

Logical Design Specification

Not yet done.

Physical Implementation

To complement the long term strategy of moving to a Content Repository, the data should be kept separate and the HTML pages should be assembled dynamically. Be aware also that in accordance with our multi-language requirements, all data stored as text will require dynamic size storing. P2 will probably not see the full language solution we need but keep an eye on the Language Project and design/code in a manner friendly to it.

Project Diary

10 April 1997

Project spec completed.