Software reuse standards

Abstract

m To explore the impact of current software standards on software reuse, we describe the analysis, findings, and recommendations of the IEEE Software Engineering Standards Committee (SESC) Reuse Planning Group. The object of the Reuse Planning Group was to define, for the SESC, a statement of direction for IEEE standards related to the analysis, design, implementation, validation, verification, documentation, and maintenance of reusable software assets as well as supporting infrastructure in the creation of new applications. We also examine the current state of software reuse standards by the following: (1) an analysis of the needs of various users of standards and a classification of the needs with respect to the type of reuse standards that might be written; (2) a set of normative documents on the subject of software reuse, identified and evaluated for the role they might play in the standardization process; (3) a program element view of the IEEE Software Engineering Standards Committee collection, into which reuse standards must fit; and (4) recommendations for standardization projects. nsertion of any new innovation by an organization requires adoption, utilization, and management of the new technology. The motive for an organization to adopt a new technology is based on expectations for achieving a set of goals. The insertion of software reuse technologies is no different from other innovations, in that they must be adopted, utilized, and managed in software product development or maintenance lifecycles. The following goals are usually stated for software reuse: (1) the organization expects product development or maintenance efforts to decrease; (2) the organization expects an increase in product quality; and (3) the organization expects a decrease in product time-to-market. Although the benefits of software reuse have been discussed in the literature for several decades, it remains an elusive goal. Successful insertion of new technology depends on both technical and nontechnical factors. It is important that both be adequately addressed. Clearly, software standards are an important technical issue, and while explicit software reuse standards do not exist, a number of current de facto and official government standards are making an impact. To explore the impact of current software standards on software reuse, we describe the analysis, findings, and recommendations of the IEEE Software Engineering Standards Committee (SESC) Reuse Planning Group. The goal of the Group was to define, for the SESC, a statement of direction for IEEE standards on the analysis, design, implementation, validation, verification, documentation, and maintenance of reusable software assets, as well as their supporting infrastructure in the creation of new applications. We examine the current state of software reuse standards by addressing the following topics: (1) the needs of various users of standards and a classification of those needs with respect to kinds of reuse standards; (2) normative documents on software reuse, identified and evaluated for their roles in standardization; (3) a “Program Element” view of the IEEE Software Engineering Standards Committee collection, into which reuse standards must fit; and (4) recommendations for standardization projects. I ✮ F E A T U R E A R T I C L E