--- projects/cms/documentation/plan/time_allocation.txt 2000/10/30 14:04:59 1.2 +++ projects/cms/documentation/plan/time_allocation.txt 2000/10/30 17:48:25 1.3 @@ -13,109 +13,146 @@ 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) +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) + - 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 + - all members -Requirements, analysis, specification (85 total) - Find out what the reqs are (5) + +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. - - 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) + 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. - - all members - produce spec (10) + 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. - - tdb1 & pjm2 + overall system, from which proper UML designs can be + made. + - tdb1 & pjm2 -Design (200 total) - UML (25) + +Design (200 hours total) + + UML (25 hours) Producing UML designs for the various parts of the system. - - ajm4 - Interface design (20) + - ajm4 + + Interface design (20 hours) 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) + - 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) + - tdb1 & ajm4 + + GUI/Client design (20 hours) Designing the GUI/Client side of the system. - - pjm2 & ab11 - Host design (10) + - pjm2 & ab11 + + Host design (10 hours) 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) + 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 is key, and - it should be in BCNF. - - pjm2 + they should be arranged. Database design principles + should be put into practice. + - pjm2 -Implempentation (300 total) + +Implempentation (300 hours 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 + 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 total) - Doc specs (5) + +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) + - 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) + - 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) + - all (rotation within group) -Documentation (150 total) - User docs (40) + +Documentation (150 hours total) + + User docs (40 hours) Documentation for the user. - - ajm4 & tdb1 - Maintenance docs (60) + - ajm4 & tdb1 + + Maintenance docs (60 hours) Documentation for the maintainer and possible future developers. - - all - Internal docs (50) - Internal documentation. - - all + - all + + Internal docs (50 hours) + Internal documentation made during the course of the + project. + - all