| 1 |
< |
Estimated time allocation |
| 2 |
< |
========================= |
| 3 |
< |
|
| 4 |
< |
pjm2, 23/10/2000 |
| 5 |
< |
|
| 6 |
< |
|
| 7 |
< |
Combined efforts in hours: - |
| 8 |
< |
|
| 9 |
< |
|
| 10 |
< |
Management and Admin tasks (200 total) |
| 11 |
< |
webpages (10) |
| 12 |
< |
cvs (10) |
| 13 |
< |
meetings/minutes/meetings with iau (180) |
| 14 |
< |
|
| 15 |
< |
Requirements, analysis, specification (85 total) |
| 16 |
< |
Find out what the reqs are (5) |
| 17 |
< |
look at other systems (30) |
| 18 |
< |
Analysing our own ideas (40) |
| 19 |
< |
produce spec (10) |
| 20 |
< |
|
| 21 |
< |
Design (200 total) |
| 22 |
< |
UML (25) |
| 23 |
< |
Interface design (20) |
| 24 |
< |
Protocol design (30) |
| 25 |
< |
Server design (40) |
| 26 |
< |
GUI/Client design (20) |
| 27 |
< |
Host design (10) |
| 28 |
< |
Web interface design (35) |
| 29 |
< |
DB infrastructure (20) |
| 30 |
< |
|
| 31 |
< |
Implempentation (300 total) |
| 32 |
< |
Phase 1 (15) |
| 33 |
< |
Phase 2 (45) |
| 34 |
< |
Phase 3 (45) |
| 35 |
< |
Phase 4 (30) |
| 36 |
< |
Phase 5 (115) |
| 37 |
< |
Further developments of public release (50) |
| 38 |
< |
|
| 39 |
< |
QA, QC, Testing (195 total) |
| 40 |
< |
Doc specs (5) |
| 41 |
< |
Coding specs (10) |
| 42 |
< |
Testing each of the modules (180) |
| 43 |
< |
|
| 44 |
< |
Documentation (150 total) |
| 45 |
< |
User docs (40) |
| 46 |
< |
Maintenance docs (60) |
| 47 |
< |
Internal docs (50) |
| 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 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 |
