>Your showing your Dinasaur -- I mean age! Someone
>once told me that every new generation of PhDs
>reinvents the wheel with a new nomenclature in
>order to justify there presence. I have come to
>believe it. The design philosophy has really not
>changed but the technology has. So in order to
>look good new words are created for philosophy to
>keep pace with the new technology.

Tom,
i think you are wrong on this -
OOP and OOP-RAD are different approaches and concepts
form the stractural/procedural programing most of us
were used to
usinf OOP requires different anylisys and design
OOAD and OOAD in a RAD contex are done differently than the
regular waterfall scheme
a good reading for these are 2 cutter information
group publications Application Development strategies (edited by Ed Yourdon) and Object Oriented Strategies(edited by Paul harmon)
also a nice intruductory to OOAD methodologies (ref. to books and general guidelines of each methodology) was in an article by Michel Gora in the June issue of DBMS

OOAD&P is not just about building nice MMI's or programing in
a OO lang. (ie VFP) it is about using encapsulation, inheritance and polymorphism - and using the correctly
defining the relations between objects defining the way the object interact
this combined with RAD tools (e.g the form designer) that allow fast prototyping of GUI's
make for greater productivity, ease of maintance and reusability

i think i'll step off the soap box now <s>

Arnon