Structured analysis and object oriented analysis

  • Authors:
  • Dennis de Champeaux;Larry Constantine;Ivar Jacobson;Stephen Mellor;Paul Ward;Edward Yourdon

  • Affiliations:
  • Hewlett-Packard Laboratories, Moderator;Independent Consultant;Objective Systems SF AB;Project Technology, Inc;Software Development Concepts;American Programmer

  • Venue:
  • OOPSLA/ECOOP '90 Proceedings of the European conference on object-oriented programming on Object-oriented programming systems, languages, and applications
  • Year:
  • 1990

Quantified Score

Hi-index 0.00

Visualization

Abstract

The object-oriented paradigm still faces an open challenge: Delivering huge software systems routinely and cost effectively. To quote Ed Yourdon: “A system composed of 100,000 lines of C++ is not be sneezed at, but we don't have that much trouble developing 100,000 lines of COBOL today. The real test of OOP will come when systems of 1 to 10 million lines of code are developed.”Although the object-oriented community has an opening flirtation with exploratory programming and rapid prototyping by exploiting reuse via inheritance, there is for now, in my opinion, no hope that huge systems can be developed without giving due attention to what a target system is supposed to do. Which should produce an (electronic) (graphical) (Pseudo-formal) document, the requirements, that a customer can initially sign off. We believe as well that for huge systems a programming language independent design activity, that bridges the requirements and the actual programming effort, is mandatory. It goes without saying that we do not suggest that these activities constitute a waterfall sequence.Consequently, the object-oriented community needs to address the question whether well established analysis techniques, like Structured Analysis, Jackson's JSD, etc. can be reused for object-oriented system development or whether a dedicated object-oriented analysis (and design) method is called for.The panel members have been asked to consider the following of question: What is the relationship between Structured Analysis (SA) and Object Oriented Analysis (OOA)?More specifically:Can SA be used effectively to produce the requirements for a system that will be designed and implemented in an OO fashion?If not, is it possible to adjust SA, what needs to be added? If SA cannot be used at all, what is the key obstacle?In case SA and OOA have different applicability ranges, how do we circumscribe — positively and negatively - these ranges? Any overlap?We appreciate that the organizing committee of this conference has selected this crucial topic.