--- web/www/contents.inc 2001/01/16 08:31:58 1.5
+++ web/www/contents.inc 2001/12/09 18:06:07 1.27
@@ -13,57 +13,126 @@
Current Status
- Several central components are now functioning to initial
- design parameters and data can now be passed through the
- system successfully. Many planning and design decisions
- are still being made, along with various specification
- documents. Detailed information can usually be found in
- the meeting minutes. Code is viewable via CVS to UKC
- users only.
+ 
+ The "project" stage of i-scream has finished, leaving the
+ system in a completed state. Since then the goals have
+ changed from completing a project to producing a useful
+ and functional product.
+ Documentation is
+ available for people wanting to try out the i-scream
+ system, and our code is availabel via CVS.
+ Our progress during the project can be found in the meeting minutes.
+ Work is still continuing to adapt and improve the i-scream central
+ monitoring system as a product for use in networked environments.
+ 
+ The i-scream Distributed Central Monitoring System Reports
+ are no longer visible on the web. You may view some of the
+ output in the screen shots
+ section or you can sample some static example content on the
+ Reports Demo pages.
+ You may view the latest information about each machine,
+ historical 24-hour reports and alerts for each machine. If
+ you would like your i-scream web reports to be linked from this
+ site, then please email us at
+ dev@i-scream.org.uk
+
+
+
+ 
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 (viewable in a web browser). Realtime
- clients are also currently being developed - one Java Swing GUI
- version and also a command line version that can run in a terminal
- window.
+ 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. To assist in our addition of features to the system, we
+ would be extremely grateful to receive feedback from anybody who has
+ any comments about the system. You may email the development team
+ at dev@i-scream.org.uk
+
- Presentations
+ Project Completion
- On Monday 16th and Tuesday 17th October all members of the group made presentations to various groups of peers.
+ 
+ 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 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 core development team
+ 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.
-
- For those who are interested you can view an online version
- of our presentation here.
-
- Alternatively you can download a powerpoint version from
- here.
-
+
+
+ 
+ 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.
+
Naming 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 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
+
+
+
+
+
+
+