Strategy-driven reuse: Bringing reuse from the Engineering Department to the Executive Boardroom

  • Authors:
  • Wayne C. Lim

  • Affiliations:
  • Lombard Hill Group, 1535 Fairway Green Circle, San Jose, CA 95131, USA E-mail: Wayne_Lim@post.harvard.edu

  • Venue:
  • Annals of Software Engineering
  • Year:
  • 1998

Quantified Score

Hi-index 0.00

Visualization

Abstract

Organizations have predominantly utilized reuse in Engineering Departments for the purposes of reducing the cost and improving the quality of the software they develop. While these strategies have been successful, we believe that the full potential of reuse can only be tapped when reuse is brought to the Executive Boardroom as well. We propose that organizations tap reuse not only for cutting costs, but also for strategic and wide‐ranging business initiatives such as entering new markets, increasing agility in response to a dynamic marketplace, and competitive positioning and advantage. In order to do so effectively, organizations must harness the potential of reuse by migrating reuse into the company’s business and product‐line planning processes. We present a framework for analyzing and changing reuse business practices. Such practices include cost‐reduction reuse, when the organization utilizes reuse for cost savings purposes; reuse‐enabled business, when the organization uses reuse to create new business opportunities; and strategy‐driven reuse, when the organization incorporates reuse in the formulation of its business and product‐line strategy for the purposes of obtaining competitive positioning and advantage. To determine whether or not reuse is the proper software development strategy to pursue, we utilize concepts in competitive software engineering, an integrated approach to software development that is attuned to the competitive demands of the marketplace. First, a framework is established by identifying and analyzing the organization’s goals, strengths, and limitations, its market and its competitive environment. Based on these analyses, possible business or product strategies are formulated and one or more are chosen that help achieve the organization’s goals. Finally, a development strategy is chosen. Following this choice, each step of the decision cycle should be re‐evaluated to ensure that it is consistent with the chosen development strategy.