I have yet to encounter a business application problem that does not lend itself to that approach. A librarian must be designated to oversee the administrative aspects of the repository. Larger, more formal organizations may also choose to establish a review process for contributions. The repository must be indexed and the components documented, so that the effort required to locate, understand, and incorporate a component is less than the effort required to develop a comparable one from scratch. The indexing scheme need not be elaborate and does not require a hierarchical classification.
Experience shows that a simple permuted keyword index of descriptive titles is adequate.
The organization's programming standards must call for the use of certain components in certain common situations. Those components may come either from the organization's own repository or from vendors' libraries. Quality assurance or walkthrough reviews of new application systems should note and question missed opportunities to make use of existing components, to contribute a new component. Quasi measures of productivity based on quantity of new code written and tested must be eliminated. Let's reward our programmers when they solve a problem without writing custom code.