Title: Escrow Project
Performer(s):
Alexander Wolf
Department of Computer Science
University of Colorado
Campus Box 430
Boulder, CO 80309-0430
Dennis Heimbigner
Department of Computer Science
University of Colorado
|
Cluster: SNAIR
Contact Information:
Phone: 303-492-5263
Fax: 303-492-2844
email: alw@cs.colorado.edu
Phone: 303-492-6643
email: dennis@cs.colorado.edu
|
1. Instructional Focus:
Content areas/topics: Not applicable. This is infrastructure supporting all CAETI software users.
Process skills: Not applicable.
2. Target Population: All users of CAETI produced software.
3. Summary Description: CAETI will generate a significant amount of educational software. For this software to succeed, a large, diverse, and active user community must develop around the software. This project will develop infrastructure and prototypes for supporting the management of complex configurations of software systems across a wide-area network. Additionally, it will explore the analogs between courseware and software.
4. Training and Staff Development:
- Teacher prerequisite skills/knowledge needed: None specified.
- Student prerequisite skills needed: None specified.
- Training needed/provided: None specified.
- Technical support needed/provided: None specified.
5. Technological/Resources Needed: UNIX will be the initial target, but later expect to move to include Windows 95 and NT. Disk and memory requirements are secondary (but not unimportant).
6. Intended Outcomes:
Students: Not applicable.
Teachers: Teachers will be able to use the tools to facilitate and enhance their use of CAETI software products.
7. Instructional Time Required: Not applicable.
8. Role of the Pilot Teacher(s): Provide input about the architecture(s) used by various groups.
9. Example(s) of the Use of this Product (Scenario): A software administrator wants to distribute upgraded versions of software. This is automatically negotiated, scheduled, and coordinated with lesson development performed by teachers and lesson plans put in place by those teachers in such a way that the upgrades are consistent with the desired learning experience at particular sites and at particular times.
Users of software develop a community to a) report bugs to developers b) publish interesting ideas to other users of the same software c) obtain access to help-desks, user registration, and written and on-line materials to help to educate users in the proper use of a software system.
