+ <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.kent.ac.uk">
+ Computer Science</a> students at the <a href="http://www.kent.ac.uk">
+ University of Kent at Canterbury</a>, UK. The project was completed at
+ 4pm on 29 March 2001. It consisted of five lever-arch folders containing
+ mostly source code and documentation. The CVS repository was tagged to
+ signify this even, however, the project is still being developed by the
+ <a href="acknowledgements.shtml">core development team</a>.
+ </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 interest
+ to anybody who wishes to monitor a number of machines on their
+ network using a central configuration. The i-scream central
+ monitoring system is now being used by the UKC Computer Science
+ department, and their feedback is being used to further improve
+ the product.
+ </p>
+
+ <p align="justify">
+ <a href="screenshots/"><img border="0" src="screenshots/thumbnail-conient-config.gif" width="100" height="48" align="left"></a>
+ The name <i>i-scream</i> arose from a meeting whereupon one member
+ of the <a href="acknowledgements.shtml">development team</a> felt a strange urge to draw an ice cream on the discussion board.