This is the authors' abstract. We don't add key points for this paper.
To create successful interactive systems, user interface designers need to cooperate with developers and application domain experts in an interdisciplinary team. These groups, however, usually miss a common terminology to exchange ideas, opinions, and values.This paper presents an approach that uses pattern languages to capture this knowledge in software development, HCI, and the application domain. A formal, domain-independent definition of design patterns allows for computer support without sacrificing readability, and pattern use is integrated into the usability engineering life cycle.As an example, experience from building an award-winning interactive music exhibit was turned into a pattern language, which was then used to inform follow-up projects and support HCI education.
Answers are grounded in this paper and cite their sources.
No takes yet. Share an insight, caveat, or question.
Jan Borchers (2000) studied this question.
Synapse has enriched 8 closely related papers on similar clinical questions. Consider them for comparative context: