/[i-scream]/projects/cms/documentation/minutes/minutes-20001017.txt
ViewVC logotype

Contents of /projects/cms/documentation/minutes/minutes-20001017.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph


Revision 1.1 - (show annotations)
Wed Oct 25 18:05:37 2000 UTC (18 years, 8 months ago) by tdb
Branch: MAIN
CVS Tags: PROJECT_COMPLETION, HEAD
File MIME type: text/plain
Minutes from meeting on 17/10/2000.

1 Minutes of Meeting, 17/10/2000 @ 7pm.
2 Location: 2 Mead Way
3
4 Present: ab11, pjm2, tdb1
5 Absent: ajm4
6
7 Initial discussions surrounded the fact that iau wants a
8 plan from us pretty soon. However, we soon digressed to the
9 other things we needed to get working on. These are as
10 follows;
11
12 - Produce a feature list - re: first minutes
13 - Produce an "implementation phases" document, based on the
14 feature list
15 - Prepare the above two for review by jc (and iau?)
16
17 - Set ourselves some rough milestones (ie. phase 3 by xmas
18 etc...)
19 - With the above in mind produce a plan for the overall
20 project and assign initial roles.
21
22 - Define the Interfaces of the various server classes
23 - Define the Protocols for cross-network data
24
25 Discussions about all of our limited knowledge of C/C++ put
26 an end to the plan that one of us could actually write all
27 the host programs :)
28
29 Some questions and points were raised
30
31 - Differences between Solaris SPARC/Intel - will program run
32 on both ?
33 - The "Client Interface" in the server - how much "thinking"
34 will it do, and how much will be left to the client.
35 (Thinking about bottlenecks).
36 - Database, need to get a machine sorted, and pick database.
37 - Would multicasting work for server to client
38 communications ?
39
40 Next the document on the Implementation Phases was drawn up.
41 It's only provisional at this stage, but gives us some
42 initial ideas. It was noted that by using "phases" we can
43 have milestones/breaks for testing, documentation
44 and review. This would ensure that we keep things under
45 control, and don't get swamped in code. It was also
46 mentioned that using phases would help to keep the whole
47 project in sync - ie. the server code would not run off
48 ahead of the host code.
49
50 pjm2 leaves at 7:45pm, whilst ab11 & tdb1 continue with
51 implementation phases document.
52
53 The final Implementation Phases document is seperately
54 stored.
55
56 Meeting is concluded at 8:30pm to watch MIB.

  ViewVC Help
Powered by ViewVC 1.1.26