A Method and Tool for Wide Audience Requirements Elicitation and Rapid Prototyping for Mobile Systems

In recent years, consumer oriented information systems development has become increasingly important matter, as more and more complex information systems are targeted towards consumer markets. We argue that developing IS for non-organizational users creates new problems, which IS and requirement engineering (RE) community should attend to. First of all, the elicitation of requirements becomes more difficult as usually consumers do not explicitly know what they want, and it is difficult for them to express their ideas. To support different views of product development, project management and design, the method should present requirements in a ‘rich enough’ way to avoid overloading management, but in the same time giving designers the detailed information they need. Furthermore, to facilitate iterative requirements development the method should allow for rapid development of prototypes from designs. To support these goals we have constructed an enhanced requirements elicitation and mobile system construction method and its support environment within Metaedit+ Meta CASE tool. We based our method on Critical Success Chains (CSC) method, which supports top-down approach for planning, but also provides for wide participation of IS customers to get rich information. The high level results of CSC are turned into mobile applications running in Symbian platform by using a novel domain specific method that supports generation of executable environments from specifications.

[1]  E. Rogers New Product Adoption and Diffusion , 1976 .

[2]  Klaus Pohl,et al.  The three dimensions of requirements engineering: a framework and its applications , 1994, Inf. Syst..

[3]  Ke Te Le Mei Ru He Deng Yi Marketing management: analysis. planning. implementation and control , 2000 .

[4]  Tuure Tuunanen,et al.  Extending Critical Success Factors Methodology to Facilitate Broadly Participative Information Systems Planning , 2003, J. Manag. Inf. Syst..

[5]  D. MacInnis,et al.  Characteristics of portrayed emotions in commercials: when does what is shown in ads affect viewers? , 1995 .

[6]  Brian Everitt,et al.  Cluster analysis , 1974 .

[7]  Tuure Tuunanen,et al.  Planning for IS applications: a practical, information theoretical method and case study in mobile financial services , 2005, Inf. Manag..

[8]  Joseph A. Goguen,et al.  Requirements engineering: social and technical issues , 1994 .

[9]  Juhani Iivari,et al.  Hierarchical spiral model for information system and software development. Part 1: Theoretical background , 1990 .

[10]  J. N. Brinkkemper,et al.  Formalisation of information systems modelling , 1990 .

[11]  Görel Hedin,et al.  Incremental Semantic Analysis , 1992 .

[12]  J. Rockart Chief executives define their own data needs. , 1979, Harvard business review.

[13]  Tuure Tuunanen,et al.  Using Rich Information to Plan Mobile Financial Services Applications with Maximum Positive Impact: A Case Study , 2002 .

[14]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[15]  Glenn J. Browne,et al.  An Empirical Investigation of User Requirements Elicitation: Comparing the Effectiveness of Prompting Techniques , 2001, J. Manag. Inf. Syst..

[16]  M. Aldenderfer,et al.  Cluster Analysis. Sage University Paper Series On Quantitative Applications in the Social Sciences 07-044 , 1984 .

[17]  Matti Rossi,et al.  Mobile banking services , 2004, CACM.

[18]  Tuure Tuunanen,et al.  A New Perspective on Requirements Elicitation Methods , 2003 .

[19]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[20]  Wanda J. Orlikowski,et al.  CASE Tools as Organizational Change: Investigating Incremental and Radical Changes in Systems Development , 1993, MIS Q..

[21]  Venkataraman Ramesh,et al.  Improving information requirements determination: a cognitive perspective , 2002, Inf. Manag..

[22]  Matthias Jarke,et al.  Toward Reference Models of Requirements Traceability , 2001, IEEE Trans. Software Eng..

[23]  Suzanne Robertson,et al.  Mastering the Requirements Process , 1999 .

[24]  Martin Höst,et al.  An Industrial Case Study on Distributed Prioritisation in Market-Driven Requirements Engineering for Packaged Software , 2001, Requirements Engineering.

[25]  Erik L. Olson,et al.  Implementing the lead user method in a high technology firm: A longitudinal study of intentions versus actions , 2001 .

[26]  G. Kelly The Psychology of Personal Constructs , 2020 .

[27]  Colin J. Neill,et al.  Requirements Engineering: The State of the Practice , 2003, IEEE Softw..

[28]  J. Rockart The changing role of the information systems executive : a critical success factors perspective , 1982 .

[29]  S. Lauesen Software Requirements Styles and Techniques , 2001 .

[30]  T. J. Reynolds,et al.  Consumer Understanding and Advertising Strategy: Analysis and Strategic Translation of Laddering Data , 2001 .

[31]  Ken Peffers,et al.  How to identify new high-payoff information systems for the organization , 2003, CACM.

[32]  Soren Lauesen,et al.  Software Requirements: Styles & Techniques , 2002 .

[33]  T. J. Reynolds,et al.  Laddering theory, method, analysis, and interpretation. , 2001 .

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