Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!hubcap!billwolf%hazel.cs.clemson.edu
From: billwolf%hazel.cs.clemson.edu@hubcap.clemson.edu (William Thomas Wolfe,2847,)
Newsgroups: comp.sw.components
Subject: Re: What kinds of keys do you sort?
Message-ID: <5443@hubcap.clemson.edu>
Date: 10 May 89 17:53:16 GMT
References: <32269@sgi.SGI.COM>
Sender: news@hubcap.clemson.edu
Reply-To: billwolf%hazel.cs.clemson.edu@hubcap.clemson.edu
Lines: 18

From article <32269@sgi.SGI.COM>, by thant@horus.SGI.COM (Thant Tessman):
> What exactly would an "intelligent software librarian" do?  I have seen 
> software development environments that do "HyperCard" type things to link 
> libraries to manuals to the code that refrences those libraries, etc.  The 
> stuff was very neat, but only if the developers explicitly maintained all the 
> interconnections.

     In any library there is generally a librarian.  To provide human
     librarians for each component library user would be quite expensive.
     Therefore, the "intelligent software librarian" software is constructed.
     The human librarian encodes domain knowledge and component selection 
     heuristics into the system, and the users are then guided automatically
     by the automated librarian.  Thus, a small number of human knowledge
     engineers (the human librarian(s)) can serve a very large number of  
     library users.  


     Bill Wolfe, wtwolfe@hubcap.clemson.edu