On the purpose of object-oriented analysis

The paper discusses the general purpose of analysis and evaluates OOA with respect to this, arguing that OOA does not deliver what it claims to do. The two major problems are that OOA often does not meet the full needs of the analysis phase, and that the transition to design is not always as easy as promised. The last point is illustrated by a solution to the OOPSLA conference registration problem. Due to the mentioned shortcomings, OOA/OOD was not found sufficient for forming the basis of a common development methodology for three Norwegian software producers in a technology transfer project with our university. The suggestion made is that OOA should become problem-oriented rather than target-oriented.

[1]  Edward Yourdon,et al.  Object-oriented analysis , 2012 .

[2]  Kenneth S. Rubin.  Object behavior analysis , 1992, CACM.

[3]  David W. Embley,et al.  Object-oriented systems analysis - a model-driven approach , 1991, Yourdon Press Computing series.

[4]  Grady Booch,et al.  Object-oriented development , 1986, IEEE Transactions on Software Engineering.

[5]  G. Sindre,et al.  Object-oriented role modeling for the analysis and design of organizational information systems , 1993, [1993] Proceedings of the Twenty-sixth Hawaii International Conference on System Sciences.

[6]  Jacques Hagelstein,et al.  Declarative approach to information systems requirements , 1988, Knowl. Based Syst..

[7]  James E. Rumbaugh,et al.  Designing bugs and dueling methodologies , 1992 .

[8]  David W. Embley,et al.  Turnable formalism in object-oriented systems analysis: meeting the needs of both theoreticians and practitioners , 1992, OOPSLA.

[9]  Dennis de Champeaux,et al.  A comparative study of object-oriented analysis methods , 1992 .

[10]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[11]  Sidney C. Bailin,et al.  An object-oriented requirements specifications method , 1989, CACM.

[12]  W. W. Royce,et al.  Managing the development of large software systems , 1970 .

[13]  John Mylopoulos,et al.  Knowledge Representation as the Basis for Requirements Specifications , 1985, Computer.

[14]  V. De Antonellis,et al.  Validation of object-oriented dynamic specifications , 1993, [1993] Proceedings of the Twenty-sixth Hawaii International Conference on System Sciences.

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

[16]  Pericles Loucopoulos,et al.  Information systems development: a rule-based approach , 1988, Knowl. Based Syst..

[17]  Andreas L. Opdahl,et al.  Concepts for Real-World Modelling , 1993, CAiSE.

[18]  Rebecca Wirfs-Brock,et al.  Designing object-oriented software , 1990 .

[19]  F. W. Wierda,et al.  Playing with toy trains or an empirical investigation into the feasibility of dynamic modeling of information systems , 1993, [1993] Proceedings of the Twenty-sixth Hawaii International Conference on System Sciences.

[20]  Ralph E. Johnson,et al.  Surveying current research in object-oriented design , 1990, CACM.

[21]  Alan M. Davis,et al.  A Strategy for Comparing Alternative Software Development Life Cycle Models , 1988, IEEE Trans. Software Eng..

[22]  Derek Coleman,et al.  Introducing Objectcharts or how to use Statecharts in object-oriented design , 1992 .

[23]  Frank M. Lillehagen,et al.  A Generic Object Model for Engineering Design , 1992, TOOLS.

[24]  Gruia-Catalin Roman,et al.  A taxonomy of current issues in requirements engineering , 1985, Computer.

[25]  Geir Magne Hoeydalsvik.  OORAM: Object-Oriented Role Analysis and Modeling , 1994 .

[26]  Roelf J. Wieringa,et al.  Algebraic Foundations for Dynamic Conceptual Models , 1990 .

[27]  Simon McGinnes,et al.  How objective is object-oriented analysis? , 1992 .

[28]  David Harel,et al.  Statecharts: A Visual Formalism for Complex Systems , 1987, Sci. Comput. Program..

[29]  Ian M. Holland,et al.  Contracts: specifying behavioral compositions in object-oriented systems , 1990, OOPSLA/ECOOP '90.

[30]  Øystein Haugen,et al.  Engineering real time systems - an object-oriented methodology using SDL (2. pr.) , 1993, BCS practitioner series.

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

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

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

[34]  Mehmet Aksit,et al.  Obstacles in object-oriented software development , 1992, OOPSLA 1992.

[35]  Raghubir N. Mathur.  Methodology for Business System Development , 1987, IEEE Transactions on Software Engineering.

[36]  Stephen J. Mellor,et al.  Object lifecycles: modeling the world in states , 1992 .

[37]  Stephen W. Clyde,et al.  Turnable formalism in object-oriented systems analysis: meeting the needs of both theoreticians and practitioners , 1992, OOPSLA 1992.

[38]  R. G. G. Cattell,et al.  An Object-Oriented Interface to a Relational Database , 1991, On Object-Oriented Database System.

[39]  Simon MacGinnes,et al.  How Objective is Object-Oriented Analysis? , 1992, CAiSE.

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