🚀 go-pugleaf

In article <14346@duke.cs.duke.edu> crm@romeo.cs.duke.edu (Charlie Martin) writes:
>
>I've heard it said that the best predictor of eventual success in 
>building a large system is domain knowledge on the part of the designer,
>i.e. tax preparation software is best designed by someone who knows 
>tax preapration well rather than someone who knows, say, human-interface
>design well.
>
>I'd like to see if I can find any good studies on it.  Does anyone 
>know of a reference?
The IEEE Tutorial "Software Reusability" by Peter Freeman is a good place
to start.  Plenty of work compiled on this issue.  In fact, a whole new
news group, comp.sw.components is being established to discuss software
components.  The domain analysis and engineering problem you are refering
to was first outlined by James Milne Neighbors in his thesis "Software
Construction Using Components" UC Irvine Tech Rpt. TR160, 1980.

The full reference for the IEEE pub is:

"Software Reuseability" by Peter Freeman, IEEE Computer Society Order
No. 750, IEEE Catalog No. EH0256-8, ISBN 0-8186-0750-5 IEEE Computer Society
Press.

>Thanks,
Your welcome.
>
>Charlie Martin (crm@cs.duke.edu,mcnc!duke!crm) 

-- 
Richard M. Stein (aka Rick 'Transputer' Stein)
Office of Research Computing @ The Ohio Supercomputer Center
Ghettoblaster vacuum cleaner architect and Trollius semi-guru
Internet: stein@pixelpump.osc.edu