web/www/contents.inc


<!--
    contents.inc
    Created by pjm2 14/10/2000
    Last edited 16/01/2001
-->

    <table border="0" width="500">
     <tr>
      <td>
       <font size="2" face="arial,sans-serif">
       
       <center><h3>Current Status</h3></center>

       <p align="justify">
        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.
       </p>

       <p align="justify">
        The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports">Reports</a>
        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.
       </p>

       <p align="justify">
        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.  A real-time
        client is also available (Conient) and alert information can be
        displayed to the public via dynamic web pages.
       </p>
       
       <p align="justify">
        Builds of the i-scream Distributed Central Monitoring System
        are now available for <a href="/builds/">download</a> 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.
       </p>

       <p>&nbsp;</p>
       <center><h3>Project Completion</h3></center>

       <p align="justify">
        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.
       </p>
       
       <p align="justify">
        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. 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.
       </p>

       <p>&nbsp;</p>
       <center><h3>Naming History</h3></center>

       <p align="justify">
        The name <b>i-scream</b> arose from a meeting whereupon one member
        of our group randomly chose to draw an ice cream on the white 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 <b>i-scream</b>. And thus, we were left with a cunning
        play on words - it still sounded like <i>ice cream</i>, yet also
        served as a functional decription of our system - namely, one which
        screams at somebody if something has gone wrong...
       </p>
       <p align="justify">
        
       </p>
       </font>
      </td>
     </tr>   
    </table>
Revision:	1.12
Committed:	Fri Mar 30 08:08:46 2001 UTC (23 years, 9 months ago) by pjm2
Branch:	MAIN
Changes since 1.11:	+24 -20 lines
Log Message:	Made a lot of changes to the contents of the home page, as we've now completed the project. Oh my word, what are we going to do now that it's over?!
#	User	Rev	Content
1	tdb	1.1
2			<!--
3			contents.inc
4			Created by pjm2 14/10/2000
5	pjm2	1.5	Last edited 16/01/2001
6	tdb	1.1	-->
7
8			<table border="0" width="500">
9			<tr>
10			<td>
11			<font size="2" face="arial,sans-serif">
12
13			<center><h3>Current Status</h3></center>
14
15			<p align="justify">
16	pjm2	1.12	All i-scream components are now functioning to initial
17			design parameters and our system is regarded to be complete.
18			Documentation is available to assist third party programmers
19			in producing Hosts for use with the i-scream server.
20			Our progress during the project can be found in the meeting minutes.
21			Code is viewable via CVS to UKC users only.
22	pjm2	1.5	</p>
23
24			<p align="justify">
25	pjm2	1.10	The i-scream Distributed Central Monitoring System <a href="http://raptor.ukc.ac.uk/~pjm2/reports">Reports</a>
26	pjm2	1.11	are now visible on the web. You may view the latest information
27			about each machine, historical 24-hour reports and alerts for
28			each machine. Please remember that this is work in progress
29			still, so the only data currently viewable is our own data that
30			has been harvested by our own testing. Also note that historical
31			reports are only available for periods during which our server
32			was running.
33			</p>
34	pjm2	1.7
35			<p align="justify">
36	pjm2	1.5	Our current host development allows us to pass machine statistics
37			to our distributed filter arrangement, which then processes the
38			data and stores it for later use. An example of such use is the
39			historical report generator which produces graphs of machine
40	pjm2	1.12	usage over periods of time. A real-time
41			client is also available (Conient) and alert information can be
42			displayed to the public via dynamic web pages.
43	tdb	1.1	</p>
44	tdb	1.9
45			<p align="justify">
46			Builds of the i-scream Distributed Central Monitoring System
47			are now available for <a href="/builds/">download</a> from this
48	pjm2	1.11	website. These are still very much in development and should
49	tdb	1.9	only be used by people who have been in communication with the
50	pjm2	1.12	development team. Please email us if you wish to use any i-scream
51			software, as we are interested to know who is using it and we may
52			be able to help you out with any problems you encounter.
53	tdb	1.9	</p>
54	tdb	1.1
55			<p> </p>
56	tdb	1.6	<center><h3>Project Completion</h3></center>
57	tdb	1.1
58			<p align="justify">
59	pjm2	1.12	The project deadline was 4pm on 29 March 2001. Most of the group
60			met very early that morning to compile the project into five
61			lever arch folders. The project, consisting of source code, user,
62			maintenance and other documents, was handed in at 3pm. The CVS
63			repository was tagged to signify the project's completion, however,
64			development and enhancements to the system shall be continued
65			in the near future.
66	tdb	1.6	</p>
67
68			<p align="justify">
69			As can be seen in the "problem domain" document, the project
70			was aimed at the UKC Computer Science department, and as such
71	pjm2	1.12	we believe a demonstration to the "customer" is important. The
72			feedback from our demonstation was more positive than we had
73			anticipated. We believe that our project may now be of great
74			interest to anybody who wishes to monitor a number of machines
75			on their network using a central configuration.
76	tdb	1.1	</p>
77
78			<p> </p>
79			<center><h3>Naming History</h3></center>
80
81			<p align="justify">
82			The name <b>i-scream</b> arose from a meeting whereupon one member
83			of our group randomly chose to draw an ice cream on the white board.
84			It later became apparent that we had no name for our project (other
85			than 'The Project'). It seemed only natural to name our project after
86			the ice cream that had been oh-so-randomly drawn on the white board.
87			Copyright issues immediately ruled out anything involving Mr Whippy,
88			so we had to settle for <b>i-scream</b>. And thus, we were left with a cunning
89			play on words - it still sounded like <i>ice cream</i>, yet also
90			served as a functional decription of our system - namely, one which
91			screams at somebody if something has gone wrong...
92			</p>
93			<p align="justify">
94
95			</p>
96			</font>
97			</td>
98			</tr>
99			</table>