ViewVC Help

View File | Revision Log | Show Annotations | Revision Graph | Root Listing

root/i-scream/projects/cms/documentation/plan/time_allocation.txt

Comparing projects/cms/documentation/plan/time_allocation.txt (file contents):
Revision 1.1 by pjm2, Thu Oct 26 08:25:09 2000 UTC vs.
Revision 1.3 by tdb, Mon Oct 30 17:48:25 2000 UTC

#	Line 1 | Line 1
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 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

Diff Legend

–	Removed lines
+	Added lines
<	Changed lines
>	Changed lines