This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Organizational Factors and Reuse
September/October 1994 (vol. 11 no. 5)
pp. 31-41

Reuse is not just a technical issue. Hewlett-Packard studied why people sometimes resist reuse and which organizational models appear to encourage reuse more than others. The study found that successful reuse programs must be integrated within the culture of a company's existing organizational structure. One crucial organizational factor is the relationship between producers and consumers of reuse components and services. What are these relationships and how well do they work? To answer this question, I conducted an empirical study of 10 engineering sites at Hewlett-Packard engaged in systematic reuse. From this reuse experience, I identified four models of producer-consumer relationships; evaluated the models in terms of their organizational structures, advantages, and disadvantages; and identified goals for management to enable a successful implementation. The four models are: lone producer, nested producer, pool producer and team producer. Two or more models may occur within a given reuse program. Recommendations to management are based on both current successful practices and interviewees' suggestions. I also include some tentative guidelines on which environments are best suited to each model.

Index Terms:
software reusability; DP management; social aspects of automation; Hewlett-Packard; systematic reuse; organizational structures; management; lone producer; nested producer; pool producer; team producer
Citation:
Danielle Fafchamps, "Organizational Factors and Reuse," IEEE Software, vol. 11, no. 5, pp. 31-41, Sept.-Oct. 1994, doi:10.1109/52.311049
Usage of this product signifies your acceptance of the Terms of Use.
 
You do not have the roles required to access this portlet.