/[i-scream]/web/www/contents.inc
ViewVC logotype

Contents of /web/www/contents.inc

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


Revision 1.6 - (show annotations)
Fri Feb 16 13:22:40 2001 UTC (18 years, 6 months ago) by tdb
Branch: MAIN
Changes since 1.5: +21 -16 lines
Updated a bit.

1
2 <!--
3 contents.inc
4 Created by pjm2 14/10/2000
5 Last edited 16/01/2001
6 -->
7
8 <table border="0" width="500">
9 <tr>
10 <td>
11 <font size="2" face="arial,sans-serif">
12
13 <center><h3>Current Status</h3></center>
14
15 <p align="justify">
16 Most i-scream components are now functioning to initial
17 design parameters and data can now be passed through the
18 system and displayed successfully. Documentation is still
19 being generated, to allow for future development of the
20 i-scream project. Detailed information can usually be
21 found in the meeting minutes. Code is viewable via CVS
22 to UKC users only.
23 </p>
24
25 <p align="justify">
26 Our current host development allows us to pass machine statistics
27 to our distributed filter arrangement, which then processes the
28 data and stores it for later use. An example of such use is the
29 historical report generator which produces graphs of machine
30 usage over periods of time (viewable in a web browser). Realtime
31 clients are also currently being developed - one Java Swing GUI
32 version and also a command line version that can run in a terminal
33 window. Alerting mechanisms are being put in place to complete the
34 i-scream system.
35 </p>
36
37 <p>&nbsp;</p>
38 <center><h3>Project Completion</h3></center>
39
40 <p align="justify">
41 The project deadline is 4pm on 29 March. As such, we plan to
42 complete the coding process by (at the latest) the end of the
43 project week (26/2 - 2/3). This allows time for documentation
44 to be tidied up and completed, and printing of the project.
45 </p>
46
47 <p align="justify">
48 As can be seen in the "problem domain" document, the project
49 was aimed at the UKC Computer Science department, and as such
50 we believe a demonstration to the "customer" is important. We
51 plan to do this over the next two weeks, and the feedback given
52 will allow any "last minute" alterations to be completed.
53 </p>
54
55 <p>&nbsp;</p>
56 <center><h3>Naming History</h3></center>
57
58 <p align="justify">
59 The name <b>i-scream</b> arose from a meeting whereupon one member
60 of our group randomly chose to draw an ice cream on the white board.
61 It later became apparent that we had no name for our project (other
62 than 'The Project'). It seemed only natural to name our project after
63 the ice cream that had been oh-so-randomly drawn on the white board.
64 Copyright issues immediately ruled out anything involving Mr Whippy,
65 so we had to settle for <b>i-scream</b>. And thus, we were left with a cunning
66 play on words - it still sounded like <i>ice cream</i>, yet also
67 served as a functional decription of our system - namely, one which
68 screams at somebody if something has gone wrong...
69 </p>
70 <p align="justify">
71
72 </p>
73 </font>
74 </td>
75 </tr>
76 </table>

  ViewVC Help
Powered by ViewVC 1.1.26