An assessment model for requirements identification in component-based software development

Software development literature is replete with studies that demonstrate how ineffective requirements analysis (RA) has led to failed applications. Some of the difficulties encountered in RA however are due to inherent limitations in traditional approach to software development. On the other hand, component-based software development (CBSD) presents a unique approach to developing software. Components advertise the services they offer and could be organized in a knowledge-base (i.e., repository). CBSD paradigm provides an effective communication vehicle for users and analysts by enabling them to uncover requirements as they navigate through the component knowledge-base.In this paper, we draw from the information processing theory (IPT) on problem solving to develop an assessment model for evaluating the impact of CBSD on requirements identification, arguing that the access to components in a knowledge-base facilitates the requirements identification. The key elements of the IPT on problem solving are information processing system of the problem solver, task environment and internal representation of the problem space. We propose that access to a component knowledge-base enhances information processing system of the problem solver and simplifies the task environment which together improve user's internal representation of the problem space. This theoretical framework makes it possible to empirically test the impact of CBSD on requirements identification process.

[1]  Jay F. Nunamaker,et al.  Supporting Joint Application Development (JAD) with Electronic Meeting Systems: A Field Study , 1992, ICIS.

[2]  H. Simon,et al.  Administrative Behavior: A Study of Decision-Making Processes in Administrative Organization. , 1959 .

[3]  Iris Vessey,et al.  Learning to Specify Information Requirements: The Relationship between Application and Methodology , 1993, J. Manag. Inf. Syst..

[4]  Gordon B. Davis,et al.  Determining Management Information Needs: A Comparison of Methods , 1977, MIS Q..

[5]  Roland Mittermeir,et al.  A survey of software reuse libraries , 1998, Ann. Softw. Eng..

[6]  H. Joel Jeffrey,et al.  Relationship definition and management: Tools for requirements analysis , 1994, J. Syst. Softw..

[7]  Allen Newell,et al.  Elements of a theory of human problem solving. , 1958 .

[8]  Ritu Agarwal,et al.  Cognitive Fit in Requirements Modeling: A Study of Object and Process Methodologies , 1996, J. Manag. Inf. Syst..

[9]  C. G. Walters,et al.  Consumer behavior: theory and practice , 1974 .

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

[11]  John R. Valusek,et al.  Information requirements determination: obstacles within, among and between participants , 1985, SIGCPR '85.

[12]  Paul Allen,et al.  Component-Based Development for Enterprise Systems: Applying the SELECT Perspective , 1997 .

[13]  Michael Sparling,et al.  Lessons learned through six years of component-based development , 2000, CACM.

[14]  Clemens A. Szyperski,et al.  Component software - beyond object-oriented programming , 2002 .

[15]  Roland Mittermeir,et al.  Storing and retrieving software components: a refinement based system , 1994, ICSE '94.

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

[17]  Jon Hopkins,et al.  Component primer , 2000, CACM.

[18]  Gary Stephen Turner.  Prototyping :a better way to develop software , 1987 .

[19]  Oscar Gutierrez,et al.  Experimental techniques for information requirements analysis , 1989, Inf. Manag..

[20]  David W. Conrath,et al.  The Use of Cognitive Mapping for Information Requirements Analysis , 1986, MIS Q..

[21]  Robert J. Kauffman,et al.  Supporting Search for Reusable Software Objects , 1996, IEEE Trans. Software Eng..

[22]  Allen Newell,et al.  THE THEORY OF HUMAN PROBLEM SOLVING , 1988 .

[23]  Bruce I. Blum,et al.  Software engineering - a holistic view , 1992 .

[24]  Erran Carmel,et al.  PD and joint application design: a transatlantic comparison , 1993, CACM.

[25]  Robert C. Mecham,et al.  A study of job characteristics and job dimensions as based on the Position Analysis Questionnaire (PAQ). , 1972 .

[26]  John Dodd.  Developing information systems from components: the role of CASE , 1994 .

[27]  Allen Newell,et al.  Human problem solving: The state of the theory in 1970. , 1971 .

[28]  James T. C. Teng,et al.  Choice Of An Information Requirements Analysis Method: An Integrated Approach , 1988 .

[29]  Iris Vessey,et al.  Requirements specification: learning object, process, and data methodologies , 1994, CACM.

[30]  S. Palmer,et al.  The information processing approach to cognition , 1984 .

[31]  Dave K. Kythe.  The promise of distributed business components , 1996, AT&T Tech. J..

[32]  G. Marakas.  Decision Support Systems in the 21st Century , 1998 .

[33]  Herbert A. Simon,et al.  Information-Processing Theory of Human Problem Solving , 1978 .

[34]  Patricia J. Guinan,et al.  Enabling Software Development Team Performance During Requirements Definition: A Behavioral Versus Technical Approach , 1998, Inf. Syst. Res..

[35]  Joyce J. Elam,et al.  Semantic Structuring in Analyst Acquisition and Representation of Facts in Requirements Analysis , 1998, Inf. Syst. Res..

[36]  Eva Hudlicka,et al.  Requirements elicitation with indirect knowledge elicitation techniques: comparison of three methods , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[37]  Ernest A. Edmonds,et al.  Creativity enhancement with emerging technologies , 2000, CACM.

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

[39]  Johannes Sametinger,et al.  Software Engineering with Reusable Components , 1997, Springer Berlin Heidelberg.

[40]  Karen Holtzblatt,et al.  Requirements gathering: the human factor , 1995, CACM.

[41]  William B. Frakes,et al.  An Empirical Study of Representation Methods for Reusable Software Components , 1994, IEEE Trans. Software Eng..

[42]  Hemant Jain,et al.  Designing and managing reusable business components , 2000 .

[43]  Ronald A. Ash,et al.  A note on the readability on the Position Analysis Questionnaire (PAQ). , 1975 .

[44]  H. Holbrook,et al.  A scenario-based methodology for conducting requirements elicitation , 1990, SOEN.

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

[46]  Len Bass,et al.  Volume I: Market Assessment of Component-Based Software Engineering , 2001 .

[47]  Nickolas Makrygiannis,et al.  Toward mass-customized information systems , 1998 .

[48]  Blake Ives,et al.  User Involvement and MIS Success: A Review of Research , 1984 .

[49]  Prodromos D. Chatzoglou,et al.  A DEA Framework to Assess the Efficiency of the Software Requirements Capture and Analysis Process , 1999 .

[50]  Ronald A. Ash,et al.  Evaluation Of Job Analysis Methods By Experienced Job Analysts , 1983 .

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

[52]  Paul H. Cheney,et al.  A Theoretically Grounded Approach to Assist Memory Recall During Information Requirements Determination , 1998, J. Manag. Inf. Syst..

[53]  G. C. Thornton,et al.  Influence of job characteristics on the acceptability of employee drug testing. , 1991, The Journal of applied psychology.

[54]  Alan M. Davis,et al.  Software requirements - analysis and specification , 1990 .

[55]  Allen Newell,et al.  Human Problem Solving. , 1973 .

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

[57]  Randolph B. Cooper,et al.  Information Technology Development Creativity: A Case Study of Attempted Radical Change , 2000, MIS Q..

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

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