Path: utzoo!attcan!uunet!cs.utexas.edu!uwm.edu!ogicse!plains!kmagel
From: kmagel@plains.UUCP (ken magel)
Newsgroups: comp.software-eng
Subject: CASE for OOS
Message-ID: <5012@plains.UUCP>
Date: 13 Jun 90 16:50:25 GMT
Reply-To: kmagel@plains.UUCP (ken magel)
Organization: North Dakota State University, Fargo
Lines: 19


    AN earlier article mentioned the inadequacies of present CASE tools for 
handling object-oriented systems.  Several other correspondents have supported this view and argued that the needed new CASE tools to support object oriented
systems clearly will be very different from present tools.  They argue that
structure charts, data flow diagrams, etc. will not have much use in object
oriented development methodologies.
    I think these arguements are not correct.  The CASE tools needed to support
object oriented systems and development methodologies will be only modestly 
different from those needed to support structured analysis and design.  Many
of the diagrams such as entity-relationship, data flow, and so on will need 
only minor modifications to be extremely useful in designing, implementing and
understanding object oriented systems.  The minor modifications will be needed,
but they should be doable well within the framework of existing CASE tools.
      Some correspondents are arguing that object orientation will cause a 
paradigm shift, a revolution in software development.  I think object 
orientation is merely an evolutionary step along the path of improved
software manipulation.  It is not a radical change althoug it is a significant
change.  The notion of fifty year revolutions overthrowing the old order 
seems to overstate the real situation.