From Rich User Requirements to System Requirements

In recent years the usage of information systems has changed dramatically. Today many information systems are developed for non-organizational users. These wide-area end-users are often socially, as well as geographically very widely dispersed, which makes it for organizations that develop information systems extremely difficult to know who their users are, or what they expect. Previous research has claimed that rich user requirements information is necessary, in order to understand how to serve this audience right. However, at the same time current requirements engineering methods, capable of providing this rich information, do not serve the needs of designers and developers, who actually implement the services and who need precise knowledge of system requirements. We found that there is a severe gap in the communication of requirements between end-user, analyst, and designer. We used the design science research agenda to develop a method for extending one advanced requirements engineering method, WARE, to provide support for the full spectrum of communication. Our study presents the results of an ongoing research program, studying the innovation possibilities of Mobile Presence technology. Our method enables analysts to make the transition from rich user requirements to system requirements, which designers and developers can use in their implementation work.

[1]  Tuure Tuunanen,et al.  Developing Innovative Information Systems Services Together with Wide Audience End-Users , 2005, Proceedings of the 38th Annual Hawaii International Conference on System Sciences.

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

[3]  Marjo Kauppinen,et al.  Linking the business view to requirements engineering: long-term product planning by roadmapping , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[4]  H. Merisalo-Rantanen,et al.  Gathering innovative end-user feedback for continuous development of information systems: a repeatable and transferable e-collaboration process , 2005, IEEE Transactions on Professional Communication.

[5]  Brian R. Gaines,et al.  Requirements acquisition , 1996, Softw. Eng. J..

[6]  Jan Jürjens,et al.  UMLsec: Extending UML for Secure Systems Development , 2002, UML.

[7]  Salvatore T. March,et al.  Design and natural science research on information technology , 1995, Decis. Support Syst..

[8]  John Mylopoulos,et al.  From object-oriented to goal-oriented requirements analysis , 1999, CACM.

[9]  M. Rossi,et al.  An Advanced Requirements Elicitation Method and Tool , 2003 .

[10]  Cris Kobryn,et al.  Architecting Systems with UML 2.0 , 2003, IEEE Softw..

[11]  Tuure Tuunanen,et al.  Wide Audience Requirements Engineering (WARE): A Practical Method and Case Study , 2008 .

[12]  Jan Stage,et al.  Prototyping and Specifying: Principles and Practices of a Mixed Approach , 1995, Scand. J. Inf. Syst..

[13]  Jonathan Grudin,et al.  Interactive systems: bridging the gaps between developers and users , 1991, Computer.

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

[15]  Sandeep Purao,et al.  Design Research in the Technology of Information Systems: Truth or Dare , 2002 .

[16]  Colin Atkinson,et al.  Model-Driven Development: A Metamodeling Foundation , 2003, IEEE Softw..

[17]  Jaco H. Appelman,et al.  Designing mobile information services: user requirements elicitation with GSS design and application of a repeatable process , 2004 .

[18]  Shailey Minocha,et al.  Supporting Scenario-Based Requirements Engineering , 1998, IEEE Trans. Software Eng..

[19]  Alan R. Hevner,et al.  Design Science in Information Systems Research , 2004, MIS Q..

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

[21]  Tuure Tuunanen,et al.  Engineering a method for wide audience requirements elicitation and integrating it to software development , 2004, 37th Annual Hawaii International Conference on System Sciences, 2004. Proceedings of the.

[22]  Bran Selic,et al.  The Pragmatics of Model-Driven Development , 2003, IEEE Softw..

[23]  Alan W. Brown Large Scale Component Based Development , 2000 .

[24]  Axel van Lamsweerde,et al.  Managing Conflicts in Goal-Driven Requirements Engineering , 1998, IEEE Trans. Software Eng..

[25]  Richard L. Daft,et al.  Organizational information requirements, media richness and structural design , 1986 .

[26]  Klaus Pohl,et al.  Requirements Elicitation and Validation with Real World Scenes , 1998, IEEE Trans. Software Eng..

[27]  Axel van Lamsweerde,et al.  Handling Obstacles in Goal-Oriented Requirements Engineering , 2000, IEEE Trans. Software Eng..

[28]  Tuure Tuunanen,et al.  Developing Feature Sets for Geographically Diverse External End Users: A Call for Value-Based Preference Modeling , 2006 .

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

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

[31]  Ian Sommerville,et al.  Software engineering (6th ed.) , 2001 .

[32]  Martin Gogolla,et al.  Validating UML Models and OCL Constraints , 2000, UML.

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

[34]  Gordon B. Davis,et al.  Strategies for Information Requirements Determination , 1982, IBM Syst. J..

[35]  Wanda J. Orlikowski,et al.  Research Commentary: Desperately Seeking the "IT" in IT Research - A Call to Theorizing the IT Artifact , 2001, Inf. Syst. Res..