The document discusses the creation of a web design patterns library at UC Berkeley to address isolated development efforts and inconsistent user interface practices among diverse teams. It emphasizes the importance of design patterns in fostering collaboration, sharing knowledge, and providing a common language for developers. The library includes contributions from the UC developer community and reflects a user-centered design methodology.

1. Web Design Pattern Library www.ui-designpatterns.org Kelly Snow, Mano Marks, Tim Dennis, Dave Hong May 12, 2006 U.C. Berkeley Web Design Patterns Library

2. UC Berkeley Environment Autonomous fiefdoms Lack of coordinated development efforts. Applications based on organizational structure Different strategies and code base Top-down initiatives are doomed May 12, 2006 U.C. Berkeley Web Design Patterns Library

3. UI Design at UC Berkeley No formal training Work in isolation Few resources / many responsibilities No sense of community Developers with non-technical managers May 12, 2006 U.C. Berkeley Web Design Patterns Library

4. Sakai Many cooks in the kitchen Distributed and disparate development environments Unique branding for each campus May 12, 2006 U.C. Berkeley Web Design Patterns Library

5. Collaborative Tools Working groups Discussion groups Email Wiki May 12, 2006 U.C. Berkeley Web Design Patterns Library

6. Common Solutions Templates Hi-fi Wireframes Tags / Markup Styleguides “ Top-down Smackdown” May 12, 2006 U.C. Berkeley Web Design Patterns Library

7. Distributed Knowledge “ knowledge about user interface and design is distributed and often not shared” May 12, 2006 U.C. Berkeley Web Design Patterns Library

8. Inconsistency “ knowledge about what constitutes good user interface is inconsistent” May 12, 2006 U.C. Berkeley Web Design Patterns Library

9. Personalities “ each person has their own ideas and agenda about the interface” May 12, 2006 U.C. Berkeley Web Design Patterns Library

10. Web Design Patterns A model for common problems and appropriate solutions in highly diverse development environments. Provide a common language for people to use in their work process. May 12, 2006 U.C. Berkeley Web Design Patterns Library

11. Why Design Patterns? Collect and redistribute knowledge of large communities. May 12, 2006 U.C. Berkeley Web Design Patterns Library

12. Why Design Patterns? Cooperative & inclusive: a better model and artifact for attaining and capturing consensus. May 12, 2006 U.C. Berkeley Web Design Patterns Library

13. Why Design Patterns? Encapsulate rationale and best practices as well as shared interests May 12, 2006 U.C. Berkeley Web Design Patterns Library

14. Why Design Patterns? Combine a heavy text-based medium with visual examples May 12, 2006 U.C. Berkeley Web Design Patterns Library

15. Why Design Patterns? Describe design elements allowing for flexible implementation and mixing and matching May 12, 2006 U.C. Berkeley Web Design Patterns Library

16. What We Built Web-based application that contains web design patterns Pattern schema Supports contributions from UC developer community May 12, 2006 U.C. Berkeley Web Design Patterns Library

17. How We Did It Surveying and interviewing users Analysis of other pattern collections Analysis of existing campus apps Data Modeling Pattern Writing Methodology User Centered Design Implementation May 12, 2006 U.C. Berkeley Web Design Patterns Library