Abstract
Reuse of software knowledge is a principle for improving productivity and reliability of software development. To achieve this, reuse must be done systematically. This means that processes for retrieving, reusing, revising, and retaining have to be defined. At the same time organizational issues (such as the establishment of a separate organizational unit responsible for organizational learning) must be considered. In this paper we compare software knowledge reusemodels to the CBR cycle of Aamodt and Plaza [AP94a] and show that the approaches are very similar. We suggest to extend the CBR cycle by including organizational issues explicitly and present an organizational "implementation" of CBR. We conclude that CBR is a promising technology for realizing software knowledge reuse if our suggested organizational extensions are considered.