kcby@fenix.Atlanta.NCR.COM (kcby) (03/09/88)
We are involved in doing our first "major" development using an
object-oriented approach. I am wondering if anyone has any experience or
statistics which show what the effect of using an OO approach is on program
or product quality.
My "gut feeling" is that quality ought to be (at least slightly) improved
over the quality of a product developed using a "standard" sturctured
approach (assuming same quality designers, sufficient time applied to
project, etc) due to
a) inheritance promoting the reuse of tested code
b) data encapsulation promoting modularity which reduces
the "ripple effect" of fixing bugs and making changes
However, some nice hard statistics would be useful. "Gut feelings" or rough
estimates from someone who's had experience actually developing an OO
product (particularly in C++) would also be encouraging.
Also, does anyone know of other quality related issues concerning the use
of an OO design or C++ programming language? What I am thinking of here
might be things like "the use of OO approach forced more thought to go into
the design to a more detailed level than usally done at an early stage of
development" or "we found problems with...".
K.C. Burgess Yakemovic "Say I'm a philosopher, say I'm a seeker for truth,
kcby@Atlanta.NCR.com say I'm a lover of my kind, or best of all,
....ncrlnk!fenix!kcby say I'm a Student" ...... Henry James, Sr.
--
K.C. Burgess Yakemovic "Say I'm a philosopher, say I'm a seeker for truth,
kcby@Atlanta.NCR.com say I'm a lover of my kind, or best of all,
say I'm a Student" ...... Henry James, Sr.
<< these are my opinions ... NCR doesn't *have* opinions! >>