🚀 go-pugleaf

I would like to add to this discussion the possibility of reusing
higher level software *design* components.  There is an interesting
article which I described recently in comp.software-eng.  I
will repost here since it seems to fit the discussion:

****repost****ignore if you read this in comp.software-eng*************

The article, by Veikko Seppanen, describes an ambitious system which
attempts to provide *design* tools and a *design* repository for
software.  The idea is to facilitate reuse of design decision knowledge.
This paper actually addresses a number of points brought up in this
group recently, such as:

1) What level reuse should take place at.

2) How should design alternatives and decisions be documented.

3) How can a user be given access to this selection process and
   be assisted in reuse of previous designs.  

Naturally, there a quite a few unsolved problems (research, after all)
but the ideas are very interesting, particularly in light of the 
discussion in this group over the last month.

******** Abstract ******************
 
Seppanen, Veikko, "Acquisition, organisation and reuse of software
     of software  design knowledge," Software Engineering Jour-
     nal, vol. 7, no. 4, pp. 238-246, IEE/BCS, London, July,
     1992.
 
     The paper addresses the acquisition, organisation and reuse
     of knowledge in the design of real-time software systems.
     Experiences from capturing and making explicit software
     design alternatives and their selection criteria are
     evaluated.  Generic, software design task-specific and
     domain specific types of knowledge are discussed and illus-
     trated using real-life design examples.  A prototype of a
     CASE tool is also described, which incorporates a repository
     of reusable software components as a source of design alter-
     natives and assists a designer both in selecting them and in
     analysing the results.
 
********* Bib ***********************

%A Veikko Seppanen
%T Acquisition, organisation and reuse of software of software 
design knowledge
%J Software Engineering Journal
%V 7
%N 4
%P 238-246
%I IEE/BCS
%C London
%D July, 1992
%K software, engineering, software design, reuse
%X The paper addresses the acquisition, organisation and reuse of 
knowledge in the design of real-time software systems.  
Experiences from capturing and making explicit software design 
alternatives and their selection criteria are evaluated.  Generic,
software design task-specific and domain specific types of 
knowledge are discussed and illustrated using real-life design
examples.  A prototype of a CASE tool is also described, which 
incorporates a repository of reusable software components as a source of
design alternatives and assists a designer both in selecting them 
and in analysing the results.

**************************************

-- 
  Hugh LaMaster, M/S 233-9,     UUCP:      ames!lamaster
  NASA Ames Research Center     Internet:  lamaster@ames.arc.nasa.gov
  Moffett Field, CA 94035-1000  Or:        lamaster@george.arc.nasa.gov 
  Phone:  415/604-1056                     #include <usenet/std_disclaimer.h>