| Version 5 (modified by deyan, 17 years ago) (diff) |
|---|
Analysis
Overview
Create a document as a part of the specification. Examples:
- Tooltips
- Keyboard accessibility etc.
- Assistive technologies.
These are things that should be pointed out and writed down. Look wikipedia for a good example explanation of this task. Quotes you may find useful:
Human-computer interaction and computer science, usability usually refers to the elegance and clarity with which the interaction with a computer program or a web site is designed.
The key benefits of usability are:
* Higher revenues through increased sales
* Increased user efficiency
* Reduced development costs
* Reduced support costs
Usability includes:
* Learnability: How easy is it for users to accomplish basic tasks the first time they encounter the design?
* Efficiency: Once users have learned the design, how quickly can they perform tasks?
* Memorability: When users return to the design after a period of not using it, how easily can they re establish proficiency?
* Errors: How many errors do users make, how severe are these errors, and how easily can they recover from the errors?
* Satisfaction: How pleasant is it to use the design?
Task requirements
(Necessary requirements that the task must fulfill.)
Task result
(The Analysis should contain strict requirements about the end product of the task (for example the result must be source code, the result must be google doc, etc.))
Implementation idea
(It is advisable to include some rough implementations ideas.)
Related
(Here you can add related tasks that could be useful or helpful.)
How to demo
(In this section you must add instructions for the demo of the task.)
Design
Implementation
(Implementation results should be described and linked here (from the wiki or the repository))
Testing
Comments
Log
