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

Tomer, Amir; Goldin, Leah; Kuflik, Tsvi; Kimchi, E.; Schach, Stephen R.

doi:10.1109/tse.2004.50

Cited by 43 publications

(24 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…-Pure verbatim reuse: Frakes and Succi (2001), Mohagheghi et al (2004), Tomer et al (2004) for five assets, Morad and Kuflik (2005) and in the study of Succi et al (2001) we concluded that reuse is most probably verbatim.…”

Section: Reuse Initiationmentioning

confidence: 84%

“…Reuse gave 42% reduction in time to market for product 2. Tomer et al (2004): For all the seven assets, systematic or controlled reuse gave savings relative to new development. For 5 assets, systematic reuse gave savings between 42 to 81 percent compared to new development (measured in person-hours).…”

Section: Metricmentioning

confidence: 97%

“…The term "case study" is often used in literature to cover all studies where some data on "cases" are presented. The review has identified four case studies (Thomas et al, 1997) (Mohagheghi et al, 2004) (Baldassarre et al, 2005) (Selby, 2005), three exploratory case studies ) 2 (Morisio et al, 2002), three experience reports (Zhang and Jarzabek, 2005), and one example application Succi et al (2001) and Tomer et al (2004) have not reported programming language, and four of the papers (Baldassarre et al, 2005) (Zhang and Jarzabek, 2005) have not reported the size of products or the reusable assets, where in (Zhang and Jarzabek, 2005) it is not clear whether 4.5 KLOC is the total size or the mean size of applications. There is variation in domain and programming languages.…”

Section: Objects Types Of Studies Scale Publication Channel and Yearmentioning

confidence: 99%

“…We consider having an explicit reuse program as a type of systematic reuse. Tomer et al (2004) and Morad and Kuflik (2005) define a compromise between these two approaches as well, called controlled reuse, where candidate assets that may be reusable in the future are kept in a repository without putting effort in making them reusable. A future project that uses such asset will make a reusable asset out of it.…”

Section: Reuse Managementmentioning

confidence: 99%

“…-Six studies have reported verbatim and modified reuse, including Tomer et al (2004) for two assets. does not discuss this aspect.…”

Section: Reuse Initiationmentioning

confidence: 99%

See 4 more Smart Citations

Quality, productivity and economic benefits of software reuse: a review of industrial studies

2007

View full text Add to dashboard Cite

Abstract. Systematic software reuse is proposed to increase productivity and software quality and lead to economic benefits. Reports of successful software reuse programs in industry have been published. However, there has been little effort to organize the evidence systematically and appraise it. This review aims to assess the effects of software reuse in industrial contexts. Journals and major conferences between 1994 and 2005 were searched to find observational studies and experiments conducted in industry, returning eleven papers of observational type. Systematic software reuse is significantly related to lower problem (defect, fault or error) density in five studies and to decreased effort spent on correcting problems in three studies. The review found evidence for significant gains in apparent productivity in three studies. Other significant benefits of software reuse were reported in single studies or the results were inconsistent. Evidence from industry is sparse and combining results was done by votecounting. Researchers should pay more attention to using comparable metrics, performing longitudinal studies, and explaining the results and impact on industry.

show abstract

Section: Reuse Initiationmentioning

confidence: 84%

Section: Metricmentioning

confidence: 97%

Section: Objects Types Of Studies Scale Publication Channel and Yearmentioning

confidence: 99%

Section: Reuse Managementmentioning

confidence: 99%

“…-Six studies have reported verbatim and modified reuse, including Tomer et al (2004) for two assets. does not discuss this aspect.…”

Section: Reuse Initiationmentioning

confidence: 99%

See 3 more Smart Citations

Quality, productivity and economic benefits of software reuse: a review of industrial studies

2007

View full text Add to dashboard Cite

show abstract

3.2.2 Enabling Economics‐Driven Systems Engineering Through Reusable Software Architectures and Components

Selby

2007

INCOSE International Symp

View full text Add to dashboard Cite

Economics-driven systems engineering integrates system design principles with measurement-based analyses of value, options, and tradeoffs. This study helps enable economics-driven systems engineering by describing an example of measurement-based analysis of software reuse in large-scale systems. Software reuse enables developers to leverage past accomplishments and facilitates significant improvements in software productivity and quality. Software reuse catalyzes gains in productivity by avoiding redevelopment and gains in quality by incorporating components whose reliability has already been established. The purpose of this study is to characterize software reuse empirically by investigating one development environment that actively reuses software. Twenty-five software systems ranging from 3000 to 112,000 source lines have been selected for analysis from a NASA systems development environment. The amount of software either reused or modified from previous systems averages 32% per project in this environment. Non-parametric statistical models are applied to examine numerous development variables across the software modules in the systems. This research focuses on initial results and graphical characterizations of the data. Four classes of software modules are analyzed: (a) modules reused without revision, (b) modules reused with slight revision (< 25% changes), (c) modules reused with major revision (≥ 25% changes), and (d) newly developed modules. The modules reused without revision had the fewest faults, lowest fault correction effort, and lowest fault densities. In conclusion, we outline future research directions that build on these strategies and ideas.

show abstract

A Case for Product Lines

Nolan

Pickard

Fisher

et al. 2016

INCOSE International Symp

View full text Add to dashboard Cite

It would seem obvious that a business could benefit from a Product Line, but what is the business case, when can we expect benefits and how much do we need to invest? Under what conditions will it not be cost beneficial to adopt a Product Line? A Product Line is complicated, strategic in nature and it is probably beyond the capability of most people to simply “judge” if it is the right strategy. It was evident that in order for Rolls‐Royce to understand Product Lines, and to make the right trade decisions, we would need to develop a Product Line cost/benefit estimation tool. The tool estimated both the costs to develop assets as well as the costs to deploy the assets onto a project. This paper summarizes the estimation tool we developed and some of the conclusions it revealed. Although the concept was used on a Software Product Line, the principles have been duplicated in hardware and Systems Engineering but are not discussed in this paper.

show abstract

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

Cited by 43 publications

References 5 publications

Quality, productivity and economic benefits of software reuse: a review of industrial studies

Quality, productivity and economic benefits of software reuse: a review of industrial studies

3.2.2 Enabling Economics‐Driven Systems Engineering Through Reusable Software Architectures and Components

A Case for Product Lines

Contact Info

Product

Resources

About