Fall2006.CSIS672Homework1Template History

Hide minor edits - Show changes to output

Deleted lines 79-86:

----

* Your report should have sections that follow the above outline. Include figures and illustrations that give '''substantive''' help to the reader in understanding the user interface, the usability breakdown, and your analysis. You are encouraged to '''use screen snapshots''' and other graphics (e.g., diagrams) for elucidation. However, '''avoid decorative graphics/pictures'''.

* As per course collaboration policy, there should be no discussion of any kind about this assignment (and possible solutions) with any person other than the instructor. '''You are not allowed to discuss/look at someone else’s solution (including material in books and the Internet) or show your solution to someone else other than the instructor'''.

* Include '''references''' on materials (other than the textbooks and handouts) you consulted to do the assignment.
Added lines 1-87:
/**
* Author: {Your Name} \\
* Course: CSIS 672, Section 90 \\
* Assignment: Homework 1 \\
* Due Date: {The assignment's due date} \\
* \\
* Certification of Authenticity {include one of the following}: \\
* \\
* I certify that this work is entirely my own. \\
* \\
* I certify that this work is my own, but I received \\
* some assistance from: {Name(s), References, etc.} \\
*/

----

!Name of System you are Evaluating

!!Introduction

Describe your first impressions:

!!!Good

What is good and bad about this interface?

* good 1
* good 2
** good 2.1
* good 3
* ...etc.

!!!Bad

What is good and bad about the user experience it produces?

...

%center% %rframe margin-right=8px margin-bottom=8px% Attach:demo.jpg | [-'''Here is an example of how to add\\
an image.'''-]

!!Functionality

Describe the system's functionality.

Provide concise, yet complete description (one to three sentences).

!! User Tasks

List user tasks.

What would a typical user want to accomplish? (''Remember'': Focus on user tasks, not system features.)

Is the functionality greater, equal, or less than what the user needs?

!! Usability Breakdown

Describe a usability breakdown caused by the system's design.

* The problem should be one that came up as a difficulty in getting the system do what you wanted, due to flaws in the design.
* '''Note:''' We are not interested in cases where the system crashed, or the program just didn't work.
* The example of breakdown can be a situation where you did something that created a problem, or you failed to find the way to do something.
* Give a few sentences ("bullet points") characterizing the breakdown from the point of view of you as a typical user. They should say briefly what you tried, what you expected, and what happened.

!! Analysis

Using design concepts and other principles from class/textbook, explain why this usability breakdown occurred.
* State the most important concepts/principles that were violated.
* Provide short, yet complete explanations (one to three sentences) for each.

!! Improvements

Discuss possible design improvements to the interface, based on your usability evaluation.

!! References

# ref 1
# ref 2
# ...

----

* Your report should have sections that follow the above outline. Include figures and illustrations that give '''substantive''' help to the reader in understanding the user interface, the usability breakdown, and your analysis. You are encouraged to '''use screen snapshots''' and other graphics (e.g., diagrams) for elucidation. However, '''avoid decorative graphics/pictures'''.

* As per course collaboration policy, there should be no discussion of any kind about this assignment (and possible solutions) with any person other than the instructor. '''You are not allowed to discuss/look at someone else’s solution (including material in books and the Internet) or show your solution to someone else other than the instructor'''.

* Include '''references''' on materials (other than the textbooks and handouts) you consulted to do the assignment.