13 |
|
<center><h3>Current Status</h3></center> |
14 |
|
|
15 |
|
<p align="justify"> |
16 |
< |
Several central components are now functioning to initial |
16 |
> |
Most i-scream components are now functioning to initial |
17 |
|
design parameters and data can now be passed through the |
18 |
< |
system successfully. Many planning and design decisions |
19 |
< |
are still being made, along with various specification |
20 |
< |
documents. Detailed information can usually be found in |
21 |
< |
the meeting minutes. Code is viewable via CVS to UKC |
22 |
< |
users only. |
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/browser.php">Reports</a> |
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 |
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. |
40 |
> |
window. Alerting mechanisms are being put in place to complete the |
41 |
> |
i-scream system. |
42 |
|
</p> |
43 |
|
|
44 |
|
<p> </p> |
45 |
< |
<center><h3>Presentations</h3></center> |
45 |
> |
<center><h3>Project Completion</h3></center> |
46 |
|
|
47 |
|
<p align="justify"> |
48 |
< |
On Monday 16th and Tuesday 17th October all members of the group made presentations to various groups of peers. |
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 |
< |
<p align="justify"> |
54 |
< |
For those who are interested you can view an online version |
55 |
< |
of our presentation <a href="documentation/presentation/i-scream-web.htm">here</a>. |
56 |
< |
<br> |
57 |
< |
Alternatively you can download a powerpoint version from |
58 |
< |
<a href="documentation/presentation/i-scream-web.ppt"> here</a>. |
59 |
< |
</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> </p> |
63 |
|
<center><h3>Naming History</h3></center> |