Introduction

Purpose

Your goal is to create a design for a software interface.  You will experience the scope of the design process from brainstorming ideas and gathering information about users’ needs to storyboarding, prototyping, and finally, testing and refining your product. As you work on the software interface, you will demonstrate your ability to apply fundamental Human-Computer Interaction principles to interface analysis, design, and implementation. You will be responsible for delivering project components to your professor at several points during the course.

Deliverables

This project should follow the main steps of the first three phases and presentation. Details description and diagrams should be included in each phase.

Phase One:

You will need to decide on an idea for an interface. It could be a web site, a mobile app, an appliance touch screen, etc. Don’t make your idea too broad. Focus on something that solves a problem or fills a need.

Your project idea needs to be sufficiently complex to show your ability to design multiple screens and interaction flows as the user carries out a small number of tasks. For that you need to do the following:

1. Brainstorm ideas. You might want to use a free, online mind-mapping tool like SpiderScribe or Mindomo (Optional). Here are some questions you might want to consider to focus your brainstorming:

0. Think of a service you or your friends use. What’s the biggest avoidable hassle (inconvenience) customers must endure?

0. What happens in your daily routine that is complex or confusing? How could you simplify it?

0. Think of a domain that interests you: shopping, elementary education, exercise, social media, etc. What possibilities are there to do something new or better? What might be redesigned for newer or different technologies like smart phones or gaming platforms?

1. Narrow your choices down to one idea.

1. Write a brief description of the problem, including the following main points:

2. The Problem

2. Why It’s Interesting

2. Main Users Affected

2. Current Solutions (if any)

2. Make a list of the needs/goals/tasks you observed (at least 10). Group and organize this list as appropriate.

2. A brief literature review of at least two literature resources related to your idea. The resources can include peer reviewed journal and conference papers, books, product manuals and product websites. All resources must be cited in APA style.

Phase Two:

A high-fi prototype shows the main elements of a user interface connected and working together using a software tool. Its purpose is to get a quick clear and precise look of the final interface, which provides both designer and user the ability to interact with the system and check some of its functions. You can use a high-fi prototype to identify usability issues such as confusing paths, bad terminology, layout problems, and missing feedback. Please note that your prototype does not need to be as extensive, 3-5 interfaces to show the main functions will be sufficient. Your prototype should allow people to navigate from screen to screen, recover from errors, and change their choices.  Don’t try to show every possible action or detail. Focus on the main interactions.

1. Using any software prototyping application, create a prototype for your interfaces following the instructions above.

1. Write a description of each of the interfaces (include screenshots) explaining the following:

1. The purpose of the interface.

1. The main functions in the interface.

1. The previous and next status of each action.

1. The layout of the interface.

Phase Three:

1. You will conduct a heuristic evaluation of your prototype with expert users. Your classmates in this course would make great expert reviewers. You should use Jakob Nielsen’s Ten Usability Heuristics or another set of heuristics approved by your professor.

0. Allow at least 3 expert users to use the high-fi prototype.

0. The purpose of the heuristics is to guide your expert users and help them find as many different types of usability issues as possible.

0. Instruct your experts to describe each issue noted as specifically as possible. Allow the expert to explore the interface and follow any paths.

1. Make sure to practice with your prototype so that you can operate it effectively and not waste time. Doing several practice runs or walkthroughs will help you identify missing pieces and dead ends.

1. It would be a good idea to do this testing in groups. One person can be the expert tester while another works the prototype and the others take notes. Then, everyone can switch roles until all participants have been experts and had a chance to test their designs.

1. Review the feedback you got from your reviewers.

1. Write a summary of the prototype testing results describing what worked and what did not. In addition to a list of specific changes you want to make to your interface. This summary must include;

4. Average subjective satisfaction of reviewers

4. Number and details of terms/metaphors unfamiliar to reviewers

4. Number and details of action sequences considered confusing lengthy by reviewers

4. Number and details of inputs/outputs not understood by reviewers

And you can add any further items of interest from review activity.

Phase Four:

Prepare a presentation of your project idea describing all of the following:

1. Background: Introduce the idea of project you chose including problems with existing interface and its possible impact.

1. Summary of Work: Explaining what your implemented changes to interface accomplish, how you designed it, and what possible improvements were brought in comparison to problems you listed earlier.

1. Features: Describe of the main interface elements and features you implemented

1. Reviewer Testing: Describe briefly the reviewer evaluation results as you compiled those in your report including all problems identified.

1. Evolution: Describe how your implemented interface makes the system better from perspective of usability and user satisfaction. List all improvements experienced by reviewers or other sources who evaluated your interface. Include graphics to show before and after.

1. Conclusion: Briefly discuss the conclusion and any future improvements you can suggest about interface of your selected system. Address problems that remain and what your next steps for the product might be if you were to continue further working on same system.

you will present this in front of your class at the end of the semester, your instructor will provide you with the time/date for your presentation.