Assignment 03: Design Decisions
| Assignment | Description | Due on | Value |
|---|---|---|---|
| 01 | user analysis | 06 Feb | 10% |
| 02 | task analysis | 25 Feb | 10% |
| 03 | your rationale for the design decisions made | 06 Mar | 20% |
| 04 | prototype and system description | 10 Apr | 20% |
| 05a | usability inspection of a design developed by one of your classmates | 17 Apr | 10% |
| 05b | response to a usability inspection of your design | 22 Apr | 05% |
| 06 | planning a usability test of your own design | 06 May | 15% |
| participation | in class and online | daily | 10% |
As you develop your design, you will be making decisions about how the system will be implemented. Five or six of your major design decisions should be documented formally (though you may also document smaller decisions, if it is helpful to you).
For each decision, you should
- specify the decision itself,
- the alternatives considered,
- and your rationale for selecting a particular alternative, including the evidence supporting your reasoning.
Evidence supporting your design decisions may be drawn from published usability guidelines, prior research studies that are relevant to your decision, or data you have gathered from your target audience.
You have four examples to look at.
- The first example is simple and straightforward for a reasonably scoped proposal.
- The second example goes a bit more into detail about design philosophy and lays out a few examples for a fairly complex proposal.
- The third example seeks to display clearly what those design decisions may look like for a fairly complex proposal.
- The fourth example is the most robust, but for a fairly simple proposal - a website for a small town government.
At least two decisions should be documented and are due on Wednesday, 06 Mar 2013
All five/six will be turned in with the final documentation for the project, on Monday, 22 Apr 2013
[top]