documentation/plan/time_allocation.txt

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
Revision:	1.2
Committed:	Mon Oct 30 14:04:59 2000 UTC (23 years, 6 months ago) by tdb
Content type:	text/plain
Branch:	MAIN
Changes since 1.1:	+121 -47 lines
Log Message:	Addition of who's doing what and basic description of each section.
#	User	Rev	Content
1	tdb	1.2	Estimated time allocation
2			=========================
3
4			pjm2, 23/10/2000
5			tdb1, 30/10/2000
6
7			Combined efforts in hours, with description of sections and
8			names against each section.
9
10			It should be noted that this is a plan, and there are many
11			circumstances that could affect how closely we follow this.
12			There will, of course, be a review at the end of the
13			project.
14
15
16			Management and Admin tasks (200 total)
17			webpages (10)
18			Maintaining and updating the website.
19			- pjm2 (others contribute 50%)
20			cvs (10)
21			Setting up, managing and maintaining the CVS
22			repository and related facilities. Also assisting in
23			the use of CVS.
24			- tdb1 (others contribute 50%)
25			meetings/minutes/meetings with iau (180)
26			Attending regular meetings, both as a group and with
27			iau. Also taking of minutes and planning each meeting
28			in advance.
29			- all members
30
31			Requirements, analysis, specification (85 total)
32			Find out what the reqs are (5)
33			Find out exactly what the system needs to do,
34			including meeting with jc.
35			- all members
36			look at other systems (30)
37			Research into simliar products with the intention of
38			seeing how our proposed idea compares.
39			- ajm4 & ab11
40			Analysing our own ideas (40)
41			Looking at the merits/weaknesses of our ideas, and
42			helping to improve them.
43			- all members
44			produce spec (10)
45			Generating a relatively detailed specification of the
46			overall system.
47			- tdb1 & pjm2
48
49			Design (200 total)
50			UML (25)
51			Producing UML designs for the various parts of the
52			system.
53			- ajm4
54			Interface design (20)
55			Specifying the interfaces for communication between
56			the various parts of the system.
57			- pjm2 & ab11
58			Protocol design (30)
59			Specifying the protocol in detail.
60			- pjm2 & ab11
61			Server design (40)
62			Designing the server and how the components plug
63			together and interact.
64			- tdb1 & ajm4
65			GUI/Client design (20)
66			Designing the GUI/Client side of the system.
67			- pjm2 & ab11
68			Host design (10)
69			Desiging the host application, which will require more
70			work due to the C/C++ implementation.
71			- ajm4 & tdb1
72			Web interface design (35)
73			Designing the web frontend.
74			- pjm2
75			DB infrastructure (20)
76			Setting up the database and tables, and deciding how
77			they should be arranged. Database design is key, and
78			it should be in BCNF.
79			- pjm2
80
81			Implempentation (300 total)
82			These sections are detailed in a seperate document
83			named implementation_phases.txt.
84			Phase 1 (15)
85			- all
86			Phase 2 (45)
87			- all
88			Phase 3 (45)
89			- all
90			Phase 4 (30)
91			- all
92			Phase 5 (115)
93			- all
94			Further developments of public release (50)
95			- all
96
97			QA, QC, Testing (195 total)
98			Doc specs (5)
99			Producing a proper specification that all of our
100			documentation should follow.
101			- pjm2
102			Coding specs and adherance (10)
103			Producing a coding specification, and ensure all code
104			adheres to it.
105			- all (rotation within group)
106			Testing each of the modules (180)
107			Testing each part of the system, preferably with good
108			testing rigs.
109			- all (rotation within group)
110
111			Documentation (150 total)
112			User docs (40)
113			Documentation for the user.
114			- ajm4 & tdb1
115			Maintenance docs (60)
116			Documentation for the maintainer and possible future
117			developers.
118			- all
119			Internal docs (50)
120			Internal documentation.
121			- all