COAP:COAP-3150 - week 2: Difference between revisions
Jump to navigation
Jump to search
Line 27: | Line 27: | ||
* targeting public and defining [http://www.usabilityfirst.com/about-usability/project-stakeholders/ stakeholders] | * targeting public and defining [http://www.usabilityfirst.com/about-usability/project-stakeholders/ stakeholders] | ||
* determining objectives | * determining objectives | ||
* determining client needs [ | * determining client needs using a [https://www.usability.gov/how-to-and-tools/methods/task-analysis.html task analysis] | ||
* defining types of interactions - what will users '''do''' on site and '''how''' | * defining types of interactions - what will users '''do''' on site and '''how''' | ||
* analyzing user needs <ref>Usability.gov User Research Basics. Retrieved October 31, 2016 from https://www.usability.gov/what-and-why/user-research.html</ref> - who, what, when, how, why - Read [https://www.usability.gov/what-and-why/user-research.html User Needs analysis] | * analyzing user needs <ref>Usability.gov User Research Basics. Retrieved October 31, 2016 from https://www.usability.gov/what-and-why/user-research.html</ref> - who, what, when, how, why - Read [https://www.usability.gov/what-and-why/user-research.html User Needs analysis] |
Revision as of 15:09, 2 November 2016
Part I
Usable web design principles
Principles
Some links that list and describe design principles for usable and effective web pages.
- 9 Essential Principles for Good Web Design
- The Ten Most Violated Homepage Design Guidelines
- Top 10 Mistakes in Web Design (Jakob Nielsen's Alertbox)
- 10 Principles Of Effective Web Design
See also Usability, User-centered design, User experience and user experience design
Typography - using type for the web
Colour theory (RGB, HSB, hexidecimal)
Assignment – Requirements specification
Part II
Design processes and models
- We will be using a combination of the Model of Pervasive Usability and this Step-by-step Usability Guide from Usability.gov. See Design processes and models for other models used in web-design processes.
Conducting a requirements analysis
A thorough requirements analysis is used for
- targeting public and defining stakeholders
- determining objectives
- determining client needs using a task analysis
- defining types of interactions - what will users do on site and how
- analyzing user needs [1] - who, what, when, how, why - Read User Needs analysis
- defining success
- ↑ Usability.gov User Research Basics. Retrieved October 31, 2016 from https://www.usability.gov/what-and-why/user-research.html