+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-latest-misc.gif" width="100" height="104" align="left"></a>
+ The i-scream Distributed Central Monitoring System started off as
+ a final year project for a group of <a href="http://www.cs.ukc.ac.uk">Computer Science</a> students at
+ the <a href="http://www.ukc.ac.uk">University of Kent at Canterbury</a>, UK.
+ The project deadline was 4pm on 29th 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,
+ the project is still being developed by the <a href="acknowledgements.shtml">core development team</a>
+ as we have found the system to be very useful in practice. We would
+ love to hear of ideas for extra features that we may include in the
+ next builds.
+ </p>
+
+ <p align="justify">
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-ihost-main.gif" width="100" height="51" align="right"></a>
+ As can be seen in our "<a href="/probdomain.shtml">problem domain</a>" 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
+ feedback from our demonstation was more positive than we had
+ anticipated. We believe that the system may now be of great
+ interest to anybody who wishes to monitor a number of machines
+ on their network using a central configuration.