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 hours total)
    
    webpages (10 hours)
      Creating, and maintaining the website, aswell as 
      ensuring that everyone adheres to the same design.
        - pjm2 (others contribute 50%)
    
    cvs (10 hours)
      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 hours)
      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 hours total)
    
    Find out what the reqs are (5 hours)
      Find out exactly what the system needs to do, 
      including meeting with jc. Document these requirements 
      in a requirements list.
        - all members
    
    look at other systems (30 hours)
      Research into similiar products with the intention of 
      seeing how our proposed idea compares, and maybe get 
      ideas for new features in the system.
        - ajm4 & ab11
    
    Analysing our own ideas (40 hours)
      Looking at the merits/weaknesses of our ideas, and 
      helping to improve them. Finding faults in our ideas 
      will help to improve the final design.
        - all members
    
    produce spec (10 hours)
      Generating a relatively detailed specification of the 
      overall system, from which proper UML designs can be 
      made.
        - tdb1 & pjm2


Design (200 hours total)
    
    UML (25 hours)
      Producing UML designs for the various parts of the 
      system.
        - ajm4
    
    Interface design (20 hours)
      Specifying the interfaces for communication between 
      the various parts of the system.
        - pjm2 & ab11
    
    Protocol design (30 hours)
      Specifying the protocol in detail for host to server 
      communications, and client to server communications.
        - pjm2 & ab11
    
    Server design (40 hours)
      Designing the server and how the components plug 
      together and interact.
        - tdb1 & ajm4
    
    GUI/Client design (20 hours)
      Designing the GUI/Client side of the system.
        - pjm2 & ab11
    
    Host design (10 hours)
      Desiging the host application, which will require more 
      work due to the C/C++ implementation language.
        - ajm4 & tdb1
    
    Web interface design (35 hours)
      Designing the web frontend to the database, providing 
      graphs and access to logs.
        - pjm2
    
    DB infrastructure (20 hours)
      Setting up the database and tables, and deciding how 
      they should be arranged. Database design principles 
      should be put into practice.
        - pjm2


Implempentation (300 hours total)
    
      These sections are detailed in a seperate document 
      named implementation_phases.txt, and are documented in 
      quite some detail.
      
    Phase 1 (15 hours)
        - all
    Phase 2 (45 hours)
        - all
    Phase 3 (45 hours)
        - all
    Phase 4 (30 hours)
        - all
    Phase 5 (115 hours)
        - all
    Further developments of public release (50 hours)
        - all


QA, QC, Testing (195 hours total)
    
    Doc specs (5 hours)
      Producing a proper specification that all of our 
      documentation should follow.
        - pjm2
    
    Coding specs and adherance (10 hours)
      Producing a coding specification, and ensure all code 
      adheres to it.
        - all (rotation within group)
    
    Testing each of the modules (180 hours)
      Testing each part of the system, preferably with good 
      testing rigs.
        - all (rotation within group)


Documentation (150 hours total)
    
    User docs (40 hours)
      Documentation for the user.
        - ajm4 & tdb1
    
    Maintenance docs (60 hours)
      Documentation for the maintainer and possible future 
      developers.
        - all
    
    Internal docs (50 hours)
      Internal documentation made during the course of the 
      project.
        - all
Revision:	1.3
Committed:	Mon Oct 30 17:48:25 2000 UTC (24 years, 1 month ago) by tdb
Content type:	text/plain
Branch:	MAIN
CVS Tags:	PROJECT_COMPLETION, HEAD
Changes since 1.2:	+110 -73 lines
Error occurred while calculating annotation data.
Log Message:	Tidied it up a touch further.
#	Content
1	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 hours total)
17
18	webpages (10 hours)
19	Creating, and maintaining the website, aswell as
20	ensuring that everyone adheres to the same design.
21	- pjm2 (others contribute 50%)
22
23	cvs (10 hours)
24	Setting up, managing and maintaining the CVS
25	repository and related facilities. Also assisting in
26	the use of CVS.
27	- tdb1 (others contribute 50%)
28
29	meetings/minutes/meetings with iau (180 hours)
30	Attending regular meetings, both as a group and with
31	iau. Also taking of minutes and planning each meeting
32	in advance.
33	- all members
34
35
36	Requirements, analysis, specification (85 hours total)
37
38	Find out what the reqs are (5 hours)
39	Find out exactly what the system needs to do,
40	including meeting with jc. Document these requirements
41	in a requirements list.
42	- all members
43
44	look at other systems (30 hours)
45	Research into similiar products with the intention of
46	seeing how our proposed idea compares, and maybe get
47	ideas for new features in the system.
48	- ajm4 & ab11
49
50	Analysing our own ideas (40 hours)
51	Looking at the merits/weaknesses of our ideas, and
52	helping to improve them. Finding faults in our ideas
53	will help to improve the final design.
54	- all members
55
56	produce spec (10 hours)
57	Generating a relatively detailed specification of the
58	overall system, from which proper UML designs can be
59	made.
60	- tdb1 & pjm2
61
62
63	Design (200 hours total)
64
65	UML (25 hours)
66	Producing UML designs for the various parts of the
67	system.
68	- ajm4
69
70	Interface design (20 hours)
71	Specifying the interfaces for communication between
72	the various parts of the system.
73	- pjm2 & ab11
74
75	Protocol design (30 hours)
76	Specifying the protocol in detail for host to server
77	communications, and client to server communications.
78	- pjm2 & ab11
79
80	Server design (40 hours)
81	Designing the server and how the components plug
82	together and interact.
83	- tdb1 & ajm4
84
85	GUI/Client design (20 hours)
86	Designing the GUI/Client side of the system.
87	- pjm2 & ab11
88
89	Host design (10 hours)
90	Desiging the host application, which will require more
91	work due to the C/C++ implementation language.
92	- ajm4 & tdb1
93
94	Web interface design (35 hours)
95	Designing the web frontend to the database, providing
96	graphs and access to logs.
97	- pjm2
98
99	DB infrastructure (20 hours)
100	Setting up the database and tables, and deciding how
101	they should be arranged. Database design principles
102	should be put into practice.
103	- pjm2
104
105
106	Implempentation (300 hours total)
107
108	These sections are detailed in a seperate document
109	named implementation_phases.txt, and are documented in
110	quite some detail.
111
112	Phase 1 (15 hours)
113	- all
114	Phase 2 (45 hours)
115	- all
116	Phase 3 (45 hours)
117	- all
118	Phase 4 (30 hours)
119	- all
120	Phase 5 (115 hours)
121	- all
122	Further developments of public release (50 hours)
123	- all
124
125
126	QA, QC, Testing (195 hours total)
127
128	Doc specs (5 hours)
129	Producing a proper specification that all of our
130	documentation should follow.
131	- pjm2
132
133	Coding specs and adherance (10 hours)
134	Producing a coding specification, and ensure all code
135	adheres to it.
136	- all (rotation within group)
137
138	Testing each of the modules (180 hours)
139	Testing each part of the system, preferably with good
140	testing rigs.
141	- all (rotation within group)
142
143
144	Documentation (150 hours total)
145
146	User docs (40 hours)
147	Documentation for the user.
148	- ajm4 & tdb1
149
150	Maintenance docs (60 hours)
151	Documentation for the maintainer and possible future
152	developers.
153	- all
154
155	Internal docs (50 hours)
156	Internal documentation made during the course of the
157	project.
158	- all