|
Creating Awareness with Subscription Services (CASS) Strategy
|
|
|
Scenarios
There are such a wide variety of possible scenarios that it is difficult to choose a representative sample. Instead, this page presents a few scenarios that potential users have asked us to address.
Documents Complete: CassDAV
CassDAV is a WebDAV implementation that sends notifications of events on files and folders. Our work group has an ISO 9001 process where five documents must be completed, filed and the fact that they were filed must itself be recorded, and all of this must happen before a certain worker can begin the part of the process which they are responsible for. A WebDAV folder named Release has been created, and the documents will be placed in this folder when complete.
Using an email awareness tool, an email archive has been subscribed to be notified each time a document is put into the Release folder, and has also subscribed to be emailed when all of the documents are filed. By emailing this to a mail archive, the archive acts as a repository documenting project history, and providing an electronic record of the completion of the five documents.
The person who must wait for the five documents to be filed before begining work uses the biffarray, with five icons; one for each of the five documents that must be completed. As each icon lights up, the user can see which documents are complete and which still in progress. The user can use this information to estimate when his task will begin and perhaps to figure out which document he may need to help people to complete.
Experimenting with new software architectures for implementing a new AWACS (Advanced Warning and Control System), and for allowing modifications to the AWACS architecture on-the-fly (while the AWACS is in the air, and with no or minimal down time for the system) it was decided that awareness gauges were needed not just to visualize system behavior of the AWACS during development, but that these gauges would be very important while modifying the architecture on the fly for verifying that the transition was successful and was running smoothly. Using the design of the AWACS simulator as a basis, and eventually building a simulator of an AWACS simulator (which was still under development), we provided a series of guages for showing load, message passing activity, warnings of dangerous software states, and other types of activity within the simulator. For more information, see our flier.
Research Staff Michael Kantor
Professor David F. Redmiles
Institute for Software Research
Information and Computer Science
University of California, Irvine
CA 92697-3425
E-mail: mkantor@ics.uci.edu
E-mail: redmiles@ics.uci.edu