Information System Design Info-440 Autumn 2002 Session #13

Agenda Quiz Review assignment #3 Finish IA exercise Review sketches Feedback on project proposals Participatory design & prototyping Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Admin Announcements Interactive design project Upcoming Anyone? Feedback today Upcoming Design Exercise #3: Nov 13th Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Assignment #3: Goals & Expectations

Assignment #3 This assignment consists of three parts: Scenario (10 points) Conceptual model (20 points) Information architecture (10 points) Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Part I 10: Personalization scenario You write a plausible use scenario The scenario shows an understanding for personalization on the web The scenario tells a well-defined story, using proper names, events, and relevant artifacts The scenario encompasses a full context of use Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Part II 10: Conceptual model (diagram) You identify the major entities, relationships, attributes & operations in My Yahoo! You prioritize what you show You draw a legible diagram that is laid out logically and neatly You use the correct symbols You use a legend and call outs to explain your diagram Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Part II (continued) 10: Conceptual model (discussion) You identify two metaphors and justify your choices. You discuss, and justify, their merits. You provide a reasoned explanation for how well the conceptual model supports the scenario. You propose a method for investigating users’ mental models of personalization. The merits of the proposal are discussed and justified. Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Part III 10: Information architecture blueprints You draw an architecture of the content displays of the site You draw an architecture of the sign-up process You prioritize what you show The diagrams are logical and neatly presented You use the correct symbols You use a legend and call-outs to explain your diagram Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

IA Blueprint Exercise

Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Project Proposals: Feedback

Overall Generally: Good first drafts No one was too narrow! All most everyone should aim to narrow problem Everyone should revise for final submission Some people showed a lot of passion Nice to see the journals Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Topics Heart Dance Birds Allen,David Paul Doan,KhanhvyKim Chan,Alan Kwan-Ming Lai,Alexander Tsekit Yearsley,John Ross Heart Allen,David Paul Doan,KhanhvyKim McCully,Bretton Major Nakashima,Jon Kiyoshi Stevens,Tyler James Tai,Robert C Birds Hong,E-Sok Kanov,Jeanine Marie Lau,Hong Wun Meade,Kimberly Dawn Saint Clair,Nathan Amari Stroud,William G IV Villarta,Robert Joseph Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Topics Snow Camera Bonogofsky,Elexa Karen Chow,Andy Smith,Benjamin David Tabert,Jason Ryan Young,Nathan Dong Camera Cadag,Eithon Michael Galinato Cheung,Jeremy Tai Loi Coles,Matthew Scott Ganje,David Patrick Hamilton,Dustin C Lanier,Philip Steven Lovseth,Joshua Timothy McCully,Bretton Major Stolyar,Anna Towle,Jeffrey Alan Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Some common challenges The objective is for everyone to be able to do X better Example: The objective is for all cooks to cook better This objective is too broad Experience shows it won’t meet anyone’s needs Better: The objective is teach novice Indian food cooks how to make simple traditional vegetarian meal Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Some common challenges The design will replace person X Example: The ‘joke machine’ will replace comedians Your tablet computer application should not aim to replace people Better: My ‘joke machine’ will allow children to share jokes The design will enhance a situation by doing X, Y, Z Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Some common challenges The design will be X because of X Example: The design will be easy to use because it presents clear and concise information A circular argument Better: We will measure ease of use by: Timing how long it takes to users to complete the three key goals … Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Some common challenges The design will be ineffective because it will cost too much Why work on a project that will be ineffective? No cost justification Better: Make some assumptions and make estimate of Return on Investment Example: Doctor’s time is work $150/hr It takes 20min to explain a heart problem The application will reduce this time to 10min … and give better information Cost savings could therefore be … Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Common challenges The design will be a super-combination of X, Y, and Z Be careful of the technological paradox The more features you add the complex the thing become Try to enhance the situation with incremental changes Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Vision statements Focus on ‘hook’ or ‘root concept’ that makes your idea innovative and unique Hints Narrow is better What is the ‘value proposition’ Why would people be excited by your idea Strike a balance between user needs and technology for satisfying them Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Background Describe Hints: The major factors and issues within the situation How your design will respond to those issues Hints: Compare your design to ‘paper books’ or other everyday technology Suggest how your design with ‘amplify’ or ‘augment’ existing human skills or activities Try to avoid redundancy between background section and vision Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Stakeholders Once you’ve identified the stakeholders Consider the relationships amongst them Narrow your focus SCIENCE FAIR influence supports Judges Students Parents mark advise communicates Teachers Community at large Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Social impact statement Some projects might not have significant social issues – It’s okay to say that (but do justify your belief) Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Timetable Many copied it from the assignment Expected you to enhance it make it your own Some people added things such as: Methods for working with users to generate requirements (interviews, simple experiments, observations, etc.) Iterations Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Hints Think about who the audience is Think about your objective Advance Concept Group (ACG) Think about your objective Convince ACG that you have a great idea and a way to solve it Do some background reading in your domain Find ways to gather feedback from real people Brainstorm and talk about your ideas Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Next week Still one class behind! No class on Monday (veteran’s day) Sorry… made some timing/coverage mistakes No class on Monday (veteran’s day) Wednesday Participatory design & prototyping (principles and theory) No readings for next week The following week: Usability Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Prototyping

Development process Waterfall model Linear process with well-define phases One phase feeds into the next Documents are outputs and inputs Example Analysis of functional requirements Software design Implementation Testing Maintenance Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Development process Prototyping and iterative development Create a working model Demonstrate model and test it quickly Prototypes can be created at different phases: Requirements Conceptual design Detailed design Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Trade-offs Waterfall model + Simplifies management Cost estimation Tracking progress Coordination amongst large number of people Feedback on system is weak New requirements are uncovered during testing No early feedback Tendency to focus inward on the process Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Trade-offs Prototyping + Feedback is strong Incremental approach Early feedback on requirements User involvement throughout process Identification of dependencies Incremental approach Risk that prototype becomes the system Risk that prototype will reflect incremental changes rather than radical changes Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Development process Define: Vision/scope Deploy: Delivery stable Version Release Define: Vision/scope Needs assessment Deploy: Delivery stable technology Beta software Vision/scope document Develop: Build the technology Design: Invent the technological solution Design specifications document Copyright David Hendry (INFO-440 session 13 - 11/13/2002)

Types of prototyping

When do carry out prototyping? Engineering  Design Design  Engineering Selecting materials Low fidelity vs. high fidelity Involving users Testing methods Copyright David Hendry (INFO-440 session 13 - 11/13/2002)