CSC USI Class Meeting 7 February 24, 2009

 Apologies for lack of celebration for Mardi Gras

Important Concepts As listed on the one-minute survey  GOMS analysis  User interface assessment with GUEPs and CDs  Specific GUEPS and CDs including Consistency, KISS, Viscosity  Complexity of UI design  Keystroke level analysis, models (e.g. Fitts’ Law), and notation  Semantic and syntactic analysis of widgets  Mental models  Learning tools: concept maps, research paper reading process

Article Presentations  Choose one of the three topic areas (defined below)  Find an interesting recent (last 4 years) paper in the area  Prepare a 15 minute presentation of the paper –The background –The experiment –The results –The critique –The relationship to other papers or concepts

Article Presentations (2) Subject areas:  Intelligent user interfaces (IUI) and especially the implementation and evaluation of features.  Computer supported collaborative work (CSCW) and especially the design and functionality of collaboration systems  Participatory design as a software engineering tactic –Users involved at all stages of system development

Course planning  3/3 – Spring break  3/9 –  Choice of research article for presentation with area and bibliographic information due, via  Perfect Phone design team task choice due, via  3/10 – Interface design team meetings  Preliminary Perfect Phone design report due at end of class  Research project Progress Report 1 due  3/17 – St. Patrick’s Day, but class meets.  Final Perfect Phone design report due  3/24 –  Research project Progress Report 2 due  3/31 – Paper presentations: Intelligent user interfaces

Course planning (2)  4/7 – Paper presentations: Computer supported collaborative work  Draft research report, part 1, due  4/14 – Paper presentations: Participatory design  Draft research report, part 2, due  4/21 –  4/28 – Research Project Presentations  Final research report due  5/5 – Final Exam  Research project poster abstract and design due

Research Project 1. Progress reports (PR 1 due 3/10; PR 2 due 3/24) 2. Report drafts (Sections 1&2 due 4/7; Sections 3-5 due 4/14) 3. Final written report (Due 4/28) 4. Oral report (Given 4/28) 5. Poster abstract and design (Due 5/5)

The Perfect Phone Project  Goal: Create a user interface design –As powerful as possible –As perfect as possible –As intuitive as possible  Process: –Divide into design teams –Brainstorm design and features, in several rounds, tonight –Choose components for actual design process

The Perfect Phone Project (2) Design Teams are: Team P: Jon, Katie, Scott Team Q: Alvin, Andrew B., Lindsay Team R: Andrew M., Keith, Tony Team S: Anton, Matt, Nawar Team T: Christopher, Joseph, Nareg

The Perfect Phone Project (3)  Move into groups, separating each group from all others as much as possible.  Take a few minutes to read the Chronicle article  Then we’ll think creatively

The Perfect Phone See Thomas Claburn, Information Week, Sep 25, 2007 and Jeffrey R. Young, Chronicle of Higher Education, Feb 27, 2009, Now You Can Track Colleagues and Students on Your Laptop  By perception  By design philosophy  By task  By physical interface

The Imperfect Phone  Which of the imperfections Claburn lists are still present?  Are there other imperfections with your phone?

Imperfect Phone (2) Difficulties with the mobile phone are:  Battery needs frequent recharging  Little software is open source  Little internal storage available  Battery charge indicator is unreliable  Unreliable service coverage  Physical interface constraints: e.g., keys too small  Inability to support Flash, etc.  Slow network speed and bandwidth

Imperfect Phone (3)  Physical button design  Fast obsolescence  No universal applications  Expensive  Lack of standard connectors  Autocorrect overreacts  Recharging requires electrical supply (rather than solar or light)

Imperfect Phone (4)  Lack of software that corresponds to usual desktop  User app submission process complicated for developer

Perfect Phone: Perception  What do you think of when someone starts talking about a perfect phone?  What is your mental model of the device?

Perfect Phone: Perception (2) Features of the Perfect Phone include:  For the future: chip in brain  High bandwidth: instantaneous connections  Multifunctional device integration –Perhaps somewhat limited in scope. Do we need the kitchen sink also? Or should it stay behind?  Customizability: software and hardware  Low power drain  Unlimited storage  Secure

Perfect Phone: Perception (3)  Universal connectors; inductive chargers  Universal wireless connectivity (no wires anywhere)  Indestructible; hence, waterproof  Accurate GPS  Built-in projector  Use anywhere—other countries

Perfect Phone: Design Philosophy  How does the perception of the perfect phone translate to an overall design?  An Analogy: –A toaster should make toast. –A toaster can be easily made to toast more than bread (e.g. bagels, English muffins, –Sometimes the item needing toasted is frozen.

Perfect Phone: Design Philosophy (2) The functionality of the phone should:  Support voice recognition  Provide reminder capability  Support video conferencing  Include easily upgradable, modular hardware  Provide awareness of venue of use –Noisy, poorly lit, precise location

Perfect Phone: Design Philosophy (3)  Be built on open source technology and even FOSS  Have general IM capability  Provide secure access to  Have a sleek design making it less cumbersome to use  Be compatible with charging technology  Contain smart SIM card

Perfect Phone: Physical Interface  What should the physical design of the phone and its physical interface widgets be?

Perfect Phone: Physical Interface (2)  touch screen, needs to be durable  tactile keyboard (flip-up screen); tactile feedback  USB ports; headphone; microphone  fit in pocket and hand  screen—high res, maximize size  no proprietary connectors  easily replaceable battery  stylus

Perfect Phone: Task List  What tasks would you like to accomplish on your Perfect Phone?

Perfect Phone: Task 1. Output from phone to larger device 2. Output from phone to Web 3. Send/receive with properties described above 4. Get directions to address from here 5. Upload and play music 6. Conduct IM sessions 7. Search for things within phone

Perfect Phone: Task (2) 8. Manage contact list 9. Show environment (weather) 10. Backup / secure data 11. Manage calendar / appointments 12. Browse the web 13. Manage voice activation properties 14. Take pictures and manage photo collection 15. Play games

Perfect Phone: Design Task  Each design team chooses three of the fifteen tasks in order of preference. Submit choice by 3/9 –One alternate task can be proposed. –Instructor will assign task based on preference ordering –Important: The teams are designing the user interface for the functionality described, not the implementation of the functionality itself.  Design teams meet Tuesday, 3/10, during class time  Interim design report due by 9:00 p.m. EDT that evening.  Final design report due Wednesday, 3/17

Perfect Phone: DT (2) Being as creative as possible  Develop a task analysis  Use a State Transition Network (see Dix)  Propose a design for the PPh to accomplish the team’s assigned task  Implement a prototype of the design (implement can mean “screen shots” or a running program)  Analyze the prototype in light of the GUEPs and CDs  Use other ideas from course as appropriate to justify your design.  Submit a report with the results of your work.

Perfect Phone: DT (3)  Results should be 5 designs that, when combined, describe a device that is close to a PPh.

To Do  Submit presentation area and article for approval by Monday, March 9. Send area and bibliographic citation by .  Submit choices of perfect phone tasks by Monday, March 9.  Submit (by ) Progress Report 1 by Tuesday, March 10.  Meet as an interface design team on Tuesday, March 10. Submit initial design report by 9:00 p.m. EDT.