COAP:COAP-3150 - week 2: Difference between revisions

The educational technology and digital learning wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 14: Line 14:


====[[Color | Colour theory]] (RGB, HSB, hexidecimal)====
====[[Color | Colour theory]] (RGB, HSB, hexidecimal)====
Color palette generators
* [http://kuler.adobe.com/ Kuler]
* [http://paletton.com/ Paletton colorscheme designer]
* [http://www.colorsontheweb.com/Color-Tools/Color-Wizard Colors on the web wizard]
* [http://www.cssdrive.com/imagepalette/ CSSdrive] - generate a palette from an image


 
See also [http://www.colorsontheweb.com/ Colors on the web] - a site "dedicated to color theory and the use of colors in web design"
-----
Assignment – Requirements specification


==Part II==
==Part II==
Line 24: Line 27:


==== Conducting a requirements analysis====
==== Conducting a requirements analysis====
* targeting public and defining stakeholders
A thorough [https://www.usability.gov/how-to-and-tools/methods/requirements.html requirements analysis] is used for
* targeting public and defining [http://www.usabilityfirst.com/about-usability/project-stakeholders/ stakeholders]
* determining objectives
* determining objectives
* determining client needs [http://www.cosmicidea.com/start/needs-analysis.php link to form for clients]
* 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>User needs analysis - Web Guide. (n.d.). Retrieved January 26, 2012, from http://webguide.gov.au/accessibility-usability/user-needs-analysis/</ref> - who, what, when, how, why - Read [http://webguide.gov.au/accessibility-usability/user-needs-analysis/ 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]
* defining success
* defining success



Latest revision as of 17: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.

See also Usability, User-centered design, User experience and user experience design

Typography - using type for the web

Colour theory (RGB, HSB, hexidecimal)

Color palette generators

See also Colors on the web - a site "dedicated to color theory and the use of colors in web design"

Part II

Design processes and models

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


  1. Usability.gov User Research Basics. Retrieved October 31, 2016 from https://www.usability.gov/what-and-why/user-research.html