Design Patterns Project Plan (preliminary)

This project plan is a DRAFT, and will be used for the Fluid UX Team's planning exercises. The tasks which are coming up soon are defined in a more granular fashion than those far in the future.

 Fluid 0.1 Release

• Prepare drag-and-drop design pattern for Fluid 1.0 release
  • Determine where pattern will live (on a temporary basis, until a pattern library is started)
  • Add introductory text to front page of DP Library
  • Add examples of implementations in non-Fluid applications
  • Add examples of implementations in Sakai
  • Add examples of implementations in uPortal, Moodle (if possible)
  • determine whether we have all needed DP sections by looking at other DP libraries

Add tasks to the List. Assign yourself to work and mark when complete.

General Planning

• Create meeting/working group plan
• Create project communications plan (for members interested in and impacted by the project, but not part of a working group)
• Determine what we think the goals of the project are in the current context (see Questions for the Group to Consider (preliminary) for some ideas)
  • Determine who we currently think is the target audience of the project
  • Create persona hypothesis about the audience(s) of the project
  • Create hypothesis about link to Fluid Design Handbook, Component Library
  • Determine how Fluid Design Patterns Library will work with other Design Patterns libraries (e.g. Sakai DP Library)
• Create Scope statement for the project

Add tasks to the List. Assign yourself to work and mark when complete.

Research/Competitive Analysis

• Competitive Analysis of & Research Into Design Pattern Libraries
  • Determine libraries to analyze (see Design Pattern Libraries)
  • Analyze Design Pattern Libraries
  • Select Design Pattern literature to read
    • Potential ideas
      • Design Pattern Resources
      • A Pattern Approach to Interaction Design
      • The Promise of Pattern Languages for Interaction Design
      • Don't Write Guidelines ­ Write Patterns!
      • Pattern Languages for Usability: An Investigation of Alternative Approaches
      • Principles for a Usability-Oriented Pattern Language
      • Pattern Languages as Languages
      • Putting It All Together: Towards a Pattern Language for Interaction Design& PLML: Pattern Language Markup Language
      • Common Ground: A Pattern Language for Human-Computer Interface Design
      • Experiences - A Pattern Language for User Interface Design
      • Seven Habits of Successful Pattern Writers
      • Patterns: The Top Ten Misconceptions
      • Lingua Francas for Design: Sacred Places and Pattern Languages
      • The Elements of a Design Pattern
      • An Introduction to Using Patterns in Web Design
      • Designing with Patterns
      • Tips for Writing Pattern Languages
      • Enhancing Re-Use: Towards a Pattern- and Component-Based UI Development [pdf] [ppt]
      • Patterns and Components for Enhancing Reusability and Systematic UI Development [pdf] [ppt]
      • Pattern-Based UI Design: Adding Rigor with User and Context Variables [pdf] [ppt]
      • A Pattern Framework for Eliciting and Delivering UCD Knowledge and Practices [pdf] [ppt]
      • User Interface Patterns: Reusable solutions for design - Allison
  • Read Design Pattern literature
  • Are there Accessibility Design Patterns?
  • Should Accessibility for a feature be it's own "pattern" or part of the component? Separate but linked somehow?

Add tasks to the List. Assign yourself to work and mark when complete.

User Needs Assessment

• Observe users of the Design Patterns Library (& likely the Design Handbook & Component Library) as they do work which uses it
  • Plan for this to occur (at least) at uCamp & Sakai Conference (? Probably at Sakai uCamp they would have access to that DP library)
    • Determine activity to observe
      • Coordinate with Daphne who is coming up with ideas for where re-orderer could be implemented
    • Create Focus Structure document on what to look for in observations
  • Do observations
    • Determine how design patterns are used by component implementors
    • Determine what additional context is needed beyond the design pattern in order to properly implement the component
  • Create personas & scenarios for site/application based on user observations
• Revisit goals and scope statement based on research

Add tasks to the List. Assign yourself to work and mark when complete.

System Design

• Design system to allow target audiences to achieve their goals
  • Determine whether we can reuse any Oracle materials/infrastructure
  • Determine whether we can reuse UC Berkeley's Design Patterns Library infrastructure (PHP or Drupal version)
  • Determine whether we can reuse materials from other design patterns libraries
  • Gather existing content
  • Determine content which must still be created
  • Design information architecture
  • Determine what technology will be used to present information

Add tasks to the List. Assign yourself to work and mark when complete.

Implementation

• Build system/website to hold Design Pattern Library/Design Handbook
  • Are the components presented in this system somehow?
  • Should/can we add "interactions" to our patterns (they are dynamic not static)
• Create content
  • Create additional design patterns to populate library
    • Determine how the Sakai Design Patterns library will interact with or be part of the Fluid library
  • Determine whether we'd like to create patterns which do not directly relate to Fluid components

Add tasks to the List. Assign yourself to work and mark when complete.

Current Implementation (website building tasks)

Project Plan Draft from Barbara

• • Create a "look and feel" for the Fluid OSDP
  • Create tutorial for how to add a pattern to the library for new comers
  • Include coding examples later for each pattern in Fluid library to help developers.
    • The library should include links components, code examples, mark-up primitives, HTML/CSS "templates" wherever possible.
  • Have small team of people look through libraries like Yahoo patterns or Berkeley Library and see if there's patterns they have we want to link to. 
    • Create links into these libraries for those patterns we feel are relevant to our OSDP
    • Create Fluid screen shots illustrating those patterns. | | |