Eliminating the adoption barrier

Krueger, Charles W.

doi:10.1109/ms.2002.1020284

Cited by 80 publications

(57 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Product families or in general any reuse program may be initiated in multiple ways (Krueger, 2002): -Proactive when companies can predict their reuse requirements and have resources to design all reusable assets up-front; -Reactive when one or several product variations are developed at a time; -Extractive when reusable assets are extracted from one or several products to make the product family baseline.…”

Section: Reuse Initiationmentioning

confidence: 99%

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: 99%

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

2007

View full text Add to dashboard Cite

show abstract

“…To mitigate the weaknesses on communication and collaboration, an extractive model (Krueger, 2002) with with an incremental or pilot technology transfer strategy, which reuses one or more existing software products for the product line could be more appropriated to foster interest from the company.…”

Section: Technology Transfer Strategymentioning

confidence: 99%

Software product line scoping and requirements engineering in a small and medium-sized enterprise: An industrial case study

Silva

Neto²,

O’Leary

et al. 2014

Journal of Systems and Software

View full text Add to dashboard Cite

Software Product Line (SPL) engineering has been applied in several domains, especially in large-scale software development. Given the benefits experienced and reported, SPL engineering has increasingly garnered interest from small to medium-sized companies. It is possible to find a wide range of studies reporting on the challenges of running a SPL project in large companies. However, very little reports exist that consider the situation for small to medium-sized enterprises and these studies try develop universal truths for SPL without lessons learned from empirical evidence need to be contextualized. This study is a step towards bridging this gap in contextual evidence by characterizing the weaknesses discovered in the Scoping (SC) and Requirements (RE) disciplines of SPL. Moreover, in this study we conducted a case study in a Small to Medium sized Enterprises (SMEs) to justify the use of agile methods when introducing the SPL SC and RE disciplines through the characterization of their bottlenecks. The results of the characterization indicated that ineffective communication and collaboration, long iteration cycles, and the absence of adaptability and flexibility can increase the effort and reduce motivation during project development. These issues can be mitigated by agile methods.

show abstract

“…During the adoption, the change effort needed is usually underestimated and timetables are often defined to be too tight [8,26]. In addition, this is challenging, as normally resources have to be shifted from existing projects, and those rarely have resources to spare [7].…”

Section: Software Product Line Adoptionmentioning

confidence: 99%

“…McGregor et al [9] present two main types of adoption strategies, which they call heavyweight and lightweight strategies. Krueger [8] discusses about proactive, reactive, and extractive adoption models. Further, according to Schmid and Verlage [10], there are four types of situations when adopting a product line: independent, project-integrating, reengineering-driven, and leveraged.…”

Section: Software Product Line Adoption Strategiesmentioning

confidence: 99%

“…In the cases where the organization has already products, or even a product line, which are worth to utilize, it may choose an exploitation of existing systems strategy. That strategy can also facilitate the adoption barrier of large-scale reuse as the organization can reuse existing items (software, tools, people, organization charts, and processes) to establish a product line [8].…”

Section: Software Product Line Adoption Strategiesmentioning

confidence: 99%

See 1 more Smart Citation

Software Product Line Adoption – Guidelines from a Case Study

Kuvaja

Similä

Hanhela³

2011

Software Engineering Techniques

View full text Add to dashboard Cite

Abstract. It is possible to proceed with software product line adoption only once without major reinvestments and loss of time and money. In the literature, reported experiences of using the adoption models are not to be found, and especially the suitability of the models has not been reported. The purpose of this research is to compare known adoption models by formulating general evaluation criteria for the selection of an adoption model. Next an adoption model is selected for empirical research based on the context of a multimedia unit of a global telecommunication company. The empirical part consists of a case study analyzing the present state of adoption and producing plans for proceeding with the adoption. The research results can be utilized when selecting an adoption model for an empirical case and adopting a software product line in a software intensive organization.

show abstract

Eliminating the adoption barrier

Cited by 80 publications

References 1 publication

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

Software product line scoping and requirements engineering in a small and medium-sized enterprise: An industrial case study

Software Product Line Adoption – Guidelines from a Case Study

Contact Info

Product

Resources

About