home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.software-eng
- Path: sparky!uunet!spool.mu.edu!umn.edu!The-Star.honeywell.com!saifr00.cfsat.honeywell.com!shanks
- From: shanks@saifr00.cfsat.honeywell.com (Mark Shanks)
- Subject: Re: When do we inspect
- Message-ID: <1992Dec21.215642.5706@saifr00.cfsat.honeywell.com>
- Organization: Honeywell Air Transport Systems Division
- References: <BzJK8L.6r0@NeoSoft.com> <1992Dec21.184224.21056@den.mmc.com>
- Date: Mon, 21 Dec 92 21:56:42 GMT
- Lines: 51
-
- In article <1992Dec21.184224.21056@den.mmc.com> jhull@vulcan-gw.den.mmc.com writes:
-
- >In article 6r0@NeoSoft.com,
- >claird@NeoSoft.com (Cameron Laird) writes:
- >cl> I assert: source code should go into the CM system
- >cl> from its first day. ... Some object
- >cl> that checking in source is too much overhead; for
- >cl> me, that's only a symptom that the check-in process
- >cl> isn't yet adequate. Coders should *want* the benefits
- >cl> of even the most rudimentary CM: automated regression
- >cl> testing, static semantic analysis, validation of
- >cl> porting considerations, ...
- >
- >Au contraire. Since we are not yet, and may never be, at a
- >point where we all think alike and work alike, I suggest that
- >each programmer should be allowed to do his or her own work
- >in whatever manner allows them to be most productive. If
- >that involves some form of CM, fine. But if not, so what.
- >
- >I suggest that a unit of code should enter a "Software
- >Development Library" at the time when the individual team
- >member has finished coding and unit testing it
-
- >I further suggest that there should be a "Project Software
- >Library" controlled and managed by a Software Quality
- >Assurance group/team/organization, and that Unit A must be
- >entered in the PSL prior to being released for use by Team
- >B.
-
- I believe Cameron misunderstood me, or perhaps has a different
- working model for "CM" than I do. I was referring to a simple
- "vault" type of tool; no regression testing, no semantic analyses,
- no nothing but a freeze on the code and enforced procedures to
- check it out and make changes.
-
- I guess Jeff's description of a "SW Development Library" is
- less restrictive than a typical CM system. I can understand
- a customer's desire for tracking changes, but IMHO, taking a
- "snapshot" at CDR time accomplishes that function without
- incurring the truly prodigious overhead entailed by some
- CM systems (check out package, make changes, inspect, fill
- out software change request (SCR) form, meet with configuration
- control board, edit SCR, check package back in, get change from
- customer, goto line 1). I'm on a program using Ada, heading a
- team of 10 software designers producing well over 200 Ada
- packages and close to 20,000 LOC. Multiply that by 30 or 40
- such teams and see how much time will be spent on CM alone.
- Why start that process any sooner than necessary?
-
- Mark Shanks
- shanks@saifr00.cfsat.honeywell.com
-