--- projects/cms/documentation/plan/time_allocation.txt	2000/10/26 08:25:09	1.1
+++ projects/cms/documentation/plan/time_allocation.txt	2000/10/30 14:04:59	1.2
@@ -1,47 +1,121 @@
-Estimated time allocation
-=========================
-
-pjm2, 23/10/2000
-
-
-Combined efforts in hours: -
-
-
-Management and Admin tasks (200 total)
-    webpages (10)
-    cvs (10)
-    meetings/minutes/meetings with iau (180)
-
-Requirements, analysis, specification (85 total)
-    Find out what the reqs are (5)
-    look at other systems (30)
-    Analysing our own ideas (40)
-    produce spec (10)
-
-Design (200 total)
-    UML (25)
-    Interface design (20)
-    Protocol design (30)
-    Server design (40)
-    GUI/Client design (20)
-    Host design (10)
-    Web interface design (35)
-    DB infrastructure (20)
-
-Implempentation (300 total)
-    Phase 1 (15)
-    Phase 2 (45)
-    Phase 3 (45)
-    Phase 4 (30)
-    Phase 5 (115)
-    Further developments of public release (50)
-
-QA, QC, Testing (195 total)
-    Doc specs (5)
-    Coding specs (10)
-    Testing each of the modules (180)
-
-Documentation (150 total)
-    User docs (40)
-    Maintenance docs (60)
-    Internal docs (50)
+Estimated time allocation
+=========================
+
+pjm2, 23/10/2000
+tdb1, 30/10/2000
+
+Combined efforts in hours, with description of sections and 
+names against each section.
+
+It should be noted that this is a plan, and there are many 
+circumstances that could affect how closely we follow this. 
+There will, of course, be a review at the end of the 
+project.
+
+
+Management and Admin tasks (200 total)
+    webpages (10)
+      Maintaining and updating the website.
+      - pjm2 (others contribute 50%)
+    cvs (10)
+      Setting up, managing and maintaining the CVS 
+      repository and related facilities. Also assisting in 
+      the use of CVS.
+      - tdb1 (others contribute 50%)
+    meetings/minutes/meetings with iau (180)
+      Attending regular meetings, both as a group and with 
+      iau. Also taking of minutes and planning each meeting 
+      in advance.
+      - all members
+
+Requirements, analysis, specification (85 total)
+    Find out what the reqs are (5)
+      Find out exactly what the system needs to do, 
+      including meeting with jc.
+      - all members
+    look at other systems (30)
+      Research into simliar products with the intention of 
+      seeing how our proposed idea compares.
+      - ajm4 & ab11
+    Analysing our own ideas (40)
+      Looking at the merits/weaknesses of our ideas, and 
+      helping to improve them.
+      - all members
+    produce spec (10)
+      Generating a relatively detailed specification of the 
+      overall system.
+      - tdb1 & pjm2
+
+Design (200 total)
+    UML (25)
+      Producing UML designs for the various parts of the 
+      system.
+      - ajm4
+    Interface design (20)
+      Specifying the interfaces for communication between 
+      the various parts of the system.
+      - pjm2 & ab11
+    Protocol design (30)
+      Specifying the protocol in detail.
+      - pjm2 & ab11
+    Server design (40)
+      Designing the server and how the components plug 
+      together and interact.
+      - tdb1 & ajm4
+    GUI/Client design (20)
+      Designing the GUI/Client side of the system.
+      - pjm2 & ab11
+    Host design (10)
+      Desiging the host application, which will require more 
+      work due to the C/C++ implementation.
+      - ajm4 & tdb1
+    Web interface design (35)
+      Designing the web frontend.
+      - pjm2
+    DB infrastructure (20)
+      Setting up the database and tables, and deciding how 
+      they should be arranged. Database design is key, and 
+      it should be in BCNF.
+      - pjm2
+
+Implempentation (300 total)
+      These sections are detailed in a seperate document 
+      named implementation_phases.txt.
+    Phase 1 (15)
+      - all
+    Phase 2 (45)
+      - all
+    Phase 3 (45)
+      - all
+    Phase 4 (30)
+      - all
+    Phase 5 (115)
+      - all
+    Further developments of public release (50)
+      - all
+
+QA, QC, Testing (195 total)
+    Doc specs (5)
+      Producing a proper specification that all of our 
+      documentation should follow.
+      - pjm2
+    Coding specs and adherance (10)
+      Producing a coding specification, and ensure all code 
+      adheres to it.
+      - all (rotation within group)
+    Testing each of the modules (180)
+      Testing each part of the system, preferably with good 
+      testing rigs.
+      - all (rotation within group)
+
+Documentation (150 total)
+    User docs (40)
+      Documentation for the user.
+      - ajm4 & tdb1
+    Maintenance docs (60)
+      Documentation for the maintainer and possible future 
+      developers.
+      - all
+    Internal docs (50)
+      Internal documentation.
+      - all