All i-scream components are now functioning to initial design parameters and our system is regarded to be complete. Documentation is available to assist third party programmers in producing Hosts for use with the i-scream server. Our progress during the project can be found in the meeting minutes. Code is viewable via CVS to UKC users only.

The i-scream Distributed Central Monitoring System Reports are now visible on the web. You may view the latest information about each machine, historical 24-hour reports and alerts for each machine. Please remember that this is work in progress still, so the only data currently viewable is our own data that has been harvested by our own testing. Also note that historical reports are only available for periods during which our server was running.

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 historical report generator which produces graphs of machine usage over periods of time. A real-time client is also available (Conient) and alert information can be displayed to the public via dynamic web pages.

Builds of the i-scream Distributed Central Monitoring System are now available for download from this website. These are still very much in development and should only be used by people who have been in communication with the development team. Please email us if you wish to use any i-scream software, as we are interested to know who is using it and we may be able to help you out with any problems you encounter.

The project deadline was 4pm on 29 March 2001. Most of the group met very early that morning to compile the project into five lever arch folders. The project, consisting of source code, user, maintenance and other documents, was handed in at 3pm. The CVS repository was tagged to signify the project's completion, however, development and enhancements to the system shall be continued in the near future.

As can be seen in the "problem domain" document, the project was aimed at the UKC Computer Science department, and as such we believe a demonstration to the "customer" is important. The feedback from our demonstation was more positive than we had anticipated. We believe that our project may now be of great interest to anybody who wishes to monitor a number of machines on their network using a central configuration.

The name i-scream arose from a meeting whereupon one member of our group randomly chose to draw an ice cream on the white board. It later became apparent that we had no name for our project (other than 'The Project'). It seemed only natural to name our project after the ice cream that had been oh-so-randomly drawn on the white board. Copyright issues immediately ruled out anything involving Mr Whippy, so we had to settle for i-scream. And thus, we were left with a cunning play on words - it still sounded like ice cream, yet also served as a functional decription of our system - namely, one which screams at somebody if something has gone wrong...