Fall2005.CSCI380Homework1 History

Hide minor edits - Show changes to output

Deleted lines 83-86:


Student submissions: [[CSCI380Homework1_Baker | Baker]], [[CSCI380Homework1_Crosby | Crosby]], [[CSCI380Homework1_Evans | Evans]], [[CSCI380Homework1_Hearn | Hearn]], [[CSCI380Homework1_Leung | Leung]], [[CSCI380Homework1_Mojica | Mojica]], [[CSCI380Homework1_Peterson | Peterson]], [[CSCI380Homework1_Phillips | Phillips]], [[CSCI380Homework1_Rice | Rice]], [[CSCI380Homework1_Singleton | Singleton]], [[CSCI380Homework1_Tindall | Tindall]], [[CSCI380Homework1_Trinklein | Trinklein]].
Added lines 85-87:

Student submissions: [[CSCI380Homework1_Baker | Baker]], [[CSCI380Homework1_Crosby | Crosby]], [[CSCI380Homework1_Evans | Evans]], [[CSCI380Homework1_Hearn | Hearn]], [[CSCI380Homework1_Leung | Leung]], [[CSCI380Homework1_Mojica | Mojica]], [[CSCI380Homework1_Peterson | Peterson]], [[CSCI380Homework1_Phillips | Phillips]], [[CSCI380Homework1_Rice | Rice]], [[CSCI380Homework1_Singleton | Singleton]], [[CSCI380Homework1_Tindall | Tindall]], [[CSCI380Homework1_Trinklein | Trinklein]].
Changed lines 83-84 from:
Student submissions [- (locked) -]: [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Baker | Baker]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Crosby | Crosby]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Evans | Evans]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Hearn | Hearn]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Leung | Leung]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Mojica | Mojica]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Peterson | Peterson]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Phillips | Phillips]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Rice | Rice]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Singleton | Singleton]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Tindall | Tindall]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Trinklein | Trinklein]].
to:
Student submissions [- (require password) -]: [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Baker | Baker]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Crosby | Crosby]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Evans | Evans]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Hearn | Hearn]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Leung | Leung]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Mojica | Mojica]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Peterson | Peterson]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Phillips | Phillips]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Rice | Rice]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Singleton | Singleton]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Tindall | Tindall]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Trinklein | Trinklein]].
Added lines 81-84:
!!!Submissions

Student submissions [- (locked) -]: [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Baker | Baker]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Crosby | Crosby]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Evans | Evans]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Hearn | Hearn]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Leung | Leung]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Mojica | Mojica]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Peterson | Peterson]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Phillips | Phillips]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Rice | Rice]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Singleton | Singleton]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Tindall | Tindall]], [[http://www.cs.cofc.edu/~manaris/notes/pmwiki.php/CSCI380Fall2005/H1_Trinklein | Trinklein]].
Changed lines 66-68 from:
Signature: ________________________ Date: ___________
to:
Name: ________________________ Date: ___________
Changed lines 74-76 from:
** Work for clarity, succinctness, and effectiveness.
** ''Hint'': It might help to think of your report as a (meta) user interface, and your classmates as your end-users. What are the tasks they would want to accomplish with your report?
to:
* Work for clarity, succinctness, and effectiveness.
* ''Hint'': It might help to think of your report as a (meta) user interface, and your classmates as your end-users. What are the tasks they would want to accomplish with your report?
Changed lines 60-68 from:
Certification of Authenticity:

I certify that this submission is entirely my own work,
as per course collaboration policy.


Signature: ________________________ Date: ___________
to:
Certification of Authenticity:

I certify that this submission is entirely my own work,
as per course collaboration policy.


Signature: ________________________ Date: ___________
Changed lines 62-64 from:
I certify that this submission is entirely my own work, as per course collaboration policy.
to:
I certify that this submission is entirely my own work,
as per course collaboration policy.
Changed lines 1-2 from:
'''Assigned Date''': Tuesday, Sep. 6, 2005 \\
'''Due Date''': Thursday, Sep. 15, 2005 \\
to:
'''Assigned Date''': Thursday, Sep. 8, 2005 \\
'''Due Date''': Tuesday, Sep. 20, 2005 \\
Changed lines 11-13 from:
Identify usability issues associated with a familiar (to you) interface.
to:
Identify usability issues associated with a familiar user interface.
Changed lines 16-19 from:
# Tuesday, noon: Send email with, at least, three different user interfaces/usability breakdowns (in decreasing order of preference). I will let you know which to work on.

''More
soon...''
to:
# ''Tuesday, Sep. 13, noon'': Send email with, at least, three different user interfaces/usability breakdowns (in decreasing order of preference).

# ''Tuesday, Sep. 20, noon'': Submit a short report
on the Wiki (details soon). Be ready to present your analysis in class (in 10 minutes or less).
Changed lines 24-31 from:
''More soon...''

!!!Sample Solutions

[[http://www.cs.cofc.edu/~manaris/spring05/cs672/hmwk1/cameraAnalysis.pdf | PhotoImpression 5.0]],
[[http://www.cs.cofc.edu/~manaris/spring05/cs672/hmwk1/JGodwin_CSIS672_HW1.pdf | DP Weight Training Bench]],
[[http://www.cs.cofc.edu/~manaris/spring05/cs672/hmwk1/Jason_Miller-Assignment_1.pdf | KDC-MP522 Car Stereo]],
[[http://www.cs.cofc.edu/~manaris/spring05/cs672/hmwk1/thesink.pdf | Motion Detection Faucet]].
to:
In your report, follow the following outline:

* Name, class, date, etc.

# '''Introduction''': Describe your first impressions:
** What is good and bad about this interface?
** What is good and bad about the user experience it produces?

# '''Functionality''': Describe the system's functionality.
** Provide concise, yet complete description (one to three sentences).

# '''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.

!!!Notes

* 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'''.

* At the bottom of your report, include a certificate of authenticity using this format:


Certification of Authenticity:

I certify that this submission is entirely my own work, as per course collaboration policy.


Signature: ________________________ Date: ___________


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

!!!Grading

Grading will be based on your ability to carefully and succinctly identify the key points of the case study.
** Work for clarity, succinctness, and effectiveness.
** ''Hint'': It might help to think of your report as a (meta) user interface, and your classmates as your end-users. What are the tasks they would want to accomplish with your report?

!!!Reference

This assignment comes from the Preece et al, ''Interaction Design'' textbook (p. 28). It includes elements from an [[http://ldt.stanford.edu/~chaoyc/course/fall.html | HCI class]] assignment at Stanford University taught by Terry Winograd. Here is a [[http://stono.cs.cofc.edu/~manaris/spring05/cs672/sample_solution_hmwk1.pdf | sample solution]] from that assignment (note that your specs are somewhat different).
Changed lines 7-8 from:
This is a group assignment (three people per team). See course collaboration policy for details.
to:
This is an individual assignment. See course collaboration policy for details.
Changed lines 16-17 from:
# Thursday, noon: Send email with, at least, two different user interfaces/usability breakdowns (in decreasing order of preference). If another student has selected your first choice, I will let you know.
to:
# Tuesday, noon: Send email with, at least, three different user interfaces/usability breakdowns (in decreasing order of preference). I will let you know which to work on.
Changed lines 24-31 from:
''More soon...''
to:
''More soon...''

!!!Sample Solutions

[[http://www.cs.cofc.edu/~manaris/spring05/cs672/hmwk1/cameraAnalysis.pdf | PhotoImpression 5.0]],
[[http://www.cs.cofc.edu/~manaris/spring05/cs672/hmwk1/JGodwin_CSIS672_HW1.pdf | DP Weight Training Bench]],
[[http://www.cs.cofc.edu/~manaris/spring05/cs672/hmwk1/Jason_Miller-Assignment_1.pdf | KDC-MP522 Car Stereo]],
[[http://www.cs.cofc.edu/~manaris/spring05/cs672/hmwk1/thesink.pdf | Motion Detection Faucet]].
Changed lines 22-24 from:
Choose an interactive interface with which you have experienced some kind of usability breakdown. Examine how the interface has been designed, paying particular attention to how the user is meant to interact with it.
to:
Choose an interactive interface with which you have experienced some kind of usability breakdown. Examine how the interface has been designed, paying particular attention to how the user is meant to interact with it.

''More soon...''
Changed lines 7-8 from:
This is a group assignment (three people per team).
to:
This is a group assignment (three people per team). See course collaboration policy for details.
Changed lines 16-23 from:
# (Thursday, Jan. 27, noon) Send email with, at least, two different user interfaces/usability breakdowns (in decreasing order of preference). If another student has selected your first choice, I will let you know.
# (Wednesday, Feb. 2, noon) Submit a short report via email (PDF format). You may use only up to one late day on this deliverable.
3. (Thursday, Feb 3, beginning of class) Submit a signed hard copy of your report. Be ready to present your case study (in 10 minutes). Aim for clarity, succinctness, and effectiveness. No late days may be used here.



Specification:
to:
# Thursday, noon: Send email with, at least, two different user interfaces/usability breakdowns (in decreasing order of preference). If another student has selected your first choice, I will let you know.

''More soon...''

!!!
Specification
Added lines 1-24:
'''Assigned Date''': Tuesday, Sep. 6, 2005 \\
'''Due Date''': Thursday, Sep. 15, 2005 \\
'''Due Time''': Noon

Last modified on {$LastModified} (see [[http://www.cs.cofc.edu/~manaris/index.php/Fall2005/CSCI380Homework1?action=diff&source=n&minor=n | updates]])

This is a group assignment (three people per team).

!!!Purpose

Identify usability issues associated with a familiar (to you) interface.


!!!Deliverables

# (Thursday, Jan. 27, noon) Send email with, at least, two different user interfaces/usability breakdowns (in decreasing order of preference). If another student has selected your first choice, I will let you know.
# (Wednesday, Feb. 2, noon) Submit a short report via email (PDF format). You may use only up to one late day on this deliverable.
3. (Thursday, Feb 3, beginning of class) Submit a signed hard copy of your report. Be ready to present your case study (in 10 minutes). Aim for clarity, succinctness, and effectiveness. No late days may be used here.



Specification:

Choose an interactive interface with which you have experienced some kind of usability breakdown. Examine how the interface has been designed, paying particular attention to how the user is meant to interact with it.