1 / 26

Ensuring ease of use – identifying repository design patterns

Ensuring ease of use – identifying repository design patterns. October 2007. Hvad er brugbarhed - Collage. Afslutning. Afslutning. Learnability Efficiency Memorability Low error rate Satisfaction. What is a design pattern?. “Patterns are optimal solutions to common problems.“

leiko
Download Presentation

Ensuring ease of use – identifying repository design patterns

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Ensuring ease of use– identifying repository design patterns October 2007

  2. Hvad er brugbarhed - Collage

  3. Afslutning

  4. Afslutning • Learnability • Efficiency • Memorability • Low error rate • Satisfaction

  5. What is a design pattern? “Patterns are optimal solutions to common problems.“ (Yahoo! Design Pattern Library)

  6. www.welie.com/patterns/ developer.yahoo.com/ypatterns/

  7. Why are patterns good? • They solve problems • They are very concrete • They are proven concepts • They describe relationships and represent knowledge in a structured form • They impose design discipline on design teams

  8. Adhering to a pattern does not impede creativity

  9. Building a pattern • A title • A problem • Use When • Solutions – including examples (screen shots)

  10. Pattern relationships Three levels: • Pattern groups • Patterns • Solutions

  11. Pattern relationships Three levels: • Pattern groups – e.g. “Keep users updated” • Patterns – e.g. “RSS”, “Newsletter”, “e-mail alerts” • Solutions – e.g. “Provide contextual help on the term “RSS” “Place the RSS-icon at the bottom of the page”

  12. Repository pattern groups • Navigation • Collecting resources • Resource description page • Repository homepage • Keep users updated • Metadata editors • Profile page / personal settings

  13. Getting started - Pattern writing • Do some initial research • Make screen shots (incl. URL) • Make a checklist • Flesh it out • Upload on the Edrene web site • Get it reviewed Remember: Patterns are “work in progress”

  14. Identify new patterns • Browse other types of websites to identify relevant patters

  15. The plan • Group session 1Work on two different patterns for 2 hours. • Group session 2Discuss pattern with 2 other persons who have been working on the same pattern. Make one new, revised version. • Group session 3Review a pattern made by another group by comparing it to the actual design on your own site.

  16. Practical details • Find your name on the hand-out - see what pattern you’re responsible for - see what group number you belong to in the first session • Find the other person who belongs to your group number • Spend 1 hour working on one pattern • Have a coffee break! • Spend 1 hour working on the other pattern

More Related