An Experimental Investigation into the Effectiveness of OOA for Specifying Requirements

The application of object oriented concepts (OO) to the requirements phase of information systems (IS) and software development has been adopted by many proponents of IS and software development methodologies. Although many claims have been made about the effectiveness of OO techniques for improving requirements analysis, very few experimental studies have been done to substantiate these claims. This paper addresses this gap in the literature by conducting an experimental study that attempts to validate the effectiveness of object-oriented analysis (OOA) by comparing it to structured analysis (SA) for producing requirements. We argue that the quality of the requirements specification can be measured and that measurement can be used to compare the effectiveness of OOA and SA. We present an overview of the basic models and principles associated with OOA and SA, a discussion of quality in requirements definition, and a detailed discussion of the research methodology used. A review of relevant research is also presented and directions for further research are suggested. Our findings suggest that the OOA methodology does not necessarily produce better requirements statements.

[1]  Andrew T. F. Hutt Object analysis and design: description of methods , 1994 .

[2]  Leonard Adelman,et al.  Experiments, quasi-experiments, and case studies: A review of empirical methods for evaluating decision support systems , 1991, IEEE Trans. Syst. Man Cybern..

[3]  Juhani Iivari,et al.  Object-orientation as structural, functional and behavioural modelling: a comparison of six methods for object-oriented analysis , 1995, Inf. Softw. Technol..

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

[5]  Jean-Marc Nerson,et al.  Object-Oriented Analysis and Design , 1992, TOOLS.

[6]  Jeffrey A. Hoffer,et al.  An Examination of Procedural and Object‐oriented Systems Analysis Methods: Does Prior Experience Help or Hinder Performance?* , 1999 .

[7]  Glenn J. Browne,et al.  Conceptual foundations of design problem solving , 1993, IEEE Trans. Syst. Man Cybern..

[8]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[9]  William E. Lorensen,et al.  Object-Oriented Modeling and Design , 1991, TOOLS.

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

[11]  Richard A. Johnson,et al.  The ups and downs of object-oriented systems development , 2000, CACM.

[12]  Gill Smith,et al.  Object-oriented analysis , 1988, WADAS '88.

[13]  Ken Orr,et al.  Methodology: the experts speak , 1989 .

[14]  Gerardine DeSanctis,et al.  ICIS Paper: Methodological Issues in Experimental IS Research: Experiences and Recommendations , 1985, MIS Q..

[15]  Grady Booch,et al.  Object-Oriented Analysis and Design with Applications , 1990 .

[16]  Brian Henderson-Sellers,et al.  The object-oriented systems life cycle , 1990, CACM.

[17]  Ivar Jacobson,et al.  The Unified Modeling Language User Guide , 1998, J. Database Manag..

[18]  David W. Embley,et al.  OO Systems Analysis: Is It or Isn't It? , 1995, IEEE Softw..

[19]  Shouhong Wang,et al.  Toward Formalized Object-Oriented Management Information Systems Analysis , 1996, J. Manag. Inf. Syst..

[20]  Alan M. Davis,et al.  Software Requirements: Objects, Functions and States , 1993 .

[21]  David E. Monarchi,et al.  A research typology for object-oriented analysis and design , 1992, CACM.

[22]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

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

[24]  Mark Mayfield,et al.  Object Models: Strategies, Patterns, and Applications , 1995 .

[25]  Ivar Jacobson,et al.  Object-Oriented Software Engineering , 1991, TOOLS.

[26]  Bernd Bruegge,et al.  Object Oriented Software Engineering, Conquering Complex and Changing Systems , 2002 .

[27]  Erik Kamsties,et al.  A Framework for Evaluating System and Software Requirements Specification Approaches , 1997, Requirements Targeting Software and Systems Engineering.

[28]  Grady Booch,et al.  Object-oriented analysis and design with applications (2nd ed.) , 1993 .

[29]  Ritu Agarwal,et al.  Comprehending Object and Process Models: An Empirical Study , 1999, IEEE Trans. Software Eng..

[30]  Edward Yourdon,et al.  Modern structured analysis , 1989 .

[31]  Edward Yourdon,et al.  Object-oriented design , 1991, Yourdon Press Computing Series.

[32]  Ali Bahrami,et al.  Object Oriented Systems Development , 1998 .

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

[34]  Jeffrey L. Whitten,et al.  Systems Analysis and Design Methods , 1986 .

[35]  Arne Sølvberg,et al.  Understanding quality in conceptual modeling , 1994, IEEE Software.

[36]  Chris F. Kemerer,et al.  Object-oriented and conventional analysis and design methodologies , 1992, Computer.

[37]  T. M. Rajkumar,et al.  Comparison of analysis techniques for information requirement determination , 1988, CACM.

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

[39]  Ivar Jacobson,et al.  The object advantage - business process reengineering with object technology , 1994 .

[40]  Tom DeMarco,et al.  Structured Analysis and System Specification , 1978 .

[41]  L. B. Hunt Getting the requirements right-a professional approach , 1997, Proceedings Eighth IEEE International Workshop on Software Technology and Engineering Practice incorporating Computer Aided Software Engineering.

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