Information requirements analysis and multiple knowledge elicitation techniques: experience with the pricing scenario system

It is well understood that large percentage of software development costs are incurred during the earlier phases of the software development process, namely the information requirement analysis. Given the importance of information requirements analysis during software development process, it is surprising that there is limited research in this area to advance the knowledge for better equipping information systems project managers and analysts. This paper examines a software prototyping project held by one organization through use of structured interviews, group sessions, and scenario analysis techniques. As suggested by Davis (1982) and Byrd et al. (1992), combining multiple elicitation techniques at more than one level in the organization allowed explicit and tacit knowledge to be surfaced. A discussion of gathering information requirements by tapping into upper management, middle managers, and end-users' knowledge is provided leading to a development of an effective information system.

[1]  Robert W. Zmud,et al.  The Use of Mental Imagery to Facilitate Information Identification in Requirements Analysis , 1993, J. Manag. Inf. Syst..

[2]  Moshe Telem,et al.  Information requirements specification I: Brainstorming collective decision-making approach , 1988, Inf. Process. Manag..

[3]  B CooperRandolph,et al.  Management information requirements assessment , 1979 .

[4]  James H. Moor,et al.  Knowledge and the Flow of Information. , 1982 .

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

[6]  Robert D. Galliers,et al.  Information analysis: selected readings , 1987 .

[7]  M. C. Jensen,et al.  Specific and General Knowledge and Organizational Structure , 1995 .

[8]  Ware Myers,et al.  MCC: Planning the Revolution in Software , 1985, IEEE Software.

[9]  William P. Alston,et al.  Knowledge and the Flow of Information , 1985 .

[10]  Roland T. Mittermeir,et al.  Alternatives to Overcome the Communications Problem of Formal Requirements Analysis. , 1982 .

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

[12]  Joyce J. Elam,et al.  Inside a software design team: knowledge acquisition, sharing, and integration , 1993, CACM.

[13]  David Chenho Kung,et al.  Formal approach to scenario analysis , 1994, IEEE Software.

[14]  Otto Wassermann,et al.  The Intelligent Enterprise , 2001 .

[15]  H. D. Thomas,et al.  SUCCESSFUL KNOWLEDGE MANAGEMENT PROJECTS , 1998 .

[16]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

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

[18]  E. Burton Swanson,et al.  Management information requirements assessment: the state of the art , 1979, DATB.

[19]  Robert W. Zmud,et al.  A Synthesis of Research on Requirements Analysis and Knowledge Acquisition Techniques , 1992, MIS Q..

[20]  June M. Verner,et al.  Prototyping: Does Your View of its Advantages Depend on Your Job? , 1997, J. Syst. Softw..

[21]  Leonard J. Bass,et al.  Scenario-Based Analysis of Software Architecture , 1996, IEEE Softw..