Supporting the Collaborative Collection of User ' s Requirements

Most of the software systems development processes carry high risks for technological companies and service organizations. Some of these risks may ultimately produce delayed or failed projects with low quality software products. The Standish Group in 1999 presented the “Chaos Report”, which determined through a large scale scan on IT projects in northern hemisphere corporations that the software development industry continued to be marked by low quality products and services. According to this report, the main causes of failed projects during 1994 were the following: incomplete requirements (13,1%), little users participation (12,4%), lack of resources (10,6%), non-realistic expectations (9,9%), insufficient executive support (12.4%), changes in requirements and specifications (8,7%), lack of planning (8,1%), little administration of information technology (6,2%), technological incomprehension (4,3%), others (9,9%). It is important to note that a high percentage of errors are related to definition and administration of requirements and little user’s participation. Even though this study was performed some years ago, most of the current software projects are still dealing with the same risks. It is clear that any improvement in requirement engineering may substantially reduce the high risk that menace the quality of decision taken during the negotiations of the user’s final requirements. Requirement engineering includes the following steps (see e.g. Nuseibeh and Easterbrook, 2000): • Collect requirements: identify the stakeholders and obtain their requirements. • Model and analyze the requirements: build abstract descriptions for a better interpretation. • Communicate the requirements: transfer the knowledge among the stakeholders. • Come to an agreement on the requirements: negotiate the requirements with the stakeholders. • Evolve the requirements: manage changes not only in the requirements but also in the environment, or changes generated by the stakeholders.

[1]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[2]  Jay F. Nunamaker,et al.  Implementing Electronic Meeting Systems at IBM: Lessons Learned and Success Factors , 1990, MIS Q..

[3]  Jay F. Nunamaker,et al.  Bringing automated support to large groups: The Burr-Brown experience , 1990, Inf. Manag..

[4]  Alan M. Davis,et al.  Operational prototyping: a new development approach , 1992, IEEE Software.

[5]  Brad Quinn Post,et al.  Building the business case for group support technology , 1992, Proceedings of the Twenty-Fifth Hawaii International Conference on System Sciences.

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

[7]  I. Nonaka.  A Dynamic Theory of Organizational Knowledge Creation , 1994 .

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

[9]  Jay F. Nunamaker,et al.  Invoking Social Comparison to Improve Electronic Brainstorming: Beyond Anonymity , 1995, J. Manag. Inf. Syst..

[10]  Roger C. Schank,et al.  Virtual Learning: A Revolutionary Approach to Building a Highly Skilled Workforce , 1997 .

[11]  Gert-Jan de Vreede,et al.  Why Some GSS Meetings Just Don't Work: Exploring Success Factors of Electronic Meetings , 1997, ECIS.

[12]  David L. Morgan,et al.  Planning Focus Groups , 1997 .

[13]  Barry W. Boehm,et al.  Using the WinWin Spiral Model: A Case Study , 1998, Computer.

[14]  D. Straub,et al.  Knowledge Worker Communications and Recipient Availability: Toward a Task Closure Explanation of Media Choice , 1998 .

[15]  Jay F. Nunamaker,et al.  A Technology Transition Model Derived from Field Investigation of GSS Use About the U , 1998 .

[16]  Jay F. Nunamaker,et al.  A Technology Transition Model Derived from Field Investigation of GSS Use Aboard the U.S.S. CORONADO , 1998, J. Manag. Inf. Syst..

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

[18]  Jay F. Nunamaker,et al.  ThinkLets: achieving predictable, repeatable patterns of group interaction with group support systems (GSS) , 2001, Proceedings of the 34th Annual Hawaii International Conference on System Sciences.

[19]  Robert O. Briggs,et al.  Surfacing tacit knowledge in requirements negotiation: experiences using EasyWinWin , 2001, Proceedings of the 34th Annual Hawaii International Conference on System Sciences.

[20]  Tony P. Pridmore,et al.  Classroom collaboration in the design of tangible interfaces for storytelling , 2001, CHI.

[21]  Barry W. Boehm,et al.  Developing Groupware for Requirements Negotiation: Lessons Learned , 2001, IEEE Softw..

[22]  John C. Thomas,et al.  The knowledge management puzzle: Human and social factors in knowledge management , 2001, IBM Syst. J..

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

[24]  Joseph D. Langford,et al.  Focus Groups: Supporting Effective Product Development , 2002 .

[25]  Deana McDonagh,et al.  Organising and Conducting a Focus Group: The Logistics , 2002 .

[26]  Sumantra Ghoshal,et al.  Improving the Quality of Conversations , 2002 .

[27]  Robert M. Davison,et al.  How a silver bullet may lose its shine , 2003, CACM.

[28]  Martin Maguire.  The use of focus groups for user requirements analysis , 2003 .

[29]  Jay F. Nunamaker,et al.  Collaboration Engineering with ThinkLets to Pursue Sustained Success with Group Support Systems , 2003, J. Manag. Inf. Syst..

[30]  Designing mobile information services: user requirements elicitation with GSS design and application of a repeatable process , 2004, 37th Annual Hawaii International Conference on System Sciences, 2004. Proceedings of the.

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

[32]  Flávia Maria Santoro,et al.  Applying Group Storytelling in Knowledge Management , 2004, CRIWG.

[33]  Wolfgang Prinz,et al.  Group storytelling for team awareness and entertainment , 2004, NordiCHI '04.

[34]  Marina Basu.  The Embodied Mind: Cognitive Science and Human Experience , 2004 .

[35]  Carlos E. Acosta,et al.  StoryMapper: a multimedia tool to externalize knowledge , 2004, XXIV International Conference of the Chilean Computer Science Society.

[36]  Robert O. Briggs,et al.  Collaboration Engineering: Designing Repeatable Processes for High-Value Collaborative Tasks , 2005, Proceedings of the 38th Annual Hawaii International Conference on System Sciences.