Skip to content

HCI final project

Requirements

HCI Final Project

This project is due by 5:00 p.m. on Tuesday, December 14, 2021, and should be done by teamwork. Each team must list the names and IDs of each team member.

This final project is worth 40% to 50% of the overall assignment score in the class. Students who do not work as part of a properly formed group will not receive full credit.

Summary: Evaluate the usability of a website or application and propose a validated redesign of the site or application.

This project has three phases: Evaluate the existing site or application, redesign it to improve the shortcomings you identified (including user tests of the new design). Be sure to read the entire assignment right away so you're aware of everything that's involved.

You will work on this assignment in teams of three or four. We estimate that the increase in coordination and communication necessary in a four-person team roughly equals the decrease in individual workload over a three-person team and we expect that the products of three-person teams will be at least as complete and thorough as the results of four-person teams. In forming your teams, it would be wise to compare schedules, other obligations, and level of commitment to the class; your work will go most easily if all group members are roughly compatible in these respects. All members of the team will receive the same score; it is up to your team to consider each member's views, to work out how to resolve differences and allocate tasks fairly, and to fill in for any team member who becomes unavailable.

What about five-person teams? They are not absolutely prohibited, but we discourage them pretty strongly. Five people make it that much harder to reach group decisions, schedule meetings and user tests, get everyone to review a document, and so on. Everyone on the team receives the same score, as indicated above. Expectations of quantity and quality of work are the same for teams of three, four, or five; there's no formula for scaling a team's product according to team size. Finally, if the teams are all formed and there is one group of two people and one or more teams of five, one of the members of a five-person team will have to join the two-person group to form a three-person team.

Any web site or application poses its own challenges, which your group needs to handle as best it can. You can only test aspects of it that you're actually authorized to use.

when we give page counts here we're referring to single-spaced text in 10- or 12-point type with one-inch margins. We encourage helpful illustrations, but illustrations do not count towards the page limits.

Part I: Evaluate the existing site

  • Determine three or four typical tasks that a user might perform on the site or with the application (e.g., compare the laptop computers available for under $1500 or pay for purchases with a debit card). Choose tasks that are realistic, broadly representative of what users might want to do on the site, and substantial enough that the user can't complete them with just a few clicks in a minute or two. (The design changes you will propose in the next part should be based on the flaws you identify in this evaluation. If you already have in mind some particular changes, choose user tasks now that you think will point up problems that your contemplated changes will address.)
  • Find at least two people who aren't enrolled in our class but who might be typical users of your site or application. Have each person, one at a time, do a walkthrough of the site, attempting to complete each of your three or four tasks. Follow the walkthrough guidelines discussed in class and in the book: Encourage the users to narrate what they're thinking and what problems or questions they're encountering. One team member should encourage the user to talk through the process (using non-judgemental, non-leading prompts); the other(s) should observe and take notes on the difficulties that come up.
  • Write usability aspect reports (UAR)of at least two and at most three pages.

Try to be comprehensive, addressing most of the major flaws, even if that means overlooking minor issues or repeated instances of the same problems. (If a site includes many links that are hard to identify, for example, just say once something like, "Many links, such as the 'Policies' link on the home page, are hard to identify as links because they're not distinguished from other content." Don't list every link that has a problem; that will fill up the available space before you have time to cover most of the important issues.) It's a good strategy to mention some successful aspects of the site, since it will make your report sound less unremittingly critical and thus more palatable to the site management, but your main goal is to propose a redesign so most of your report should address areas for improvement.

Part II: Redesign the site

  • Develop a new design for the site or application, one that improves the areas you identified in your usability evaluation. The changes you propose should mainly be changes that address problems your prior user walkthroughs identified. Don't just make a bunch of changes you think would be a good idea; the point is that your redesign address the problems found in your initial HE or TA user testing. Focus mainly on global issues of navigation and usability; don't spend much of your time polishing details like typefaces and graphics and the wording of the text on the pages.
  • Build a prototype of your new design.
  • Test your prototype, making changes as necessary.
  • Find at least three people who aren't in the class; they don't have to be the same people whom you used before, but they may be. With each person, walk through your prototype, asking the user to perform each of the original three or four tasks and any others that you think are appropriate or necessary. As always, follow the guidelines for working with users.
  • As flaws or improvements become apparent during your user testing, adjust your design and prototype and re-test the changed aspects. Keep iterating until you are satisfied with your design.

Part III: Propose your new design

  • Write a proposal of three to five pages describing your redesign. The major part of the proposal should describe the design and how it improves the usability issues you identified in Part I. Of course you will include illustrations as appropriate.
  • Submit your proposal document via Weizhujiao(微助教https://www.teachermate.com.cn ). Include your usability evaluation from Part I as an appendix. Only one member of the group should do the submission, including the names of all group members. The submitting member should send this document to all the team members right after submitting.
  • Export your prototype in some form (like a web document or a PDF) that will let the reader view the design and trace the links or interactions. Submit that exported prototype via Weizhujiao. Follow the same submitting process as above.

Part IV: Attribution

  • Each team must describes the contributions made by each member of the team. One or two sentences for each member is sufficient. This will help us to know who was responsible for what parts of the work. Every member of the group must** sign this attribution document**. Then scan or photograph the signed document and submit it with the rest of your team's work via Weizhujiao.

Discussion

project: 模拟报警系统

P1 评估现有应用

一个应用：https://www.iqiyi.com/v_19rrxrv4r1.html 找到另一个应用（可执行程序程序/源码最好）

找到三到四个用户可能遇到的问题：如视频播放没有声音，界面不够贴近用户等

找两个用户亲自尝试

写一个UAR报告，2~3页

P2 重构现有应用

P3 描述你的设计

从HE角度切入，找3~4个用户实际体验进行TA

以及和之前问题的改进与呼应之处

写一个proposal，3~5页

P4 分工：分工合作，交叉review

review文档的同学负责把控书写对应文档的同学的质量、进度等，必要可以夺命连环call

  • Task1：前期调研，程序开发完成、打包发布（ddl 11/21），review P3（ddl 11/29）—— 叶文涛
  • Task2：完成P1（找应用11/22；给出大纲11/23；完整书写11/26），review 技术文档 （ddl 11/29）—— 杨枫 任务
  • Task3：完成P3（ddl 11/26），review P1（ddl 11/29）—— 泰合
  • Task4：完成技术文档（1~2页即可，介绍MASR、pyqt等，ddl 11/25），review所有被review后的文档，整理最终文档，形成submission（ddl 12/4）—— 系风

P5 attribution

我会把程序拆分，让大家到时候都“开发”过一部分程序。