next up previous contents
Next: Quotes that might Up: No Title Previous: Administrative Information

The Outline of the Rest

[] . CSCW/HCI - we could skip this and cross our fingers
        - Iterative design
        - Use infrastructure from above
        - Interview and observe scientists
        - Build custom environments for what they need
        - Constant review process
        

[] . Innovative Claims (Our Cool Tech Ideas that are different...)
        (Rick with help and brainstorm with R'm)

	- scalability of cyberspace servers
		+ widespread use ....
	- high performance storage and I/O for archiver/playback engine
	- remote WAN control of experiments and distributed data analysis
	- exploration of multi-CAVE for collaborative immersive experiences
	- use of kerberos security mechanisms
	- personal private high profile wireless smart audio interfaces ....
	- reliability of connections over LANs... 
	- GRAPHICS

[] . Research and Development Plan (methodology) 
        (How are we going to work) (Terry and Rick)

	- end user participation in system specification
	- rapid prototyping of system components
	- incremental testing 
	- end user evaluation and feedback and training
	- incremental insertion of new technology
	- measurement and evaluation of user feedback and system performance
	  (metrics and mid course correction)
	- transition to production use
	- documentation and online training...

[] . Management Plan (Rick)
	- project leadership
	- organization of the collaboration
	- team descriptions (local team structure)
	- budget flexibility
	- collaboration meetings and workshops (training)
	- GRAPHICS

[] . Statement of Work (who is doing what) (paragraph on each) (Togther)
	- MCS 
	- NEU
	- MSD
	- HEP
	- ECT
	- EVL

[] . Milestones and Deliverables (three or four major delierables/year)
	- first year
	- second year (review of progress and methods)
	- third year

     Deliverables:
       A MOO server, extended for multi-media application interaction and 
         secure  networking.
       An initial elab environment, customized to each individual test site
         and final installation.
       Tools and documentation for extending the elab space.
       A fully distributed and scalable system for elab implementation, 
         expected to be operational several years into the project.
       An X-Windows-based browser similar to Mosaic which can utilize
         the World Wide Web as well an interact with the elab server.
       An ASCII text version of the same.
       A protocol specification for browser/elab communication.
       User documentation for the browsers.
       A ``tutorial'' elab.
       A protocol definition for broker-to-broker communication.
       A protocol definition for broker-to-local-module communication.
       A broker implementation for both user sessions and elabs.
       A security mechanism based on public key encryption and site
         identification.
       Details of the data streams for the modules that we implement.
       A mechanism for combining and separating data streams.
       X window proxy server
       Video modules
       Audio modules
       White board modules
       Shared editors
       A shared document viewer that supports version control.
       A user directory service.
       An interactive text module.
       Interfaces to the scientific instruments at use in our test bed sites.
       A playback interface for elabs.
       A playback engine implementation that takes advantage of super 
         computers.
       A simpler playback engine suitable for use on smaller computers.
       A method of storing data that allows one to locate and search relevant
         archives.
       A network library for building modules.
       Documentation for the above.

       (wow)      

[] . Budget Table
	- MCS
	- NEU
	- MSD
	- HEP
	- ECT
	- EVL

[] . Vitas and Qualifications (flesh out list)
	- Rick
	- Remy
	- Bob
	- Bill
	- Terry
	- etc.

[] . Letter of Collaboration and Support
	- PARC ?
	- IBM ?
	- MITRE ?
	- CERN ?
	- ???



[email protected]