Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!netcomsv!jls
From: jls@netcom.COM (Jim Showalter)
Newsgroups: comp.object
Subject: Re: C++ and waitresses (long)
Keywords: C++, software reuse
Message-ID: <1991May28.045845.25048@netcom.COM>
Date: 28 May 91 04:58:45 GMT
References: <2325@media03.UUCP> <1991May24.015856.9979@csusac.csus.edu> <31061@dime.cs.umass.edu> <1991May25.051758.9731@netcom.COM> <1991May28.024706.3135@tkou02.enet.dec.com>
Organization: Netcom - Online Communication Services  UNIX System {408 241-9760 guest}
Lines: 33

diamond@jit533.swstokyo.dec.com (Norman Diamond) writes:
]>In article <1991May25.051758.9731@netcom.COM> jls@netcom.COM (Jim Showalter) writes:
]>>>My experience so far suggests that a more accurate statement might be
]>>>"Many will successfully produce `.H' files.".
]>>
]>>Within reason, this is actually a promising development. Instead of
]>>the classic "I don't have time to design it--we're already behind
]>>schedule, so start TYPING [is THIS where the phrase "strong typing
]>>originated? ;-)]" approach, C++ does bring with it a more
]>>disciplined tendency to emphasize specification over implementation.

]>Yeah, this used to be called top-down specification, design, and development.
]>But now it is derisively referred to as "waterfall model."

If you read the rest of my post, I am not a big fan of the classical
waterfall model, since I regard it as completely unrealistic and doomed
to failure (I prefer to call it "top-down omniscient"). No theory can
be considered valid until checked by experiment: designs MUST be tested
by prototyping, and feedback must be accomodated.

My bias is toward a disciplined process of specification, prototyping,
refinement of specification, and iteration until a stable set of golden
specifications is arrived at.

The .h file disease is often due to the unwillingness of anybody to write
any actual code until the entire design is "done", despite the fact that
the design can't very well be done until it has been verified--and it can't
be verified until it has been prototyped.
-- 
**************** JIM SHOWALTER, jls@netcom.com, (408) 243-0630 ****************
*Proven solutions to software problems. Consulting and training on all aspects*
*of software development. Management/process/methodology. Architecture/design/*
*reuse. Quality/productivity. Risk reduction. EFFECTIVE OO usage. Ada/C++.    *