Scribd
Upload
60 views

HCI Assignment 3

This document outlines the steps for an assignment on software engineering that focuses on applying an interactive design process and evaluating usability. It involves: 1) Defining requirements, users, and initial ideas for an interface. 2) Creating a low-fidelity paper prototype and evaluating it through user testing and heuristics. 3) Building a high-fidelity prototype and conducting a usability study through user testing and observations. 4) Writing a final report analyzing the design process, evaluation results, and conclusions.

Uploaded by

Laiba Iftikhar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
60 views

HCI Assignment 3

This document outlines the steps for an assignment on software engineering that focuses on applying an interactive design process and evaluating usability. It involves: 1) Defining requirements, users, and initial ideas for an interface. 2) Creating a low-fidelity paper prototype and evaluating it through user testing and heuristics. 3) Building a high-fidelity prototype and conducting a usability study through user testing and observations. 4) Writing a final report analyzing the design process, evaluation results, and conclusions.

Uploaded by

Laiba Iftikhar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

UNIVERSITY OF ENGINEERING AND TECHNOLOGY, TAXILA

FACULTY OF TELECOMMUNICATION AND INFORMATION ENGINEERING

SOFTWARE ENGINEERING DEPARTMENT

Assignment 03(Due date:Will discuss in class)

CLO 2: Apply an interactive design process to small sized systems.


CLO 3: Evaluate the usability of a software user interface.
Total Marks: 30

Step 01: Requirements, Users, Initial Ideas

 Interface / System requirements - I am interested in the interface, not the backend so


please focus on the user-facing components and don't get caught up in databases or
things like that.
 Users, context, environment - who are your users? What is the environment and
context in which they are operating? Do they have special needs?
 Tasks - what are the main tasks your users will be performing within the system?
 System Description - a general description of what you are going to build.
 Sketch - a physical sketch of what you're going to build. Paper, hand drawing of poor
quality is fine.
 List of features, the design decisions that drove your plan to include them, and support
from heuristics, guidelines, and other HCI principles to support your decisions.

Step 02: Low-Fidelity Prototype

I mean it when I say low fidelity. Don't try to turn in a half-made website or app for this. Do it
on paper or use super basic materials if you are building an object.

You should have your main features implemented on a paper prototype. Perform both a
cognitive walkthrough, do a heuristic evaluation, and have one outside person work with your
paper prototype (2 people must do this if you are in a group).

Report out on your evaluation. Include a discussion of design points that need to be fixed in
the next prototype, how you found them, and how you plan to change them. Include photos
your paper prototype.

Step 03: High-Fidelity Prototype

Build a high-fidelity prototype, Using a refined list of tasks, have at least 2 people act as
subjects as you perform a usability study with your prototype. Use two different observation
methods. If you are in a group, you must have 4 subjects and use all three observation methods
at least once. Conduct a post-test interview with each subject.

This should not be a full report- we already know why you have your tasks. Instead, it should
describe the protocol you used for the usability study, report on the observations and your
analysis of the weaknesses, and list points you plan to improve moving forward.

You will receive no points if you do not have a fully functional, bug-free prototype Do not
show up with something half-done.
HCI 20-SE Engr. Maria Andleeb
UNIVERSITY OF ENGINEERING AND TECHNOLOGY, TAXILA
FACULTY OF TELECOMMUNICATION AND INFORMATION ENGINEERING

SOFTWARE ENGINEERING DEPARTMENT

Your analysis must be included in your final document (discussed below).

Step 05:Final Document

Your final paper should have the following:

 Description of your project - what did you build and what does it do.
 User Analysis - Who are your users, what is their context for interaction, what (if
anything) is unique about their environment?
 Feature Analysis - What are the major features and why are they there? How do they
serve your users
 Design Process - explain your prototypes, testing, and design evolution. Use the text
you've already written, but polish it and make it fit nicely in this final report.
 Quantitative Evaluation - show the results from the in-class quantitative evaluation.
How did you perform relative to others? Which tasks did you do well on? Which
usability measures? Why do you think your performance was better/worse? What
changes did you make as a result? Use statistical analysis where appropriate.
 Discussion - can you draw any generalizable conclusions for people designing for
special populations? Does the paranormal present a particular challenge in interface
design? Does the environment significantly affect design decisions in a way that would
carry over into other domains?

Marks Distribution:

 50% for step 01 to Step 04


 50% for final written report
a. 80% for quality of analysis, including thorough and proper application of HCI
principles
b. 20% for quality of writing.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

HCI 20-SE Engr. Maria Andleeb

You might also like