Software reuse: Customer vs. contractor point-counterpoint

Abstract

Software reuse promises significant benefits to the software engineering profession, and is therefore an avowed goal of both organizations that contract for software (“customers”) and those that develop it (“contractors”). Customer and contractor organizations are actively pursuing reuse programs, researching the technology and establishing libraries of reusable assets.

There are many technical challenges in achieving software reuse, but there are perhaps even more nontechnical challenges. Software reuse will require fundamental changes in business and contractual practices, organizational procedures, and the day-to-day activities of software engineers. Organizations naturally resist change; overcoming this resistance is a major consideration in moving toward an increased practice of reuse.

Many of the nontechnical issues related to reuse deal with the customer/contractor relationship. Reuse raises issues about financial incentives, software ownership, responsibility and liability, etc. that must be addressed in software development contracts. It also requires modifications to the software development process that must be recognized in program management procedures. A successful reuse program cannot be established without customer/contractor cooperation.

Unfortunately, such cooperation can be difficult to achieve. The customer and contractor necessarily have different perspectives and concerns in software contracting, and the contractual and program management processes are the formal mechanisms for managing these differences. There is a tendency for each “side” to view the other as an adversary, or an impediment in achieving its own goals. In particular, this conflict in viewpoints can appear when considering software reuse. Contractors believe the customer does not understand their concerns about reuse costs, risks, and liabilities; customers believe contractors do not support their goal of reducing software costs through reuse.

In fact, customers and contractors share the goal of reducing software cost and improving quality through reuse. Their differing perspectives, however, can obscure this basic agreement. To understand, and eventually to resolve, these differences, it is important that each side understand and appreciate the other's perspective. This paper seeks to further this understanding by examining some of these differences in perspective and suggesting common ground.