+
All i-scream components now function to initial
design parameters and our system is regarded to be complete.
Documentation is available to assist third party programmers
@@ -23,7 +23,7 @@
-
+
All i-scream components now function to initial
design parameters and our system is regarded to be complete.
Documentation is available to assist third party programmers
@@ -23,7 +23,7 @@
- 
+
The i-scream Distributed Central Monitoring System Reports
are now visible on the web. If you are not a local user, then you may
view some of the output in the screenshots section.
@@ -35,7 +35,7 @@
- 
+
Our current host development allows us to pass machine statistics
to our distributed filter arrangement, which then processes the
data and stores it for later use. An example of such use is the
@@ -46,7 +46,7 @@
- 
+
The latest builds of the i-scream Distributed Central Monitoring System
are now available for download from this
website. To assist in our addition of features to the system, we
@@ -59,7 +59,7 @@
- 
+
The i-scream Distributed Central Monitoring System started off as
a final year project for a group of Computer Science students at
the University of Kent at Canterbury, UK.
@@ -75,7 +75,7 @@
- 
+
As can be seen in our "problem domain" document, the project
was aimed at the UKC Computer Science department, and as such
we believed that a demonstration to the "customer" was important. The
@@ -89,7 +89,7 @@
- 
+
The name i-scream arose from a meeting whereupon one member
of the development team felt a strange urge to draw an ice cream on the discussion board.
It later became apparent that we had no name for our project (other