Newsgroups: comp.ai
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!nntp.sei.cmu.edu!fs7.ece.cmu.edu!hudson.lm.com!news.pop.psu.edu!news.cac.psu.edu!howland.reston.ans.net!pipex!dsbc.icl.co.uk!pml
From: pml@oasis.icl.co.uk (Patricia Lynch)
Subject: Re: component-based software reuse and software?
Message-ID: <D6GAKw.21y@dsbc.icl.co.uk>
Sender: news@dsbc.icl.co.uk (Usenet)
Nntp-Posting-Host: vpm.bra01.icl.co.uk
Organization: ICL, Bracknell, UK.
X-Newsreader: Tin 1.1 PL5
References: <jin.796844917@alice>
Date: Mon, 3 Apr 1995 08:36:30 GMT
Lines: 19

"Component-based software reuse" - build your software in little bits,
each of which has a definite and limited task. This makes it easier
to re-use them entire, rather than cutting the code around for the
next job. Strongly related to Object-oriented design techniques,
especially the idea of encapsulation, since you can then pick the 
composite object up and re-use it entire, without examining how it
works inside. Beware inefficiency though - can result in very large 
code as you pull in objects which can do a lot more than you need.

"Component-based architecture" - like building a house from a collection of 
pre-designed rooms rather than designing the whole house from scratch.
Obviously need to define the externally important characteristics of 
each room very carefully.

I've attempted this answer to test my own understanding of these concepts:
other views or amendments very welcome.

Tricia.

