home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.software-eng:2945 comp.object:2990
- Newsgroups: comp.software-eng,comp.object
- Path: sparky!uunet!munnari.oz.au!uniwa!DIALix!dent
- From: dent@DIALix.oz.au (Andrew Dent)
- Subject: Re: Software costs revisited?
- Organization: DIALix Services, Perth, Western Australia
- Date: Fri, 24 Jul 92 12:00:47 GMT
- Message-ID: <1992Jul24.120047.7217@DIALix.oz.au>
- References: <1992Jul20.120345.26472@cs.tu-berlin.de> <22493@hacgate.SCG.HAC.COM> <36065@sdcc12.ucsd.edu>
- Lines: 23
-
- In comp.object, wgg@cs.ucsd.edu (William Griswold) writes:
- >For maintenance, one desirable characteristic of a system is locality of
- >change. If an enhancement or repair can be implemented within one or two
- >modules/classes (and it is not necessary to check every module in the system
- >for consistency), then the design has succeeded in making the life of
- >maintainers easier, and improves the chances of a reliable product.
-
- After nearly two years of (on and off) work on a magazine publishing system,
- I'm a solid believer in OO for reducing maintenance hassles. Not only is the
- locality of change a major benefit but it is easier to completely reimplement
- behaviours because of greater conceptual modularity backed up by poly-
- morphism (ie: you can subclass to reimplement a behaviour - something that
- is invariably messy to try to do in a functional oriented system).
-
- After writing a FORTRAN->Pascal converter, another major OO benefit seen is
- ease of incremental development - adding similar objects with slightly different
- behaviour, instead of constantly revising central functions.
-
- Andy Dent (A.D. Software - Mac & VAX programming)
- 94 Bermuda Dve, BALLAJURA Western Australia 6066
- Phone/Fax: 09 249 2719 (local) +619 249 2719 (International)
- Internet: dent@DIALix.oz.au Compuserve: 100033,3241
-
-