Comparing task practicing and prototype fidelities when applying scenario acting to elicit requirements

Identifying accurate user requirements early in the design cycle is of the utmost importance in system development. The purpose of this study of requirements elicitation was to compare the results of involving the user early in the design cycle using a low-fidelity prototype with the results of involving the user after a high-fidelity prototype was available. Three groups of potential users applied the method of Scenario Acting. Participants in the first group were given a working prototype of a human capital development system. The participants of the second group were given a detailed description of proposed features of the system and were told to practice on a paper prototype or with current methods, such as an Internet browser. These groups then practiced the tasks for some time before participating in the Scenario Acting. The third group received a brief description of the objectives of the system and did not practice the tasks. The results of the study showed that the use of the high-fidelity prototype was not helpful for eliciting requirements when working with users. However, the second group, taking time to practice the tasks given a low-fidelity paper prototype outperformed the others. Furthermore, the analysis of the Scenario Acting sessions revealed that two sessions were better than one, especially for participants of the group working with a low-fidelity prototype. An analysis of the topic of requirements showed that there was no difference between the groups on the domain tasks (here, human capital development), but the group practicing on the high-fidelity prototype commented more on its ease of use and usefulness than the other two. By comparison, the group practicing on low-fidelity prototype had more comments on the practice of the work and output of the tasks.

[1]  Gry Seland,et al.  System designer assessments of role play as a design method: a qualitative study , 2006, NordiCHI '06.

[2]  Paul Beynon-Davies,et al.  Prototyping Praxis: Constructing Computer Systems and Building Belief , 2000, Hum. Comput. Interact..

[3]  Yvonne Rogers,et al.  Beyond Interaction Design: Beyond Human-Computer Interaction , 2001 .

[4]  Neil A. M. Maiden,et al.  Provoking Creativity: Imagine What Your Requirements Could Be Like , 2004, IEEE Softw..

[5]  Youn-Kyung Lim,et al.  Comparative analysis of high- and low-fidelity prototypes for more valid usability evaluations of mobile devices , 2006, NordiCHI '06.

[6]  Betty H. C. Cheng,et al.  Research Directions in Requirements Engineering , 2007, Future of Software Engineering (FOSE '07).

[7]  Karin Garmer,et al.  User participation in requirements elicitation comparing focus group interviews and usability tests for eliciting usability requirements for medical equipment: a case study , 2004 .

[8]  Sari Kujala,et al.  User involvement: A review of the benefits and challenges , 2003, Behav. Inf. Technol..

[9]  Austin Henderson,et al.  Interaction design: beyond human-computer interaction , 2002, UBIQ.

[10]  Natalia Juristo Juzgado,et al.  Effectiveness of Requirements Elicitation Techniques: Empirical Results Derived from a Systematic Review , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

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

[12]  Ebba Þóra Hvannberg,et al.  Heuristic evaluation: Comparing ways of finding and reporting usability problems , 2007, Interact. Comput..

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

[14]  Yvonne Rogers,et al.  Eliciting reactive and reflective feedback for a social communication tool: a multi-session approach , 2004, DIS '04.

[15]  Kasper Hornbæk,et al.  Two psychology-based usability inspection techniques studied in a diary experiment , 2004, NordiCHI '04.

[16]  J F Suri,et al.  Scenario building as an ergonomics method in consumer product design. , 2000, Applied ergonomics.

[17]  Khaled El Emam,et al.  A Replicated Survey of IT Software Project Failures , 2008, IEEE Software.

[18]  Luqi,et al.  Requirements-document-based prototyping of CARA software , 2003, International Journal on Software Tools for Technology Transfer.

[19]  Michael Schrage Never Go to a Client Meeting without a Prototype , 2004, IEEE Softw..

[20]  Roger R. Hall,et al.  Prototyping for usability of new technology , 2001, Int. J. Hum. Comput. Stud..

[21]  David E. Avison,et al.  Action research , 1999, CACM.

[22]  Sri Hastuti Kurniawan,et al.  Review of Interaction design , 2003 .

[23]  Barry W. Boehm Understanding and Controlling Software Costs , 1988 .

[24]  Esther E. Klein,et al.  The use of group support systems in focus groups: Information technology meets qualitative research , 2007, Comput. Hum. Behav..

[25]  Yvonne Rogers,et al.  Interaction Design: Beyond Human-Computer Interaction , 2002 .

[26]  R.N. Charette,et al.  Why software fails [software failure] , 2005, IEEE Spectrum.

[27]  Edgar Erdfelder,et al.  G*Power 3: A flexible statistical power analysis program for the social, behavioral, and biomedical sciences , 2007, Behavior research methods.

[28]  Jan Pries-Heje,et al.  Grounded action research: a method for understanding IT in practice , 1999 .

[29]  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.

[30]  Jan Gulliksen,et al.  A participatory process supporting design of future work , 2007 .

[31]  Maryam Alavi,et al.  An assessment of the prototyping approach to information systems development , 1984, CACM.

[32]  Jacob Cohen Statistical Power Analysis for the Behavioral Sciences , 1969, The SAGE Encyclopedia of Research Design.

[33]  Dag Svanæs,et al.  Putting the users center stage: role playing and low-fi prototyping enable end users to design mobile systems , 2004, CHI.

[34]  J. Donalek,et al.  An introduction to qualitative research methods. , 2004, Urologic nursing.

[35]  Tore Dybå,et al.  A systematic review of quasi-experiments in software engineering , 2009, Inf. Softw. Technol..

[36]  Tetsuo Tamai,et al.  How Does Requirements Quality Relate to Project Success or Failure? , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).

[37]  Giulio Jacucci,et al.  Imagining and experiencing in design, the role of performances , 2002, NordiCHI '02.

[38]  Neil A. M. Maiden,et al.  Exploring how to use scenarios to discover requirements , 2009, Requirements Engineering.