Design exploration: engaging a larger user population

Software designers must understand the domain, work practices, and user expectations before determining requirements or generating initial design mock-ups. Users and other stakeholders are a valuable source of information leading to that understanding. Much work has focused on design approaches that include users in the software development process. These approaches vary from surveys and questionnaires that garner responses from a population of potential users to participatory design processes where representative users are included in the design/development team. The Design Exploration approach retains the remote and asynchronous communication of surveys while making expression of feedback easier by providing users alternatives to textual communication for their suggestions and tacit understanding of the domain. To do this, visual and textual modes of expression are combined to facilitate communication from users to designers while allowing a broad user audience to contribute to software design. One challenge to such an approach is how software designers make use of the potentially overwhelming combination of text, graphics, and other content. The Design Exploration process provides users and other stakeholders the Design Exploration Builder, a construction kit where they create annotated partial designs. The Design Exploration Analyzer is an exploration tool that allows software designers to consolidate and explore partial designs. The Analyzer looks for patterns based on textual analysis of annotations and spatial analysis of graphical designs, to help identify interesting examples and patterns within the collection. Then software designers can use this tool to search and browse within the exploration set in order to better understand the task domain, user expectations and work practices. Evaluation of the tools has shown that users will often work to overcome expression constraints to convey information. Moreover, the mode of expression influences the types of information garnered. Furthermore, including more users results in greater coverage of the information gathered. These results provide evidence that Design Exploration is an approach that collects software and domain information from a large group of users that lies somewhere between questionnaires and face to face methods.* *This dissertation is a compound document (contains both a paper copy and a CD as part of the dissertation). The CD requires the following system requirements: Windows MediaPlayer or RealPlayer.

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

[2]  Frank M. Shipman,et al.  A comparison of questionnaire-based and GUI-based requirements gathering , 2000, Proceedings ASE 2000. Fifteenth IEEE International Conference on Automated Software Engineering.

[3]  Brent Reeves,et al.  Supporting collaborative design by embedding communication and history in design artifacts , 1993 .

[4]  Karen Holtzblatt,et al.  Contextual design , 1997, INTR.

[5]  Frank M. Shipman,et al.  Formality Considered Harmful: Experiences, Emerging Themes, and Directions on the Use of Formal Representations in Interactive Systems , 1999, Computer Supported Cooperative Work (CSCW).

[6]  Susanne Bødker,et al.  Scenarios in user-centred design-setting the stage for reflection and action , 1999, Proceedings of the 32nd Annual Hawaii International Conference on Systems Sciences. 1999. HICSS-32. Abstracts and CD-ROM of Full Papers.

[7]  Michael J. Muller,et al.  “Equal opportunity” PD using PICTIVE , 1993, CACM.

[8]  Peter Johnson,et al.  Empowering users in a task-based approach to design , 1995, Symposium on Designing Interactive Systems.

[9]  Henry Lieberman,et al.  Watch what I do: programming by demonstration , 1993 .

[10]  Frank M. Shipman,et al.  Finding and using implicit structure in human-organized spatial layouts of information , 1995, CHI '95.

[11]  Frank M. Shipman,et al.  Requirements elicitation using visual and textual information , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[12]  J. Michael Moore,et al.  Communicating requirements using end-user GUI constructions with argumentation , 2003, 18th IEEE International Conference on Automated Software Engineering, 2003. Proceedings..

[13]  Pelle Ehn Playing the language-games of design and use-on skill and participation , 1988 .

[14]  Jonathan Grudin,et al.  Personas, Participatory Design and Product Development: An Infrastructure for Engagement , 2002 .

[15]  James A. Landay,et al.  SILK: sketching interfaces like krazy , 1996, CHI Conference Companion.

[16]  Frank M. Shipman,et al.  Supporting knowledge-base evolution with incremental formalization , 1994, CHI '94.

[17]  Frank M. Shipman,et al.  Beyond location: hypertext workspaces and non-linear views , 1999, HYPERTEXT '99.

[18]  Richard J. Boland,et al.  The Process and Product of System Design , 1978 .

[19]  Mary Beth Rosson,et al.  Participatory analysis: shared development of requirements from scenarios , 1997, CHI.

[20]  Scott P. Robertson,et al.  Proceedings of the SIGCHI Conference on Human Factors in Computing Systems , 1991 .

[21]  Frank M. Shipman,et al.  Spatial hypertext and the practice of information triage , 1997, HYPERTEXT '97.

[22]  Anthony Finkelstein,et al.  Software engineering: a roadmap , 2000, ICSE '00.

[23]  Steven M. Smith,et al.  Metrics for measuring ideation effectiveness , 2003 .

[24]  John M. Carroll,et al.  Five reasons for scenario-based design , 2000, Interact. Comput..

[25]  Kon Mouzakis,et al.  PICTIOL: a case study in participatory design , 2006, OZCHI.

[26]  Frank M. Shipman,et al.  Emergent Structure in Analytic Workspaces: Design and Use of the Visual Knowledge Builder , 2001, INTERACT.

[27]  Janni Nielsen,et al.  Getting access to what goes on in people's heads?: reflections on the think-aloud technique , 2002, NordiCHI '02.

[28]  Pelle Ehn,et al.  Scandinavian Design: On Participation and Skill , 1992, Usability - Turning Technologies into Tools.

[29]  Steven F. Roth,et al.  Example based generation of custom data analysis appliances , 2001, IUI '01.

[30]  L. Suchman,et al.  Interactional Troubles in Face-to-Face Survey Interviews , 1990 .

[31]  Karen Holtzblatt,et al.  Requirements gathering: the human factor , 1995, CACM.

[32]  Karen Holtzblatt,et al.  A tool supporting capture and analysis of field research data using the contextual design methodology , 2003, CHI Extended Abstracts.

[33]  L. Suchman Plans and situated actions , 1987 .

[34]  Michael J. Muller PICTIVE—an exploration in participatory design , 1991, CHI.

[35]  Joseph A. Goguen,et al.  Techniques for requirements elicitation , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[36]  Michael J. Muller,et al.  TelePICTIVE: computer-supported collaborative GUI design for designers with diverse expertise , 1992, UIST '92.

[37]  Axel van Lamsweerde,et al.  Requirements engineering in the year 00: a research perspective , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

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

[39]  Allen Cypher,et al.  Characterizing PBD systems , 1993 .

[40]  James A. Landay,et al.  Sketching Interfaces: Toward More Human Interface Design , 2001, Computer.

[41]  Mark A. McDaniel,et al.  Mental models, pictures, and text: Integration of spatial and verbal information , 1992, Memory & cognition.

[42]  Frank M. Shipman,et al.  Supporting communication between designers with artifact-centered evolving information spaces , 1992, CSCW '92.

[43]  H. Holbrook,et al.  A scenario-based methodology for conducting requirements elicitation , 1990, SOEN.

[44]  Anthony Finkelstein,et al.  Requirements engineering: a review and research agenda , 1994, Proceedings of 1st Asia-Pacific Software Engineering Conference.

[45]  Stephen Fickas,et al.  Goal-directed concept acquisition in requirements elicitation , 1991, Proceedings of the Sixth International Workshop on Software Specification and Design.

[46]  M. Polanyi Chapter 7 – The Tacit Dimension , 1997 .

[47]  Ian Sommerville,et al.  Social analysis in the requirements engineering process: from ethnography to method , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[48]  Michael Jackson,et al.  Four dark corners of requirements engineering , 1997, TSEM.

[49]  Alistair G. Sutcliffe,et al.  Requirements rationales: integrating approaches to requirement analysis , 1995, Symposium on Designing Interactive Systems.

[50]  Kenneth R. Stern,et al.  Low vs. high-fidelity prototyping debate , 1996, INTR.

[51]  James A. Landay,et al.  Interactive sketching for the early stages of user interface design , 1995, CHI '95.

[52]  Alan Cooper,et al.  The Inmates are Running the Asylum , 1999, Software-Ergonomie.

[53]  Mary Beth Rosson,et al.  Requirements development: stages of opportunity for collaborative needs discovery , 1997, DIS '97.

[54]  Frank M. Shipman,et al.  Navigable history: a reader's view of writer's time , 2000, New Rev. Hypermedia Multim..

[55]  Ian H. Witten,et al.  Managing Gigabytes: Compressing and Indexing Documents and Images , 1999 .

[56]  Colin Potts,et al.  ScenIC: a strategy for inquiry-driven requirements determination , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[57]  Frank M. Shipman,et al.  The visual knowledge builder: a second generation spatial hypertext , 2001, HYPERTEXT '01.

[58]  Richard C. Waters,et al.  The Requirements Apprentice: Automated Assistance for Requirements Acquisition , 1991, IEEE Trans. Software Eng..

[59]  Michael J. Muller,et al.  Participatory design: the third space in HCI , 2002 .

[60]  Pelle Ehn,et al.  Playing the language-games of design and use-on skill and participation , 1988, COCS '88.