Hcsd talk ibm

426 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
426
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • You can only understand wetness as water interacts with the environmentYou can only test the effectiveness of your system as people interact with it
  • ISR: go see their table
  • But you do testing, right? Then why does this still happen? The answer is that we need to go beyond testing, towards human-centered software design (something about human-tolerated vs. human-centered)
  • Several fictitious descriptions of people in the market segmentSomeone you can imagineHelps you make decisions along the way
  • CaseTrack: student project on keeping records for medical students
  • Like a use case, but more story-likeShort story about the persona using some of the functionalityGoal of the user, setting of usage, some of the steps
  • Visual representation of task flowDifferent organizations/people appear in the lanesFlow chart across lanes
  • Supporting the current workflow is important!
  • They include people and contextJust enough detail to get the point acrossThree to five panels (per feature)
  • Supporting the current workflow is important!
  • A static display of the interactionCan evaluate things across areasConsistencyNo dead ends
  • Hcsd talk ibm

    1. 1. Human Centered Software Design If it doesn’t work for people, it doesn’t work! (And now for something completely different…)Created by: Hadar Ziv, Judy Olson, Bart KnijnenburgUniversity of California Irvine
    2. 2. About MeBart Knijnenburg– Current: UC Irvine – Institute for Software Research – Privacy and personalization– TU Eindhoven – Human Technology Interaction– Carnegie Mellon University – Human-Computer Interaction Institute@usabart -- www.usabart.nl
    3. 3. Presentation OutlineIntroduction and motivationHCSD: Augmenting software engineering with HCDOverview of HCD methodsSuccess storiesQuestions and Discussion
    4. 4. Unstoppable Innovation Moore’s Law0 18 36 54 72
    5. 5. Unstoppable Innovation
    6. 6. Unstoppable Innovation “Threshold of Frustration” After a certain point technology gets so complex that it becomes too frustrating to use
    7. 7. Unstoppable Innovation
    8. 8. Hoping (and testing)… with people!Two versions ofbarackobama.com– A/B testing– Different… – Photo (rally, family, …) – Button (sign up, learn more, …)We have a winner!– The second version… – Collected more email addresses – $ 60 000 000 additional campaign dollars!
    9. 9. Usability is essential… Expensive, safety- critical technology – Tested with real people! Examples: – Medical devices
    10. 10. Usability is essential… Expensive, safety- critical technology – Tested with real people! Examples: – Medical devices – Nuclear power plant control rooms
    11. 11. Usability is essential… Expensive, safety- critical technology – Tested with real people! Examples: – Medical devices – Nuclear power plant control rooms – Airplane cockpits
    12. 12. Usability (UCD) works!User-centered designworks– Simple– Inexpensive– Higher sales– Higher satisfactionWhy is it not used?– Printers?–
    13. 13. Usability (UCD) works!User-centered designworks– Simple– Inexpensive– Higher sales– Higher satisfactionWhy is it not used?– Printers?– Car stereos?–
    14. 14. Usability (UCD) works!User-centered designworks– Simple– Inexpensive– Higher sales– Higher satisfactionWhy is it not used?– Printers?– Car stereos?– Tax forms?
    15. 15. Unstoppable Innovation Moore’s Law Mooore! More! Moooore! Moore!0 2 4 6 8
    16. 16. Is this your software? Very likely…
    17. 17. How can we solve this problem? Answer: Human Centered Software Design!
    18. 18. The Software Iterative Model Business Modeling Requirements Analysis & Design Implementation Test Deployment Preliminary Iter. Iter. Iter. Iter. Iter. Iter. Iter. Iteration(s) #1 #2 #n #n+1 #n+2 #m #m+1
    19. 19. Who here is doing this? What is wrong with this?Business Modeling Requirements Analysis & Design Implementation Test User Test Deployment Preliminary Iter. Iter. Iter. Iter. Iter. Iter. Iter. Iteration(s) #1 #2 #n #n+1 #n+2 #m #m+1
    20. 20. Testing at ALL stages User Test Preliminary Iter. Iter. Iter. Iter. Iter. Iter. Iter. Iteration(s) #1 #2 #n #n+1 #n+2 #m #m+1
    21. 21. More than just testing User Requirements Interviews and Observations Personas Scenarios Swimming Lane DiagramsInteraction Analysis & Design Storyboards Design guidelines Site map Mockups User Test Heuristic Evaluation User tests Preliminary Iter. Iter. Iter. Iter. Iter. Iter. Iter. Iteration(s) #1 #2 #n #n+1 #n+2 #m #m+1
    22. 22. HCSD: A Blended Model Business Modeling User Requirements RequirementsInteraction Analysis & Design Analysis & Design Implementation Test User Test Deployment Preliminary Iter. Iter. Iter. Iter. Iter. Iter. Iter. Iteration(s) #1 #2 #n #n+1 #n+2 #m #m+1
    23. 23. HCSD: A Blended ModelProcess of designing from the user’sperspective– Does the right thing– Is easy to learn and use– Is satisfyingBeyond business goals, fancy features, andtechnological capabilities
    24. 24. Informatics at UC IrvineUniversity of California, Irvine– The “Best UC” in “The OC” (Orange County, CA)– Top (#1) university in the US and #4 worldwide in a ranking of universities “under 50” (2012)Bren School of Information and ComputerSciences– The only CS/ICS school in the UC system– Multiple degrees, including a major in Informatics
    25. 25. HCSD at InformaticsCapstone senior design project– Year-long (3 quarters)– Required for the Informatics major– Develop software for real needs of real users and stakeholders
    26. 26. HCSD at UC IrvineSoftware engineering Human-Centered Design (HCD)– Business and software – Requirements requirements – Interviews & – Scenarios, use cases, user observations, Personas, Scena stories, activity diagrams rios, Swimming lanes– Software analysis and design – HC analysis and design – OOAD, UML, MVC – Site maps, Storyboards, Guidelines– Implementation , Mockups – Java coding, .Net/C#, PHP/MySQL, – HC testing Python, Ruby – Heuristic evaluation, User testing– Software Testing– Project management
    27. 27. Human Centered Design Methods An Overview
    28. 28. Human Centered Design MethodsInterviews and observations of end usersPersonas UserScenarios RequirementsSwimming Lane DiagramsStoryboardsDesign guidelines InteractionSite Map / Generalized Transition Network Analysis &Mockup DesignHeuristic EvaluationUser testing User Testing
    29. 29. Interviews and observationsOn site– “to see”Watch– Tacit knowledge
    30. 30. PersonasA user-archetype– The “embodiment” of user needs, goals, desires and limitations– See the real purpose behind requirementsUseful during design– What would George do?– How would Sharon use this feature?During user testing– Bring in 3 Maries– What tasks does she want to accomplish?
    31. 31. CaseTrak: Persona Angela Lee – 28 year old resident physician at the UCI Medical Center – passionate about becoming a better physician – loves working in the Emergency Department – Enthusiastic about the potential of the new Electronic Medical Records (EMR) – Used Merlin as a student, but didn’t like it because the system took up a lot of her limited free time – She prefers going home over staying longer at work to enter required case data into one of the computer stations
    32. 32. ScenariosStory of use with the new product– Leads well into use cases– Focused on the why of each use caseCompanies do this successfully– One of the main tools of the Gmail teamOur students do this successfully
    33. 33. CaseTrak: ScenarioWhile eating lunch, Angela uses the new app enterinformation from a few of her cases todayShe grabs her chart notes and starts the applicationThe app makes data entry a lot faster: it is structuredand requires less free typing than the Merlin systemFor example, there are fields for acuity, involvementlevel, age and gender, with all the options givenShe loves that CaseTrak saves her case information, soshe can go back and add a secondary diagnosisWhile her peers are stuck in front of the Merlin systemafter work, she’ll be on her way home to relax
    34. 34. Swimming Lane DiagramsIntroduce the software design into thescenario– What is the user’s workflow?– What components are needed to support this workflow?– How does the user interact with these components?Invaluable for “groupware”!
    35. 35. CaseTrak:Supervising Physician Swimming Lane Diagram Retrieve Cases for Review
    36. 36. StoryboardsIntroduce the interface design into thescenario– How does the user interact with the system in each step of her workflow?– How can we support and improve their current workflow?
    37. 37. CaseTrak: Storyboard
    38. 38. CaseTrak: Storyboard
    39. 39. Generalized Transition Network (GTN)Integrate all storyboards into one systemdiagram– A “screenshot” of each step in the interaction– All possible transitions between stepsUseful for reflection– “Remote” features, “dead ends”, infinite loops
    40. 40. CaseTrak: GTN
    41. 41. Mockups (using Balsamiq)
    42. 42. CaseTrak: Mockups (before testing)
    43. 43. Design Guidelines
    44. 44. Heuristic Evaluation– Visibility of system status– Match system words to the real world– User control and freedom– Consistency and standards– Error prevention– Recognition rather than recall– Accelerators– Minimalist design– Help users recognize and recover from errors– Help and documentation
    45. 45. User Testing
    46. 46. CaseTrak: Mockups (after testing)
    47. 47. Human Centered Design MethodsInterviews and observations of end usersPersonas UserScenarios RequirementsSwimming Lane DiagramsStoryboardsDesign guidelines InteractionSite Map / Generalized Transition Network Analysis &Mockup DesignHeuristic EvaluationUser testing User Testing
    48. 48. What do I get in return? Profit! Profit! Profit!
    49. 49. Apple knows…
    50. 50. Example: breastcancer.org
    51. 51. Return on InvestmentWhen using HCD well– Sales increase by 100% – It doubles– Traffic count increases by 150% – More than doubles– User performance increase by 160% – Cuts time by more than half Nielsen & Gilutz 2006
    52. 52. HCSD at UC Irvine “This is a jewel at UCI…I feel very lucky to be involved…” (Stew Sutton, Aerospace Corp.)
    53. 53. HCSD at UC Irvine“It is probably the most useful class I’ve taken at UCI…” (A student)
    54. 54. SummaryUsability works!– If it doesn’t work for people, it doesn’t work!HCD Benefits:– Traffic/Sales increase– User happiness/User productivity increase– Customer retention/Customer loyalty increaseHow?– HCD Methods– Easy to integrate in existing software engineering processes
    55. 55. Thank you!We teach this integrated process/lifecycleOur students follow it during a year longcapstone course at UCI– CaseTrak, other projects successfulContact us if you’d like to:– Learn more about how it (usability) works– Participate in UCI Informatics capstone project courseziv@ics.uci.edu jsolson@uci.edu bart.k@uci.edu

    ×