A specific repository, called Design/1, is the principle tool to facilitate reuse within typical AC engagements. Though very effective at managing the work objects of an engagement, it is less then ideal for facilitating reuse. First, the repository is really a design repository organized around the design and its architecture. If one does not know the design and architecture of Customer/1 it is very difficult to find things. Second, the repository does not support versioning. Alternative versions are only supported via user imposed naming conventions. Third, traceability links are quite limited. Improvement to each of the above features would allow people not familiar with Customer/1 to browse it and become more familiar with it, thus lowering the learning curve associated with using the Customer/1 repository.
A more general problem is the lack of any support for capturing organizational memory. That is, there is a very high dependence on knowledge held by key individuals. When new people need assistance they go directly to these knowledgeable people. Alternatives need to be created. These alternatives should include better process guidance, improved training on the assets, and improved tools. In the tool category, some sort of machine mediated interaction should be used. This would facilitate current communication needs while also capturing these questions and their answers for others to draw upon. Such a tool should also support organizing and indexing into this knowledge-base.