--- web/www/contents.inc 2000/10/25 23:29:30 1.1 +++ web/www/contents.inc 2002/06/01 18:05:27 1.34 @@ -1,8 +1,7 @@
- Current StatusProject News
+ Saturday 1 June 2002
- The project is currently undergoing planning decisions.
- The implementation of this central monitoring system is
- expected to completed before Easter.
+ Tuesday 21 May 2002 - Presentations
+ Saturday 18 May 2002
- Our project presentations will run on Monday 16th and
- Tuesday 17th October. Good luck, everybody.
+ Thursday 7 Feb 2002
- For those who are interested you can view an online version
- of our presentation here.
-
+ Tuesday 8 Jan 2002 + About i-scream+ + Details of the i-scream central monitoring system can be found + on the features and overview page. + A variety of screen shots from the + system show some of the key features in use. The reports demo + page provides a static example of what the i-scream reports (alerts, + historical graphs, and live data) could look like on a production system. + + ++ + The latest source code is available in the CVS + repository, with binary downloads on the downloads page. The + documentation page has details of + installation, use and maintenance for the end user and developer. + We value feedback and comments from you, so please drop us an e-mail + to dev@i-scream.org.uk. + + ++ Current Work
+ Extending monitoring facilites
+ Server security
+ Testing and Development - Naming HistoryProject History- 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. + + 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. 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 + core development team. + + ++ + 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 + 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. + + ++ + 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 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 + 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 + served as a functional description of our system - namely, one which screams at somebody if something has gone wrong... - + + + Searching i-scream |