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