SMA Stellar Presentation Mike Barker 22 June 2001

Today's Agenda • Review of Hi-Command the interface to Stellar designed for SMA use • Discussion of approaches to implementation "How would you like to implement SMA course support using Stellar? " I. e. , help me to schedule features and work for the summer.

Key Points • Stellar has been designed for usability and enhancement • At this point, the Stellar development will continue to add functions. TAs, Administrative staff, and Faculty can add content, arrange and rearrange, and become familiar with the system. • As other DLCs and Stanford adopt Stellar and add tools, functions, and content, the system will continue to grow.

Let's Look At Stellar • • Hi-Command Stellar Student View Stellar Faculty View Stellar Construction Sites: draupadi and stellar (note: these may not be available at all times, these are active development sites)

Stellar Summer Additions • Discussion Board (Jive, Panfora) • Websis, MIT libraries, MIT Event calendar integration • My. Stellar "miniportal" – student, faculty • Reuse and shared content tools • Additional styles (look-and-feel)

Stellar Summer Additions (2) • Course setup tools • User management tools • Assessment tools (quiz/test, homework handling, survey) • FAQ management • Chat/zephyr/IM

Stellar Scheduling Items • • • Training HW setup (UPS, RAID, etc. ) Documentation Support (training, familiarization) Release (when do we add new functions? Incremental or big-bang? ) • Cutover

Stellar Schedule Dates June July August September October November December January Development Operations Use Core Done Ready for Use

Stellar Schedule Dates Development Operations June 22 Core Done Integration/Test June 29 July 6 July 13 July 20 July 27 August 3 August 10 August 17 August 24 August 31 Ready for Use

Background Technical Info

Stellar-June Design Goals • Provide students with easily navigable, rich web course environment • Provide faculty, TAs, etc. with easy, effective ways to put content into system • Does not require a large central technical staff. I. e. minimize operations, maintenance, and support requirements • Ensure that system is extensible, I. e. that it is easy to additional capabilities • Allow for continuing additions, enhancements, and improvements • Must be accessible (ADA)

Stellar-June Design Goals • • • Robust, scalable, and sustainable Security, privacy, and intellectual property issues Support reuse and shared use of content Provide support for good pedagogical practices Support integration with external institutional systems Easy to use "standard" look and feel and course organization, as well as custom appearance and organization. • Support a number of portal environments (design to work with u. Portal in particular but not necessarily exclusively • Easy, effective ways to set up and organize system

Stellar Design Parameters 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Functional - does what MIT needs Supportable (at relatively low expense, by relatively few people) Extensible (open software, but also based on standards) Simple to use by TAs, administrative assistants, and faculty Integrates with external institutional systems Provides for security, privacy, and addresses intellectual property issues Easy to use "standard" look and feel and course organization, plus customizable appearance & organization. Support reuse and shared use of content Provide support for good pedagogical practices Must be accessible (ADA) Support a number of portal environments (designed to work with u. Portal in particular but not necessarily exclusively) Has a process for additions, enhancements, and improvements