COAP:COAP-2170/week3: Difference between revisions
Jump to navigation
Jump to search
m (→Homework 3) |
|||
| Line 8: | Line 8: | ||
* Learn about designing an information architecture | * Learn about designing an information architecture | ||
=== Monday | === Monday - Early design stages === | ||
* [[Focus group]] meetings | * [[Focus group]] meetings | ||
| Line 45: | Line 24: | ||
* Name categories | * Name categories | ||
* Discuss and compare solutions | * Discuss and compare solutions | ||
=== Wednesday === | |||
; Review meeting preparation | |||
* Retrieve hw1 + hw2 and look at it | |||
* Also [http://tecfa.unige.ch/guides/te/coap2170/homework here] | |||
; Review meeting | |||
: 9:20 usability review meeting with X (to be confirmed) | |||
* Students will present highlights from homework 1 and 2 and engage in discussion. | |||
* No preparation is needed for this (except doing homework 2 and turning it in '''before''' start of class) | |||
Program: | |||
For each Webster website | |||
* Home page and overall general impression | |||
* Selected usability tests and results. | |||
=== Homework 3 === | === Homework 3 === | ||
| Line 50: | Line 48: | ||
(1) Complete the card sorting activity if needed | (1) Complete the card sorting activity if needed | ||
* If you missed class, please have a look at all the [[Card_sorting#Videos |videos in the card sorting article]] | * If you missed class, please have a look at all the [[Card_sorting#Videos |videos in the card sorting article]] | ||
* Print out the cards from http://tecfa.unige.ch/guides/te/coap2170/data-files/webster-ch-titles.pdf (ask a classmate for the password) | * Print out the cards from http://tecfa.unige.ch/guides/te/coap2170/data-files/webster-ch-titles.pdf (to be confirmed, ask a classmate for the password) | ||
(2) Write a short report that includes: | (2) Write a short report that includes: | ||
Revision as of 14:59, 4 September 2012
COAP 2170 Week 3 program
In week three we will do two things:
- Wrap up week 1 and 2 (usability guidelines review and usability testing) through a review meeting
- Learn about designing an information architecture
Monday - Early design stages
- Focus group meetings
- Analysis of competitor's websites, e.g. with tools seen so for
- Card sorting is a popular technique for planning the information architecture of a website. It may be used to figure out an initial proposal and also to test this proposal with potential users.
- Introductory videos
- See the card sorting article
- Card sorting activity (see also homework 3 below)
- Create cards or get them from here. Best bet is webster-ch-titles.pdf
- Sort cards into piles (categories)
- Name categories
- Discuss and compare solutions
Wednesday
- Review meeting preparation
- Retrieve hw1 + hw2 and look at it
- Also here
- Review meeting
- 9:20 usability review meeting with X (to be confirmed)
- Students will present highlights from homework 1 and 2 and engage in discussion.
- No preparation is needed for this (except doing homework 2 and turning it in before start of class)
Program: For each Webster website
- Home page and overall general impression
- Selected usability tests and results.
Homework 3
(1) Complete the card sorting activity if needed
- If you missed class, please have a look at all the videos in the card sorting article
- Print out the cards from http://tecfa.unige.ch/guides/te/coap2170/data-files/webster-ch-titles.pdf (to be confirmed, ask a classmate for the password)
(2) Write a short report that includes:
- A list of categories that you found (you decide about the number and whether you need subcategories or not)
- Describe each category with a few sentences
- You also could explain why these categories should be appropriate
Other issues:
- You can turn in group work. Make sure to put the name of each participant on top of the paper. Also, I expect group work to be "richer" than individual work. Of course, you also could start from commonly found categories and then write down an individual view of the results ...
- You can organize your report in any way you like. Just make sure that it looks like an interesting design document that could be used to redesign the information architecture.
- Do not think about the website design. All I want is that you think about how to structure information ...