/[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.7 - (show annotations)
Sun Feb 25 18:13:28 2001 UTC (18 years, 5 months ago) by pjm2
Branch: MAIN
Changes since 1.6: +7 -0 lines
Added a link to the reports script and a brief description.

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 The i-scream Distributed Central Monitoring System Reports
27 are now visible on the web. You may view all reports
28 available for each day, but please remember that this is
29 work in progress still, so the only data currently viewable
30 is our own data that has been harvested by our own testing.
31
32 <p align="justify">
33 Our current host development allows us to pass machine statistics
34 to our distributed filter arrangement, which then processes the
35 data and stores it for later use. An example of such use is the
36 historical report generator which produces graphs of machine
37 usage over periods of time (viewable in a web browser). Realtime
38 clients are also currently being developed - one Java Swing GUI
39 version and also a command line version that can run in a terminal
40 window. Alerting mechanisms are being put in place to complete the
41 i-scream system.
42 </p>
43
44 <p>&nbsp;</p>
45 <center><h3>Project Completion</h3></center>
46
47 <p align="justify">
48 The project deadline is 4pm on 29 March. As such, we plan to
49 complete the coding process by (at the latest) the end of the
50 project week (26/2 - 2/3). This allows time for documentation
51 to be tidied up and completed, and printing of the project.
52 </p>
53
54 <p align="justify">
55 As can be seen in the "problem domain" document, the project
56 was aimed at the UKC Computer Science department, and as such
57 we believe a demonstration to the "customer" is important. We
58 plan to do this over the next two weeks, and the feedback given
59 will allow any "last minute" alterations to be completed.
60 </p>
61
62 <p>&nbsp;</p>
63 <center><h3>Naming History</h3></center>
64
65 <p align="justify">
66 The name <b>i-scream</b> arose from a meeting whereupon one member
67 of our group randomly chose to draw an ice cream on the white board.
68 It later became apparent that we had no name for our project (other
69 than 'The Project'). It seemed only natural to name our project after
70 the ice cream that had been oh-so-randomly drawn on the white board.
71 Copyright issues immediately ruled out anything involving Mr Whippy,
72 so we had to settle for <b>i-scream</b>. And thus, we were left with a cunning
73 play on words - it still sounded like <i>ice cream</i>, yet also
74 served as a functional decription of our system - namely, one which
75 screams at somebody if something has gone wrong...
76 </p>
77 <p align="justify">
78
79 </p>
80 </font>
81 </td>
82 </tr>
83 </table>

  ViewVC Help
Powered by ViewVC 1.1.26