1. SylViA Input Interface Design Sarai Mitnick Lisa de Larios-Heiman Carolyn Cracraft

2. Goals for SylViA Development of an interface inviting enough to compel professors to switch over to SylViA Adoption by SIMS community and continued use after our graduation Understanding how to bridge the gap between the Document Engineering process underlying our model and the UI Development process underlying our interface

3. Main Personas George Wilson  2 nd year as associate professor at SIMS  Technically oriented – came to SIMS from CMU and has engineering degree  Has taken over 255 and is working with TAs and a legacy syllabus  Lives in Berkeley Hills with his rescued greyhound, Sophie  Boyishly handsome

4. Main Personas Parvita Spencer  Visiting professor affiliated with UNIDO  Teaching a seminar on the emerging knowledge economy in South Asia  Course schedule and topics not set; she wants to respond to student desires  Renting an apartment in San Francisco  Born in India, she is married to a British journalist and travels extensively

5. Goals George’s Goals  Fit in with SIMS community and be popular with students  Support and mentor student projects  Maintain basic structure of 255 while putting his own stamp on the class  Develop his own course on managing structured and unstructured data  Get tenure and settle down in a house in Orinda

6. Goals Parvita’s Goals  Get students interested in the UNIDO program  Solicit investments, both intellectual and capital, to help Indians rise out of poverty  Develop a syllabus quickly and painlessly  Have a very flexible class schedule  See the Bay Area while she’s here

7. Scenarios Top-down approach  Start with overview of dates, then develop topics, then classes within topics  Labor-intensive at outset, but schedule stays fairly stable, so maintenance is easy Evolutionary approach  Classes developed during the semester  Need lots of flexibility for moving classes, topics, and readings around

8. Current Design My SylViA home page displaying list of existing courses Forms for adding a course Main editing area for course information, schedule, assignments, and exams Forms to support adding and editing readings, resources, topics, and lectures

9. Lo-Fi versus Interactive Initial course setup information broken into multiple screens Some rearrangement of form fields to improve flow of entering information Workflow changed to reflect more intuitive syllabus development process No access to undeveloped areas

10. Lo-Fi versus Interactive Links on left navigation bar for editing course info, schedule, and assignments moved to tabs at top of page Links for permissions removed from left nav Calendar in sidebar – makes it clearer that SylViA will be managing dates Removal of redundant fields Name changes and additional instructions to clarify editing process

11. Demo First Interactive Prototype

12. Biggest Lesson So Far Must think about the user instead of the implementation and the model  For instance, we had fields for professor first name, last name, and initials (pulled from our model) but the user should not have to enter initials, the system should figure it out