csc 8570 -- usi class meeting 7 february 24, 2009
TRANSCRIPT
CSC 8570 -- USICSC 8570 -- USI
Class Meeting 7Class Meeting 7
February 24, 2009 February 24, 2009
Apologies for lack of celebration for Apologies for lack of celebration for Mardi GrasMardi Gras
Important ConceptsImportant ConceptsAs listed on the one-minute surveyAs listed on the one-minute survey GOMS analysisGOMS analysis User interface assessment with GUEPs and CDsUser interface assessment with GUEPs and CDs Specific GUEPS and CDs including Consistency, Specific GUEPS and CDs including Consistency,
KISS, ViscosityKISS, Viscosity Complexity of UI designComplexity of UI design Keystroke level analysis, models (e.g. Fitts’ Law), Keystroke level analysis, models (e.g. Fitts’ Law),
and notationand notation Semantic and syntactic analysis of widgetsSemantic and syntactic analysis of widgets Mental modelsMental models Learning tools: concept maps, research paper Learning tools: concept maps, research paper
reading processreading process
Article PresentationsArticle Presentations Choose one of the three topic areas Choose one of the three topic areas
(defined below)(defined below) Find an interesting recent (last 4 years) Find an interesting recent (last 4 years)
paper in the areapaper in the area Prepare a 15 minute presentation of the Prepare a 15 minute presentation of the
paperpaper– The backgroundThe background– The experimentThe experiment– The resultsThe results– The critiqueThe critique– The relationship to other papers or conceptsThe relationship to other papers or concepts
Article Presentations (2)Article Presentations (2)
Subject areas:Subject areas: Intelligent user interfacesIntelligent user interfaces (IUI) and (IUI) and
especially the implementation and especially the implementation and evaluation of features.evaluation of features.
Computer supported collaborative work Computer supported collaborative work (CSCW)(CSCW) and especially the design and and especially the design and functionality of collaboration systemsfunctionality of collaboration systems
Participatory design Participatory design as a software as a software engineering tacticengineering tactic– Users involved at all stages of system Users involved at all stages of system
developmentdevelopment
Course planningCourse planning 3/3 – 3/3 – Spring breakSpring break 3/9 – 3/9 –
Choice of research article for presentation with area and Choice of research article for presentation with area and bibliographic information due, via emailbibliographic information due, via email
Perfect Phone design team task choice due, via emailPerfect Phone design team task choice due, via email 3/10 – Interface design team meetings3/10 – Interface design team meetings
Preliminary Perfect Phone design report due at end of classPreliminary Perfect Phone design report due at end of class Research project Progress Report 1 dueResearch project Progress Report 1 due
3/17 – 3/17 – St. Patrick’s Day, but class meets.St. Patrick’s Day, but class meets. Final Perfect Phone design report dueFinal Perfect Phone design report due
3/24 – 3/24 – Research project Progress Report 2 dueResearch project Progress Report 2 due
3/31 – Paper presentations: Intelligent user 3/31 – Paper presentations: Intelligent user interfacesinterfaces
Course planning (2)Course planning (2)
4/7 – Paper presentations: Computer supported 4/7 – Paper presentations: Computer supported collaborative workcollaborative work
Draft research report, part 1, dueDraft research report, part 1, due
4/14 – Paper presentations: Participatory design4/14 – Paper presentations: Participatory design Draft research report, part 2, due Draft research report, part 2, due
4/21 – 4/21 – 4/28 – Research Project Presentations4/28 – Research Project Presentations
Final research report dueFinal research report due
5/5 – Final Exam5/5 – Final Exam Research project poster abstract and design dueResearch project poster abstract and design due
Research ProjectResearch Project
1.1. Progress reports Progress reports (PR 1 due 3/10; PR 2 due (PR 1 due 3/10; PR 2 due 3/24)3/24)
2.2. Report drafts Report drafts (Sections 1&2 due 4/7; (Sections 1&2 due 4/7; Sections 3-5 due 4/14)Sections 3-5 due 4/14)
3.3. Final written report Final written report (Due 4/28)(Due 4/28)
4.4. Oral report Oral report (Given 4/28)(Given 4/28)
5.5. Poster abstract and design Poster abstract and design (Due 5/5)(Due 5/5)
The Perfect Phone ProjectThe Perfect Phone Project
Goal: Create a user interface designGoal: Create a user interface design– As powerful as possibleAs powerful as possible– As perfect as possibleAs perfect as possible– As intuitive as possibleAs intuitive as possible
Process: Process: – Divide into design teamsDivide into design teams– Brainstorm design and features, in several Brainstorm design and features, in several
rounds, tonightrounds, tonight– Choose components for actual design processChoose components for actual design process
The Perfect Phone Project (2)The Perfect Phone Project (2)
Design Teams are:Design Teams are:
Team P: Jon, Katie, Scott Team P: Jon, Katie, Scott
Team Q: Alvin, Andrew B., LindsayTeam Q: Alvin, Andrew B., Lindsay
Team R: Andrew M., Keith, TonyTeam R: Andrew M., Keith, Tony
Team S: Anton, Matt, NawarTeam S: Anton, Matt, Nawar
Team T: Christopher, Joseph, NaregTeam T: Christopher, Joseph, Nareg
The Perfect Phone Project (3)The Perfect Phone Project (3)
Move into groups, separating each Move into groups, separating each group from all others as much as group from all others as much as possible.possible.
Take a few minutes to read the Take a few minutes to read the ChronicleChronicle article article
Then we’ll think creativelyThen we’ll think creatively
The Perfect PhoneThe Perfect Phone
See Thomas Claburn, See Thomas Claburn, Information Week, Information Week, Sep 25, 2007Sep 25, 2007
and Jeffrey R. Young, and Jeffrey R. Young, Chronicle of Higher Education,Chronicle of Higher Education, Feb Feb 27, 2009, Now You Can Track Colleagues and Students 27, 2009, Now You Can Track Colleagues and Students on Your Laptopon Your Laptop
By perceptionBy perception By design philosophyBy design philosophy By taskBy task By physical interfaceBy physical interface
The Imperfect PhoneThe Imperfect Phone
Which of the imperfections Claburn Which of the imperfections Claburn lists are still present?lists are still present?
Are there other imperfections with Are there other imperfections with your phone?your phone?
Imperfect Phone (2)Imperfect Phone (2)
Difficulties with the mobile phone are:Difficulties with the mobile phone are: Battery needs frequent rechargingBattery needs frequent recharging Little software is open sourceLittle software is open source Little internal storage availableLittle internal storage available Battery charge indicator is unreliableBattery charge indicator is unreliable Unreliable service coverageUnreliable service coverage Physical interface constraints: e.g., keys Physical interface constraints: e.g., keys
too smalltoo small Inability to support Flash, etc.Inability to support Flash, etc. Slow network speed and bandwidthSlow network speed and bandwidth
Imperfect Phone (3)Imperfect Phone (3)
Physical button designPhysical button design Fast obsolescenceFast obsolescence No universal applicationsNo universal applications ExpensiveExpensive Lack of standard connectorsLack of standard connectors Autocorrect overreactsAutocorrect overreacts Recharging requires electrical supply Recharging requires electrical supply
(rather than solar or light)(rather than solar or light)
Imperfect Phone (4)Imperfect Phone (4)
Lack of software that corresponds to Lack of software that corresponds to usual desktopusual desktop
User app submission process User app submission process complicated for developercomplicated for developer
Perfect Phone: PerceptionPerfect Phone: Perception
What do you think of when someone What do you think of when someone starts talking about a perfect phone?starts talking about a perfect phone?
What is your mental model of the What is your mental model of the device?device?
Perfect Phone: Perception (2)Perfect Phone: Perception (2)
Features of the Perfect Phone include:Features of the Perfect Phone include:
For the future: chip in brainFor the future: chip in brain High bandwidth: instantaneous connectionsHigh bandwidth: instantaneous connections Multifunctional device integrationMultifunctional device integration
– Perhaps somewhat limited in scope. Do we need the Perhaps somewhat limited in scope. Do we need the kitchen sink also? Or should it stay behind? kitchen sink also? Or should it stay behind?
Customizability: software and hardwareCustomizability: software and hardware Low power drainLow power drain Unlimited storageUnlimited storage SecureSecure
Perfect Phone: Perception (3)Perfect Phone: Perception (3)
Universal connectors; inductive Universal connectors; inductive chargerschargers
Universal wireless connectivity (no Universal wireless connectivity (no wires anywhere)wires anywhere)
Indestructible; hence, waterproofIndestructible; hence, waterproof Accurate GPSAccurate GPS Built-in projectorBuilt-in projector Use anywhere—other countriesUse anywhere—other countries
Perfect Phone: Design PhilosophyPerfect Phone: Design Philosophy
How does the perception of the How does the perception of the perfect phone translate to an overall perfect phone translate to an overall design?design?
An AnalogyAn Analogy: : – A toaster should make toast.A toaster should make toast.– A toaster can be easily made to toast A toaster can be easily made to toast
more than bread (e.g. bagels, English more than bread (e.g. bagels, English muffins, muffins,
– Sometimes the item needing toasted is Sometimes the item needing toasted is frozen. frozen.
Perfect Phone: Design Philosophy (2)Perfect Phone: Design Philosophy (2)
The functionality of the phone should:The functionality of the phone should: Support voice recognitionSupport voice recognition Provide reminder capabilityProvide reminder capability Support video conferencingSupport video conferencing Include easily upgradable, modular Include easily upgradable, modular
hardwarehardware Provide awareness of venue of useProvide awareness of venue of use
– Noisy, poorly lit, precise locationNoisy, poorly lit, precise location
Perfect Phone: Design Philosophy (3)Perfect Phone: Design Philosophy (3)
Be built on open source technology Be built on open source technology and even FOSSand even FOSS
Have general IM capabilityHave general IM capability Provide secure access to emailProvide secure access to email Have a sleek design making it less Have a sleek design making it less
cumbersome to usecumbersome to use Be compatible with charging Be compatible with charging
technologytechnology Contain smart SIM cardContain smart SIM card
Perfect Phone: Physical InterfacePerfect Phone: Physical Interface
What should the physical design of What should the physical design of the phone and its physical interface the phone and its physical interface widgets be?widgets be?
Perfect Phone: Physical Interface (2)Perfect Phone: Physical Interface (2)
touch screen, needs to be durabletouch screen, needs to be durable tactile keyboard (flip-up screen); tactile tactile keyboard (flip-up screen); tactile
feedbackfeedback USB ports; headphone; microphoneUSB ports; headphone; microphone fit in pocket and handfit in pocket and hand screen—high res, maximize sizescreen—high res, maximize size no proprietary connectorsno proprietary connectors easily replaceable batteryeasily replaceable battery stylusstylus
Perfect Phone: Task ListPerfect Phone: Task List
What tasks would you like to What tasks would you like to accomplish on your Perfect Phone?accomplish on your Perfect Phone?
Perfect Phone: Task Perfect Phone: Task
1.1. Output from phone to larger deviceOutput from phone to larger device2.2. Output from phone to WebOutput from phone to Web3.3. Send/receive email with properties Send/receive email with properties
described abovedescribed above4.4. Get directions to address from hereGet directions to address from here5.5. Upload and play musicUpload and play music6.6. Conduct IM sessionsConduct IM sessions7.7. Search for things within phoneSearch for things within phone
Perfect Phone: Task (2) Perfect Phone: Task (2)
8.8. Manage contact listManage contact list9.9. Show environment (weather)Show environment (weather)10.10. Backup / secure dataBackup / secure data11.11. Manage calendar / appointmentsManage calendar / appointments12.12. Browse the webBrowse the web13.13. Manage voice activation propertiesManage voice activation properties14.14. Take pictures and manage photo Take pictures and manage photo
collectioncollection15.15. Play gamesPlay games
Perfect Phone: Design TaskPerfect Phone: Design Task Each design team chooses three of the fifteen Each design team chooses three of the fifteen
tasks in order of preference. Submit choice by 3/9tasks in order of preference. Submit choice by 3/9– One alternate task can be proposed.One alternate task can be proposed.– Instructor will assign task based on preference orderingInstructor will assign task based on preference ordering– Important: Important: The teams are designing the The teams are designing the user user
interface interface for the functionality described, not the for the functionality described, not the implementation of the functionality itself.implementation of the functionality itself.
Design teams meet Tuesday, 3/10, during class Design teams meet Tuesday, 3/10, during class timetime
Interim design report due by 9:00 p.m. EDT that Interim design report due by 9:00 p.m. EDT that evening.evening.
Final design report due Wednesday, 3/17Final design report due Wednesday, 3/17
Perfect Phone: DT (2)Perfect Phone: DT (2)
Being as creative as possibleBeing as creative as possible Develop a task analysisDevelop a task analysis Use a State Transition Network (see Dix)Use a State Transition Network (see Dix) Propose a design for the PPh to accomplish the Propose a design for the PPh to accomplish the
team’s assigned taskteam’s assigned task Implement a prototype of the design (implement Implement a prototype of the design (implement
can mean “screen shots” or a running program)can mean “screen shots” or a running program) Analyze the prototype in light of the GUEPs and Analyze the prototype in light of the GUEPs and
CDsCDs Use other ideas from course as appropriate to Use other ideas from course as appropriate to
justify your design.justify your design. Submit a report with the results of your work.Submit a report with the results of your work.
Perfect Phone: DT (3)Perfect Phone: DT (3)
Results should be 5 designs that, Results should be 5 designs that, when combined, describe a device when combined, describe a device that is close to a PPh.that is close to a PPh.
To DoTo Do
Submit presentation area and article for Submit presentation area and article for approval by Monday, March 9. Send area approval by Monday, March 9. Send area and bibliographic citation by email.and bibliographic citation by email.
Submit choices of perfect phone tasks by Submit choices of perfect phone tasks by Monday, March 9.Monday, March 9.
Submit (by email) Progress Report 1 by Submit (by email) Progress Report 1 by Tuesday, March 10.Tuesday, March 10.
Meet as an interface design team on Meet as an interface design team on Tuesday, March 10. Submit initial design Tuesday, March 10. Submit initial design report by 9:00 p.m. EDT.report by 9:00 p.m. EDT.