- Most i-scream components are now functioning to initial - design parameters and data can now be passed through the - system and displayed successfully. Documentation is still - being generated, to allow for future development of the - i-scream project. Detailed information can usually be - found in the meeting minutes. Code is viewable via CVS - to UKC users only. + 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.
@@ -27,29 +37,42 @@ 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. Alerting mechanisms are being put in place to complete the - i-scream system. + 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 is 4pm on 29 March. As such, we plan to - complete the coding process by (at the latest) the end of the - project week (26/2 - 2/3). This allows time for documentation - to be tidied up and completed, and printing of the project. + 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. We - plan to do this over the next two weeks, and the feedback given - will allow any "last minute" alterations to be completed. + 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.