Aligning the economic modeling of software reuse with reuse practices (original) (raw)

International Journal of Applied Information Systems, 2012

In today's saturated process and product market where time, money and productivity is very crucial, software reuse is considered to be one of the most promising approaches for increasing productivity . A good software reuse process facilitates the increase of productivity, quality, and reliability, and the decrease of costs and implementation time. By reusing existing software, in addition not having to reimplement it, one can avoid downstream costs of maintaining additional code, and if the re-used artifacts has been thoroughly tested and increase the overall quality of the software product. Several industrial and governmental initiatives are underway to increase the reuse of software, involving both adjustments to process, and the adoption of new technologies. Reusability is not always fruitful because some time reusability requires more effort than building new so careful study should be carried out when to reuse and when to build. In this paper effort are made to clear financial evidence of the benefits of reuse. This paper involves an exhaustive study on comparison of economic models of software reusability, their benefits and drawbacks.

An evaluation model for software reuse processes

2011

Software reuse is a major concern in many software development companies. It is one of the main strategies used to reduce the cost of software product development. Studies show that the reuse strategy is the most significant strategy in terms of effort and quality. That it could save the half of the software development effort and increase the quality of the software product. Different ways of software reuse are proposed and discussed. In this study, an evaluation model for software reuse is proposed. The model is developed in order to consider the new methods of software reuse. That developed based on the framework of develop a reusable software components through software development processes. The model is proposed in order to present the applicable methods of software reuse and to evaluate their cost.

The Economics of Software Reuse (Panel)

Conference on Object-Oriented Programming Systems, Languages, and Applications, 1991

We discuss several models of a "software components" industry and issues concerning effective reuse and object-oriented programming, and speculate on how (and whether) a vigorous components market will arise. A "software industrial revolution" requires an infrastructure, a "reuse mindset", and the treatment of software as an asset.

Evaluating software reuse alternatives: a model and its application to an industrial case study

2004

Abstract We propose a model that enables software developers to systematically evaluate and compare all possible alternative reuse scenarios. The model supports the clear identification of the basic operations involved and associates a cost component with each basic operation in a focused and precise way. The model is a practical tool that assists developers to weigh and evaluate different reuse scenarios, based on accumulated organizational data, and then to decide which option to select in a given situation.

The economics of software reuse

ACM SIGPLAN Notices, 1991

Investments in reusable software. A study of software reuse investment success factors

This research supports the thesis that there is a set of success factors which are common across organizations and have some predictability relationships to software reuse. For completeness, this research also investigated to see if software reuse had a predictive relationship to productivity and quality. The individual success factors were grouped into the following categories: management commitment, investment strategy, business strategy, technology transfer, organizational structure, process maturity, product-line approach, software architecture, availability of components, and quality of components. A questionnaire was developed to measure software reuse capability, productivity, quality, and the set of software reuse success factors. A survey was conducted to determine the state-of-the practice. The data from the survey was statistically analyzed to evaluate the relationships among reuse capability, productivity, quality, and the individual software reuse success factors. The results of the analysis showed some of the success factors to have a predictive relationship to software reuse capability. Software reuse capability also had a predictive relationship to productivity and quality. Based on the research results, the leading indicators of software reuse capability are: product-line approach, architecture which standardizes interfaces and data formats, common software architecture across the product-line, design for manufacturing approach, domain engineering, management which understands reuse issues, software reuse advocate(s) in senior management, state-of-the-art tools and methods, precedence of reusing high level software artifacts such as requirements and design versus just code reuse, and trace end-user requirements to the components which support them.

Value based software reuse investment

Annals of Software Engineering, 1998

A number of issues are covered in this paper. Chief among them is the need for greater discipline in understanding the economic benefits of software reuse within the context of a broader business strategy. While traditional methods fail to account for growth opportunities and flexibility generated by investments in reuse, the introduction of option pricing theory can greatly enhance the

An Evaluation Model for Software Reuse Processes Software Engineering and Computer Systems

2011

Toward an engineering discipline of software reuse

IEEE Software, 1999

is software reuse an issue and not, for example, hardware reuse? A question as broad as this can elicit a wide range of responses. Perhaps the common denominator of all possible answers is that software assets are typically very information-rich; hence, it is difficult to characterize them, match them, and capture their relevant properties. ♦ How is software reuse different from software design? Good software design advocates designing software from reusable assets and producing software systems with the perspective that they might be reused. Software reuse deals with producing reusable assets (domain engineering) and exploiting reusable assets (application engineering), so as to make good software design a routine practice. Also, because there are quantifiable costs associated with the integration of reuse concerns, these costs have to be weighed against reuse benefits. Software reuse deals with the trade-offs involved in such cost-benefit decisions. These decisions influence both the design process and the quality of the produced software design. This article presents some of the research issues that we feel are relevant today. The list is neither exhaustive nor perfectly orthogonal, and necessarily reflects our biases. We discuss, in turn, technical aspects and then managerial aspects that we feel are worthy of research attention.

Software reuse: metrics and models

ACM Computing Surveys, 1996

As organizations implement systematic software reuse programs to improve productivity and quality, they must be able to measure their progress and identify the most effective reuse strategies. This is done with reuse metrics and models. In this article we survey metrics and models of software reuse and reusability, and provide a classification structure that will help users select them. Six types of metrics and models are reviewed: cost-benefit models, maturity assessment models, amount of reuse metrics, failure modes models, reusability assessment models, and reuse library metrics.

Aligning the economic modeling of software reuse with reuse practices (original) (raw)

Related papers