Assignment 05 | usability inspection of a design developed by one of your classmates
Design and Implementation of an Interface Prototype
This series of assignments involves designing a prototype of an interface for an information system and developing a description of that interface.
The design process involves six components
- identifying and describing the intended users of the system | due on 29 Jan | worth 10%
- identifying and describing the essence of the task to be supported by the system | due on 26 Feb | worth 20%
- making justifiable decisions about the design | due on 24 Mar | worth 20%
- graphical overview of the system and a prototype of the interface | due on 07 Apr | worth 20%
- usability inspection of a design developed by one of your classmates | due on 16 Apr | worth 10%
Prior to Wednesday, 10 Apr 2014, you will be asked to select one of the class projects in which you are particularly interested and/or about which you are particularly knowledgeable. Prior to that date, you will have had a chance to see the prototypes demonstrated. I will assign you to evaluate one of the projects. Each project will be evaluated by at least one class member; each class member will evaluate one project.
Look over the prototypes below.
If you have a preference, send me a note and you will evaluate the project of your choosing.
You can see your match at this link
- Web Interfaces
- StrongLinks Social Network Web Site
- Activate Good web Site
- Beacon WealthCare Web Site
- Lifetime Library Web Site
- Daily Tar Heel Web Site
- Project Gutenberg Web Site
- Institute for Anacylcosis Web Site
- Digital Imaging Course Web Environment
- International Student and Scholar Services Web Site
- Summit Church Web Site
- Home-Gym Equipment Web Store Site
- Registering Social Media Accounts with Member of Congress tool
- Intranet Interface
- Mobile App Interfaces
- Google Glass App Interface
- Dashboard Interface
- Driver-centered Auto Interface
- Automobile Dashboard Interface
For the evaluation, you will have access to the complete documentation of the design. You may also communicate with the designer concerning questions of clarification. In addition, the designer may ask that the evaluator consider focusing on particular areas of interest or concern.
- Review the project documentation, paying special attention to the goal of the system, the scope of the user group, and the task to be supported. Also, be sure that you understand the scope of the prototype itself.
- Identify five strengths/weaknesses to be the focus of your evaluative comments. Of the five, one or two points should focus on strengths of the design, i.e., aspects that should be retained in the design. The remaining three or four points should focus on problems in the design, i.e., aspects that could be improved.
- For each of the five points:
- Describe the aspect of the design being discussed, and state whether it is a strength or a weakness; and
- support your evaluation with a rationale, based on the user analysis, the task analysis, and the literature, as appropriate. Each point must be supported with a general principle, a specific guideline, or research findings published in the literature.
This task is due on Wednesday, 16 Apr 2014. An electronic version of your comments should be provided to the prototype designer on or before that day.
- a thoughtful response to that inspection | due on 02 May | worth 10%