[INF43] Lecture 10 Usability and software failure

软件工程 SoftwareEngineering


@ZYX 写于2020年05月12日

Interview and obeservation

  1. tacit knowledge: cannot be desribed


  1. the purpose of these are for you to understand who your users are and you can use them in a couple of different places.
  2. So you create these personas by you need to do some research, a lot of times it’s talking to your customer. And maybe doing some market research about what types of users, there are similar applications and you want to try to find patterns in those usages and create these user groups.
  3. Casual User & Poweful User
    1. Casual User 对产品的需求度不高
    2. Powerful User 对产品需求度很高,而且会用所有functions


  1. 就和story一样
  2. So you see that in a scenario. Often it starts out with a user having a specific goal in mind or specific motivation. What does he want to do. And his emotions

Design guidelines

  1. And when you’re when you’re on a government website, you really need consistency because consistency gives you credibility.
  2. In for the US government in particular it consisted of a visual style guide, which was like font recommendations and color representation recommendations UI components and patterns that were reusable, including code.

Heuristic Evaluation

  1. And the word heuristic just simply means that it’s based on experimentation or evaluation. So your risk evaluation is using principles, based on research to evaluate and improve the usability of the system.
  2. SEE PPT

    Nielsen Evaluation

  3. Visibility of System status
    • Your users should always be kept informed of what’s going on in the system. They should never be left to wonder what the system is doing. I’m sure we’ve all had that experience where
      1. Progress Bars
  4. Match Between System and Real World
    • So users should be able to use systems without learning too much system speaks
  5. User Control and Freedom
    • Things that help users to know where they are and how to get out of them like these hamburger menus, where it shows you where you are and maybe there’s nested menus and you can always see how to go back
      1. Undo and Redo
  6. Consistency and Standards
    • 用标准的设计风格
  7. Error prevention
    • need to be able to help people like go back if they make a mistake. But even better would be if you prevent them from making that mistake in the first place.
      1. 灰按钮
  8. Recognition Rather than Recall
    • Recognition rather than recall this gets again into reducing the user’s memory load, you don’t want to have to make them memorize things in order to use your software.
      1. 字体展示、常用词
  9. Accelerators
  10. Help Users Recognize/Recover from Errors
  11. Help and Documentation

User Testing