Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!deccrl!news.crl.dec.com!pa.dec.com!rust.zso.dec.com!shlump.nac.dec.com!smaug.enet.dec.com!abbasi
From: abbasi@smaug.enet.dec.com (Nasser ABBASI)
Newsgroups: comp.lang.fortran
Subject: Re: Fortran and Object Oriented Programming
Message-ID: <18561@shlump.nac.dec.com>
Date: 31 Dec 90 04:03:31 GMT
Sender: newsdaemon@shlump.nac.dec.com
Organization: Digital Equipment Corporation
Lines: 19


 There one angle to this debate which was not looked at yet, which is
 ease of maintinance of the software.
 lets look at an example:
 given one fairly complex problem, ask 2 programmers, equal in coding skills,
 one to write the software in OO approach, and the other in traditional
 approach .
 Now the question is, which final program will be easier to maintain by
 a third person? assume the third person has equal abilities is OO and
 non OO methodologies.. in which case will the third person grasb the
 way the program works and be able to fix bugs in it faster.. (assume equal
 amount of documentations in both cases).
 since cost of software maintinance is much larger in most cases that the
 cost of the initial release, the maintinance issue should be considered
 in comapring these two methods.

Nasser ABBASI	abbasi@smaug.enet.dec.com
		--or-- ...!decwrl!smaug.enet.dec.com!abbasi
		--or-- abbasi%smaug.dec@decwrl.dec.com