Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!ames!uhccux!munnari.oz.au!ditmela!latcs1!jacob
From: jacob@latcs1.oz.au (Jacob L. Cybulski)
Newsgroups: comp.software-eng
Subject: Re: CASE - The Emperor has no clothes on!
Message-ID: <8138@latcs1.oz.au>
Date: 15 Jun 90 01:20:08 GMT
References: <1990Jun13.101122.15604@axion.bt.co.uk>
Organization: Comp Sci, La Trobe Uni, Australia
Lines: 47

I think most of the participants of this discussion forget one thing, that
Programming Environments, CASE Tools, Methodology Drivers and CASE
Environments should not be confused with each other (I think the distinction
was made by McClure). The programming environments usually integrate a number
of programming language oriented utilities, e.g. syntax oriented editors,
debuggers, steppers and tracers, etc., into a uniform framework (e.g.
Interlisp OR THINK C), CASE Tools usually target the individual programming
tasks thus improving overall programming productivity (e.g. ER-DESIGNER),
Methodology Drivers integrate the SE Tools to follow a particular
methodology (e.g. IEF, HOS, Excelerator, VAW, etc.), and then you have CASE
Environments which can be customised to follow any (or a few) methodologies
(e.g. VSF, POSE, etc.).

The systems that people so eagerly criticise happen to be SA/SD Methodology
Drivers and incorporate a number of CASE Tools supporting the techniques
accepted as a part of that methodology. I cannot see any reasons to knock
down a particular software development methodology just because a new
programming flavor appears on the market (e.g. OOP). Hundreds of companies
adopted SA/SD and invested hundreds of thousands to introduce standards and
train their staff, if an appropriate CASE tool, environment or driver
reduces their costs, we should prize the tool designers and the management
decision to adopt it. If you are an OOP fan, which means it is unlikely
you'd use COBOL as your programming vehicle, then perhaps you should use the
tools which support your activities (e.g. StP for Ada and C++).

However, a true Software Engineer must look at software development as a
process involving not only programmers (and their likes and dislikes for a
particular method or language), but also the clients, organisational needs,
costs and benefits, project structure and programming team, requirement
specification, design, implementation, testing and finally maintenance. Your
favorite CASE environment (e.g. OOP) may not provide an extensive support for
ALL elements of software development lifecycle, would you then consider
changing your mind and adopting the tool which reduces your costs overall, or
would you develop your own and committ your employer to millions (CASE
development costs goes into hundreds of man-years). I would.

Jacob L. Cybulski

Amdahl Australian Intelligent Tools Program
Department of Computer Science
La Trobe University
Budoora, Vic 3083

Phone: +613 479 1270
Fax:   +613 470 4915
Telex: AA 33143
EMail: jacob@latcs1.oz