This article outlines an approach that avoids these problems by choosing a retrieval method that utilizes minimal repository structure to effectively support the process of finding software components. The approach is demonstrated through a pair of proof-ofconcept prototypes: PEEL, a tool to semiautomatically identify reusable components, and CodeFinder, a retrieval system that compensates for the lack of explicit knowledge structures through a spreading activation retrieval process. CodeFinder also allows component representations to be modified while users are searching for information. This mechanism adapts to the changing nature of the information in the repository and incrementally improves the repository while people use it. The combination of these techniques holds potential for designing software repositories that minimize up-front costs, effectively support the search process, and evolve with an organization's changing needs.

Repositories must be designed to meet the evolving and dynamic needs of software development organizations. Current software repository methods rely heavily on classification, which exacerbates acquisition and evolution problems by requiring costly classification and domain analysis efforts before a repository can be used effectively. This paper outlines an approach in which minimal initial structure is used to effectively find relevant software components while methods are employed to incrementally improve repository structures. The approach is demonstrated through PEEL, a tool to semi-automatically identify reusable components, and CodeFinder, a retrieval system that compensates for the lack of explicit knowledge structures through spreading activation retrieval and allows component representations to be incrementally improved while users are searching for information. The combination of these techniques yields a flexible software repository that minimizes up-front costs and improves...

The main aim of this paper is to present a systemic framework of what the field of Information Systems (IS) is about; its connecting areas and its central theme. It was born out of a search for structure in providing a cohesive picture of the subject and field of IS for students and business managers. The average manager and executive has difficulty in obtaining an integrated and holistic view of information systems, and it is said that this leads to a lack of alignment between IS and the strategic aims of the enterprise. Students, particularly MBA students, have a similar problem. Using a large number of disparate data sources, including a delphic survey of leading academics, the paper adopted a grounded theory approach in developing an integrating framework of five main areas for the field: (1) IS Development,