By Paul G Basset.
In Software Development, January 1998
In this article he discusses imortantant things to remember in order to= successfully implement reuse in your organization
I order to gear your organization for reuse you need to:
=B7 change the infrastructure of the organization
=B7 culture of its people
First he defines five levels of reuse, starting from least to most, = measuered in the percentage of reused lines in the total lines of= code:
1. ad hoc - copy and modify source modules - 0 to 40% reuse
2. latentent - don't write their own reusable - 40 to 80%
3. project - reuse within projects, not sustained - 80 to 90%
4. systemic - within multiple project areas, defined reuse= process, teaching attitude - 90 to 95%
5. cultural - measure return of reuse, 95 -99%
Five subtypes of barriers get to a higher level of reuse :
1. conceptual
2. technological
3. managerial
4. infrastructural
5. cutural
You need a clear vision for why you want reuse in your= organization, Four visions that might be reashed by reuse:
1. reduction in time to market
2. strategic enabler for future projects
3. reduce system size and cost
4. reengineer business
You need a business case, where you define where your organization are= and how to reach this vision, where you address in particular:
1. limits of corporate behavior?
2. milestones of projects?
3. How you will be reallocating resources?
4. When you expect return on investment?
5. What risks you are ready to take?
You need a rollout plan where you more detailed address the subjects in= the business case, and how exactly to implement this. In particular you= should remember to:
1. Include senior executives
=B7 Set policies
=B7 Monitor process
=B7 Remove barriers
2. Educate staff and managers
3. Medium size projects, high reuse potential
4. 1 competent per 4 novices
5. Create Frame engineers
6. Frame engineering department
7. Measure and reward
It has been done in other organizations, most of them are characterized= by having :