Pattern languages in HCI: A critical review

This article presents a critical review of patterns and pattern languages in human-computer interaction (HCI). In recent years, patterns and pattern languages have received considerable attention in HCI for their potential as a means for developing and communicating information and knowledge to support good design. This review examines the background to patterns and pattern languages in HCI, and seeks to locate pattern languages in relation to other approaches to interaction design. The review explores four key issues: What is a pattern? What is a pattern language? How are patterns and pattern languages used? and How are values reflected in the pattern-based approach to design? Following on from the review, a future research agenda is proposed for patterns and pattern languages in HCI

Using pattern languages in participatory design

In this paper, we examine the contribution that pattern languages could make to user participation in the design of interactive systems, and we report on our experiences of using pattern languages in this way. In recent years, there has been a growing interest in the use of patterns and pattern languages in the design of interactive systems. Pattern languages were originally developed by the architect, Christopher Alexander, both as a way of understanding the nature of building designs that promote a ‘humane’ or living built environment; and as a practical tool to aid in participatory design of buildings. Our experience suggests that pattern languages do have considerable potential to support participatory design in HCI, but that many pragmatic issues remain to be resolved.</p

Software Design Guidelines for Usability

For years, the Human Computer Interaction &#40;HCI&#41; community has crafted usability guidelines that clearly define what&#10;characteristics a software system should have in order to be easy to use. However, in the Software Engineering &#40;SE&#41;&#10;community keep falling short of successfully incorporating these recommendations into software projects. From a SE&#10;perspective, the process of incorporating usability features into software is not always straightforward, as a large number&#10;of these features have heavy implications in the underlying software architecture. For example, successfully including an&#10;&ldquo;undo&rdquo; feature in an application requires the design and implementation of many complex interrelated data structures and&#10;functionalities. Our work is focused upon providing developers with a set of software design patterns to assist them in the&#10;process of designing more usable software. This would contribute to the proper inclusion of specific usability features&#10;with high impact on the software design. Preliminary validation data show that usage of the guidelines also has positive&#10;effects on development time and overall software design quality

Using Pattern Languages in Participatory Design

In this paper, we examine the contribution that pattern languages could make to user participation in the design of interactive systems, and we report on our experiences of using pattern languages in this way. In recent years, there has been a growing interest in the use of patterns and pattern languages in the design of interactive systems. Pattern languages were originally developed by the architect, Christopher Alexander, both as a way of understanding the nature of building designs that promote a ‘humane’ or living built environment; and as a practical tool to aid in participatory design of buildings. Our experience suggests that pattern languages do have considerable potential to support participatory design in HCI, but that many pragmatic issues remain to be resolved

The patterning of finance/security : a designerly walkthrough of challenger banking apps

Culture is being ‘appified’. Diverse, pre-existing everyday activities are being redesigned so they happen with and through apps. While apps are often encountered as equivalent icons in apps stores or digital devices, the processes of appification – that is, the actions required to turn something into an app – vary significantly. In this article, we offer a comparative analysis of a number of ‘challenger’ banking apps in the United Kingdom. As a retail service, banking is highly regulated and banks must take steps to identify and verify their customers before entering a retail relationship. Once established, this ‘secured’ financial identity underpins a lot of everyday economic activity. Adopting the method of the walkthrough analysis, we study the specific ways these processes of identifying and verifying the identity of the customer (now the user) occur through user onboarding. We argue that banking apps provide a unique way of binding the user to an identity, one that combines the affordances of smart phones with the techniques, knowledge and patterns of user experience design. With the appification of banking, we see new processes of security folded into the everyday experience of apps. Our analysis shows how these binding identities are achieved through what we refer to as the patterning of finance/security. This patterning is significant, moreover, given its availability for wider circulation beyond the context of retail banking apps

Reflecting on the usability of research on culture in designing interaction

The concept of culture has been attractive to producers of interactive\ud systems who are willing to design useful and relevant solutions to users\ud increasingly located in culturally diverse contexts. Despite a substantial body of\ud research on culture and technology, interaction designers have not always been\ud able to apply these research outputs to effectively define requirements for\ud culturally diverse users. This paper frames this issue as one of understanding of\ud the different paradigms underpinning the cultural models being applied to\ud interface development and research. Drawing on different social science theories,\ud the authors discuss top-down and bottom-up perspectives in the study of users‟\ud cultural differences and discuss the extent to which each provides usable design\ud knowledge. The case is made for combining bottom-up and top-down perspectives\ud into a sociotechnical approach that can produce knowledge useful and usable by\ud interaction designers. This is illustrated with a case study about the design of\ud interactive systems for farmers in rural Kenya