Encouraging the effective use of contextual information in design

definitions o f context are o f limited value Abstract definitions of context such as the definition offered by Wixon and Raven (1994) may not be of much use to designers. Such definitions are unlikely to be able to identify all the relevant contextual factors for any paiticular design project since each currently available definition focuses on some aspects of context at the expense of other aspects, which could be just as relevant in a design project. Chapter 2 discussed the problem of scoping with respect to different contextual design methods. Cockton et al. (1995) also discussed this issue and Clarke (1996) suggests that designers must be aware of differences in scope of each definition of context so that methods and definitions can be combined, thus ensuring complete coverage of all the relevant contextual information for a particular project. Without an awareness of the differences in scope of definitions of context, designers may be unaware of potentially relevant context that the definition they are employing simply ignores. A more concrete ‘map’ of context, such as the checklist shown in Appendix A, may help avoid the problem of ignoring relevant context, since it explicitly lists different elements of context, and can be referred to at any time by designers. In contrast, abstract definitions of context do not support explicit descriptions and rely on the designers to consistently interpret the definition in terms of identifying relevant and irrelevant context.definitions of context such as the definition offered by Wixon and Raven (1994) may not be of much use to designers. Such definitions are unlikely to be able to identify all the relevant contextual factors for any paiticular design project since each currently available definition focuses on some aspects of context at the expense of other aspects, which could be just as relevant in a design project. Chapter 2 discussed the problem of scoping with respect to different contextual design methods. Cockton et al. (1995) also discussed this issue and Clarke (1996) suggests that designers must be aware of differences in scope of each definition of context so that methods and definitions can be combined, thus ensuring complete coverage of all the relevant contextual information for a particular project. Without an awareness of the differences in scope of definitions of context, designers may be unaware of potentially relevant context that the definition they are employing simply ignores. A more concrete ‘map’ of context, such as the checklist shown in Appendix A, may help avoid the problem of ignoring relevant context, since it explicitly lists different elements of context, and can be referred to at any time by designers. In contrast, abstract definitions of context do not support explicit descriptions and rely on the designers to consistently interpret the definition in terms of identifying relevant and irrelevant context. Chapter 6; Thesis Contributions The thesis has shown that relationships'exist both from context to design and from design to context. Each type of relationship conveys a different meaning and may require different actions as a result of some change to either the source or destination of the relationship. The next chapter describes the future work that has been suggested by this research. In effect, the future work is another category of contributions. Given the small amount of research that has been carried out into explicily relating context with designs, this thesis has possibly raised more questions than it has answered. The next chapter describes these questions and issues and suggests ways in which they may be addressed. 181 6.3 Chapter Summary ..... This chapter has reviewed the main contributions of this thesis. They are split into two categories. The first category concerns the contributions made with respect to explicitly recording the relationships between context and design. It demonstrates that recording and maintaining the relationships between context and design provides benefits to designers in that it encourages them to think about and discuss the ways that context has been used. Such discussion and reflection can highlight inconsistencies and omisssions within and between particular design documents. By resolving these inconsistencies and omissions, designers start to make more efficient use of contextual information in design.

[1]  John Seely Brown,et al.  Borderline Issues: Social and Material Aspects of Design , 1994, Hum. Comput. Interact..

[2]  Jintae Lee SIBYL: a tool for managing group design rationale , 1990, CSCW '90.

[3]  Mary Beth Rosson,et al.  The designer as user: building requirements for design tools from design practice , 1988, CACM.

[4]  Helen Z. Margetts,et al.  Computerization and Controversy: Value Conflicts and Social Choices , 1993, J. Inf. Technol..

[5]  Karen Holtzblatt,et al.  Making customer-centered design work for teams , 1993, CACM.

[6]  John D. Gould,et al.  The 1984 Olympic Message System: a test of behavioral principles of system design , 1987, CACM.

[7]  Gilbert Cockton,et al.  Theories of Context Influence the System Abstractions Used to Design Interactive Systems , 1995, BCS HCI.

[8]  Andrew Dillon,et al.  Design rationale: Concepts, techniques, and use , 1997 .

[9]  Mary Elizabeth Raven,et al.  Using contextual inquiry to learn about your audiences , 1996, ASTR.

[10]  Pelle Ehn,et al.  Work-oriented design of computer artifacts , 1989 .

[11]  T.M. Duffy,et al.  Scenario-Based Design: Envisioning Work and Technology in System Development [Book Review] , 1996, IEEE Transactions on Professional Communication.

[12]  Gerhard Schmidt,et al.  Out of Scandinavia: Alternative Approaches to Software Design and System Development , 1989, Hum. Comput. Interact..

[13]  Chris Roast,et al.  Towards a framework for investigating temporal properties in interaction , 1997, SGCH.

[14]  W. Buxton Human-Computer Interaction , 1988, Springer Berlin Heidelberg.

[15]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[16]  Jean Scholtz,et al.  Systematic creativity: a methodology for integrating user, market and engineering requirements for product definition, design and usability testing , 1995, EHCI.

[17]  Michael L. Begeman,et al.  gIBIS: a hypertext tool for exploratory policy discussion , 1988, CSCW '88.

[18]  Nick Hammond,et al.  Modelling user, system design: results of a scenarios matrix exercise , 1991, CHI '91.

[19]  K. Kuutti Activity theory as a potential framework for human-computer interaction research , 1995 .

[20]  Ivar Jacobson,et al.  The use-case construct in object-oriented software engineering , 1995 .

[21]  M. Kyng,et al.  Computers and Democracy: A Scandinavian Challenge , 1987 .

[22]  Laurent Karsenty,et al.  An empirical evaluation of design rationale documents , 1996, CHI.

[23]  Andrew Clement,et al.  A retrospective look at PD projects , 1993, CACM.

[24]  K. Ochimizu,et al.  Design of a hyper media tool to support requirements elicitation meetings , 1995, Proceedings Seventh International Workshop on Computer-Aided Software Engineering.

[25]  Clay Spinuzzi,et al.  Context and consciousness: Activity theory and human-computer interaction , 1997 .

[26]  Bonnie A. Nardi Some reflections on the application of activity theory , 1995 .

[27]  J. Michael Spivey,et al.  The Z notation - a reference manual , 1992, Prentice Hall International Series in Computer Science.

[28]  Ann Macintosh,et al.  Human interface guidelines: the apple desktop interface , 1987 .

[29]  Yin Yin Wong Rough and ready prototypes: lessons from graphic design , 1992, CHI '92.

[30]  John Karat,et al.  Raison d'Etre: capturing design history and rationale in mutimedia narratives , 1994, CHI Conference Companion.

[31]  Thomas Erickson,et al.  Notes on design practice: stories and prototypes as catalysts for communication , 1995 .

[32]  Ian Sommerville,et al.  Software engineering, 4th Edition , 1992, International computer science series.

[33]  B. Nardi Context and consciousness: activity theory and human-computer interaction , 1995 .

[34]  Joyce Fortune,et al.  Understanding Systems Failures , 1988 .

[35]  Robert L. Campbell,et al.  WILL THE REAL SCENARIO PLEASE STAND UP? , 1992, ACM SIGCHI Bull..

[36]  Chris W. Johnson,et al.  Literate Development: Weaving Human Context into Design Specifications , 1996 .

[37]  Batya Friedman,et al.  Educating computer scientists: linking the social and the technical , 1994, CACM.

[38]  Patricia Sachs,et al.  Transforming work: collaboration, learning, and design , 1995, CACM.

[39]  Philip Weaver,et al.  Practical SSADM version 4+: a complete tutorial guide. 2nd edition , 1998 .

[40]  Allan MacLean,et al.  Design space analysis and use representations , 1995 .

[41]  Simon Buckingham Shum,et al.  Analyzing the Usability of a Design Rationale Notation , 1996 .

[42]  John L. Bennett,et al.  Usability Engineering: Our Experience and Evolution , 1988 .

[43]  Abraham Silberschatz,et al.  Database System Concepts , 1980 .

[44]  Susanne Bødker,et al.  Through the Interface: A Human Activity Approach To User Interface Design , 1990 .

[45]  A. F. Chalmers,et al.  What Is This Thing Called Science , 1976 .

[46]  Morten Kyng,et al.  Creating contexts for design , 1995 .

[47]  Gitta B. Salomon How the Look Affects the Feel: Visual Design and the Creation of an Information Kiosk , 1990 .

[48]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[49]  Tom Rodden,et al.  The role of ethnography in interactive systems design , 1995, INTR.

[50]  Susanne Bødker,et al.  Applying Activity Theory to Video Analysis , 1996 .

[51]  Sidney L. Smith,et al.  Guidelines for Designing User Interface Software , 1986 .

[52]  Raymonde Guindon,et al.  Designing the Design Process: Exploiting Opportunistic Thoughts , 1990, Hum. Comput. Interact..

[53]  Miles MacLeod,et al.  Usability measurement in context , 1994, Behav. Inf. Technol..

[54]  Victoria Bellotti,et al.  Integrating theoreticians' and practitioners' perspectives with design rationale , 1993, INTERCHI.

[55]  Bonnie A. Nardi,et al.  The use of scenarios in design , 1992, SGCH.

[56]  Christopher W. Johnson Literate Specification: Using Design Rationale to Support Formal Methods in the Development of Human-Machine Interfaces , 1996, Hum. Comput. Interact..

[57]  Steven J. Clarke Putting context into design , 1996, CHI Conference Companion.

[58]  M. Cole A cultural-historical approach to distributed cognition , 1993 .

[59]  John M. Carroll,et al.  Making use: a design representation , 1994, CACM.

[60]  B. Lomov The Problem of Activity in Psychology , 1982 .

[61]  Antonio C. Siochi,et al.  The UAN: a user-oriented representation for direct manipulation interface designs , 1990, TOIS.

[62]  Wanda J. Orlikowski,et al.  Learning from Notes: organizational issues in groupware implementation , 1992, CSCW '92.

[63]  C. A. R. Hoare,et al.  Communicating sequential processes , 1978, CACM.

[64]  J. W. van Aalst,et al.  Design space analysis as “training wheels” in a framework for learning user interface design , 1995, CHI '95.

[65]  Carys Siemieniuch,et al.  An investigation of user requirements for broadband communications in the automotive industry , 1990, INTERACT.

[66]  Rachel K. E. Bellamy,et al.  Designing educational technology: computer-mediated change , 1995 .