Newsgroups: comp.software-eng
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!dynsim1!litwin!jto
From: jto@litwin.com (John O'Beck)
Subject: Re: Modifiability
Message-ID: <1991Jun6.161604.4802@litwin.com>
Organization: Litwin Process Automation
References: <2192@Terra.cc.brunel.ac.uk>
Distribution: comp.software-eng
Date: Thu, 6 Jun 1991 16:16:04 GMT
Lines: 21

se90wak@cc.brunel.ac.uk (Wael A Khalil) writes:


>	- Adopting a software development method and making sure that the
>	documentation is up to date will insure that the software will
>	be highly modifiable.
>	- Software engineering method is not enough, there is more to it.

Most maintenance issues go straight back to module coupling and cohesion.  
If you are designing you system using cohesive modules  that are strictly 
data coupled; you tend to maximize the amount of reusable code and minimize 
module interactions.  This makes for highly modifiable and maintainable code.
Proper implementation of a reasonable software engineering methodology will 
help you do this.

Of course no methodology can do much for you if it is not implemented 
properly.  Nothing will ever substitute for good engineering.  Any 
methodology is nothing but a miter box.  It is up to you to learn how
to cut the joints and build the cabinet.