User Interface Design Pattern Library Project

Assignment 1
Proposal

Assignment 2
Revised Problem Statement
Persona Explanation
Personas and Goals
Task Analysis
Appendices

Assignment 3
Scenarios
Persona Revisions
Task Revisions
Comparative Analysis
Initial Design Ideas

Assignment 4
Prototype
Write-up
Appendices

Assignment 5
Write-up
Interactive Prototype
Presentation (ppt)

Assignment 6
Heuristic Evaluation for UC HIPO

Assignment 7
Write-up
2nd Interactive Prototype
Appendix

Assignment 8
Write-up
Appendix

Assignment 9
Write-up
Presentation (ppt)
Final Interactive Prototype

Interviews, Round 2

Our initial survey and interviews did not give us deep insight into specific design processes, therefore this round of interviews focuses on the interface design process individuals go through to develop and implement user interfaces We specifically targetted the "swiss army" type of person. This type of user showed interest or awareness of user interface design patterns in Round 1 of the interviews and are in a position to implement them in their work process.

Target Participants

Three "swiss army" types
They have a current or recently completed project we can discuss.
They are responsible for producing/developing the front end.

Summary Results

Analysis of the first round of interviews revealed several categories of users, of which the "swiss army" type were the most interested in user interface design patterns. Consequently we decided to do a second round of interviews targeting this type of user. We had two goals:

1. Get a feel for the process these programmers use to develop the user interface in order to give us ideas for how the pattern library might fit into that process.

2. Show users an existing pattern library and get their feedback as to how they'd like to use a pattern library, including how they'd like to navigate the library and what additional features would be useful.

Perhaps the most significant revelation was that two interviewees expressed a preference for navigating the library based on a current design problem, rather than by the pattern name, which was how our existing example library was organized. One developer expressed interest in patterns related directly to the type of work he does (e.g., a pattern for the best way to display a record of student information).

Overwhelmingly, interviewees were interested in the prospect of being able to share code related to patterns. Two interviewees mentioned the idea of having a forum for comments associated with each pattern, similar to the way programming sites like php.net allow users to comment on functions. In general we noticed throughout the interview process that developers on campus feel somewhat isolated and would appreciate a tool that allowed them to connect and share ideas with others in the profession.

Interview Script & Questions

Design Process
We are interested in how the front end gets developed. Take a moment to think about your recent project and the steps you went through to develop the user interface. Let’s pull up your application so we can walk through it.

How did you begin the process of developing the user interface?
Do you use sketches, mock ups?
Do you collaborate with others?
Do you brainstorm?
Do you get feedback from coworkers, customers, manager?
Where do you get ideas? do you search for examples? look at other Berkeley sites?
How well defined is the design before implementation or do you design as you code?
How many iterations do you go through with your boss/stakeholder?
How do you incorporate feedback? do you reject feedback that leads to bad UI design? or do you implement whatever feedback you get?

Patterns
Now I want you to take a look at something called a UI design pattern. Take a moment to review it and talk aloud. Say whatever comes to mind – your impressions of it or any questions about it.

Do you see a moment in the design process we just talked about where this might be helpful?
What would this be useful for?
Would this be useful in your job? If not, is there someone on your team that would find it useful?