Comments: With the development of advanced programming languages and
code
generating CASE tools,will programming in tradisional sense become a
lost
art?Why or why not?If not,when and where will tradisional programming
remain part of the SDLC?What are others saying about advancced
programming
languages and how they are being used

boxes are checked or whatever. Someone with traditional programming
skills will always be able to produce superior code to that which can
be generated by CASE tools, and often more simply and quickly.
Traditional programming allows for sharper focus on specific
requirements.


primarily to Pick databases. Please see :
http://groups.google.com.au/group/co...2672bb2fa95c6b

Regards
Mike.

wangwchuan wrote:

Are you writing an opinion piece or looking for answers to your
homework?


--
Kevin Powick

wangwchuan wrote:
I'll pipe up with one comment even without knowing whether you are
writing an article or for a college course, but please do let us know.

We asked questions like this in the early/mid 1980s when we were making
distinctions between upper CASE for analysis & design and lower CASE
for code generation, with few tools to even interface the two. Would
we eventually all be specifying applications from diagrams and
generating all code from that?

My opinion at that time was that coding wasn't going to go away, but
could become only one of the ways and perhaps not the most common way
to view your application. Until we are successfully working with
"round trip" tools where code, specifications (parameters to code
generation), and diagrams are various ways to view the same
application, coding will retain is current position. If we are forced
to always use the specs or diagrams for coding applications, the
industry (even if not all individuals) will stick with code.

I haven't done any in-depth study of the topic since that time, but
have kept current in the industry and have seen no reason to change my
opinion.

This was a broad stroke response. I won't go into any discussion about
on-the-fly source code generation from "parms" (such as xml documents)
or isolated areas where it is handy-enough to spec an aspect of a
system and keep the generated code hidden. Nor will I talk about "user
exits" and the wide range of IDE tools that use various forms of that.
But I do have opinions on all of these that pour into the opinion
rendered.

--dawn

dawn wrote:

I'd like to add that, while the discussion has been going since /before/
the 80s, the art and practice of computer programming has continued
since then to get /more/ complex and specialised and /less/ amenable to
automation.

Luke