1. UC HIPO UCWISE Help-for-Instructor POrtal First Interactive prototype Lois Wei Minakshi Mukherjee Tofer Merritt

2. About UCWISE UCWISE (University of California Web- based Instruction for Science and Engineering) is a project funded by CITRIS Provides technology and curricula for experimental laboratory–base courses in university level computer science and engineering.

3. UC HIPO Metadata Tagging Tool Need for UC HIPO Metadata Tagging Tool Present metadata interface is functional but not very user friendly Goals of UC HIPO Metadata Tagging Tool Facilitate tagging of curriculum content with metadata for easy categorization, retrieval, reuse, and sharing of information related to curriculum and study material

4. Personas Factors considered All target users have a fair amount of computer knowledge All users are hard pressed for time Need to track instructor schedules and students progress The three personas Dr. Alex Rosenblum: UCWISE course author / instructor Jane Kozovski: UCWISE course adopter / editor / researcher Prof. Mark Hopkins: UCWISE Course Adopter (Soon To Be Retired CS Instructor)

5. Dr. Alex Rosenblum UCWISE course author / instructor 35 yr old lecturer at Computer science division Goals Using the UCWISE tools to teach and better manage the lower division computer science course that have more than 100 students; possibly using the UCWISE tools to improve communication between instructor/TA, instructor/students; using UCWISE tools to author many computer science curriculum easily Making sure the curriculum content he authored in UCWISE can be re-used by other instructors easily

6. Jane Kozovski UCWISE course adopter / editor / researcher 39 yr old computer science instructor at Merritt College Oakland Goals To easily search for existing UCWISE curriculum material authored by other instructors which she can re-use for her course To easily share her curriculum material with other instructors who uses UCWISE To recruit other computer science instructors at Merritt college to use the UCWISE tool Find out how to improve the UCWISE curriculum materials and the UCWISE tools to make the lab-based teaching even more effective

7. Prof. Mark Hopkins UCWISE Course Adopter (Soon To Be Retired CS Instructor) 63 yr old Computer Graphics Programming instructor at San Diego State University Goals To have his curriculum and metadata be a benchmark for future UCWISE-taught computer graphics courses. To have a flexible system for metadata storage, to allow for changes as the curriculum evolves. Making his metadata well thought out and designed, such that it can be reused for future courses.

8. Scenario # 1 Title Using metadata quiz template to add bookkeeping metadata Description Captures a very particular usage of the Metadata Tagging Tool, specifically, metadata template replacement Suitable for Prof. Mark Hopkins

9. Scenario # 2 Title Adding instructor notes to a quiz activity Description Presenting a situation where an instructor needs to communicate with their TA by providing metadata in the form of instructor notes, indicating that a quiz needs to be edited to accommodate international students. Suitable for Dr. Alex Rosenblum

10. Scenario # 3 Title Tag an individual quiz question with Cognitive Learning Metadata Description Demonstrating a situation where a more in-depth method of tagging is utilized. In particular, tagging an individual question of a previously authored quiz with “modification” metadata to indicate that students’ ability to determine whether code needs modification is being tested. Suitable for Jane Kozovski

11. Interactive Design vs. Low-Fi Prototype Cognitive Learning Metadata section Instructor Notes section: no longer using the faceted design since the amount of metadata for this section has significantly shortened; allow instructor to attach notes to each of the instructor notes metadata Navigation features: breadcrumb, prev/next feature Added a search feature Still in the process of talking to instructors about topics/domain-specific metadata

12. Demo of the Prototype

13. Lessons Learned Should not make assumptions about how the user would like to represent data Really need to be flexible to adjust what the users want, really need to be flexible to make changes to the interface design We are not working under a very black and white situation in which the users know exactly what they want. They are still trying to figure out how they want to organize the metadata It is very important to have clear navigation (add breadcrumbs, previous/next button), and provide easy undo feature The user seems to always prefer a search feature

14. Questions / Suggestions?