ASE2 CARD CATALOG ENTRY
As demonstrated in European, Japanese, and U.S. organizations, the ability to reuse significant portions of existing software assets offers significant potential for increasing engineering productivity, speed-to-market, and system quality and for decreasing the costs of building and maintaining large, software-intensive systems. However, instituting an effective reuse practice in software development poses substantial challenges to an organization. These challenges derive from a wide variety of technical, managerial, economic, social, and legal factors, which must be addressed if organizations are to succeed.
This guidebook assists your organization in meeting the "reuse challenge" through a well-defined approach for adoption and institutionalization of software reuse technology to improve productivity, quality, and competitiveness. This guidebook will help you:
Reuse adoption is envisioned as part of a continuous process improvement program; thus, the guidebook assists the end user in identifying both near- and long-term needs and actions. It provides guidance for developing a plan that will put the technology into practice, and it provides guidance on how to address critical institutional barriers, risks, and planning areas that must be addressed to make a reuse effort successful.
You need a process for reuse adoption to increase the effectiveness and the likelihood of success of your organization's effort to adopt reuse. You want to avoid the situation in which the adopting organization has only a vague notion of the current situation or what is to be accomplished. Without a well-developed understanding of how reuse relates to its current practice or how reuse will fit into the overall software development effort, the adoption effort is likely to fail.
You are probably aware of efforts to incorporate reuse that have had disappointing results or of organizations that are still avoiding reuse altogether. They are typically characterized by:
Based on a survey of 113 individuals from 29 companies, Frakes and Fox (1993) report that management and infrastructure support are critical for systematic reuse but that most organizations are providing inadequate support. The report also indicates that the factors impeding reuse are lack of time to practice reuse, lack of trust in externally developed software, and lack of computer-aided software engineering (CASE) and development process support for reuse.
This guidebook helps you avoid the situation and the problems described above by providing a well-defined, bounded series of steps, guidelines, and tools that you use to address the myriad issues critical to success: the Reuse Adoption process.
This guidebook consists of a Reuse Adoption process specification, supporting methods and guidelines, and examples of artifacts produced by the process. The organization of the guidebook is:
The Appendixes provide models, guidelines, examples, and background information that support application of the Reuse Adoption process. Included are:
2.0.5 1 June 94 Initial release to the PAL
Approved for public release; Distribution unlimited
This documentation is provided "AS IS" and without any expressed or implied warranties whatsoever. No warranties as to performance, merchantability, or fitness for a particular purpose exist. The user must assume the entire risk and liability of using this document. In no event shall any person or organization of people be held responsible for any direct, indirect, consequential or inconsequential damages or lost profits.
Powered by the Generic Web-Based Reuse Library (GWRL)