Adopting and Institutionalizing a Product Line Culture

Böckle, Günter; Muñoz, Jesús Bermejo; Knauber, Peter; Krueger, Charles W.; Leite, Julio César Sampaio do Prado; Linden, Frank van der; Northrop, Linda; Stark, Mike; Weiss, David M.

doi:10.1007/3-540-45652-x_4

Cited by 25 publications

(18 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As compared to the many experience papers published in the literature (e.g. [3,7,12,19]), one could claim that our product family is rather small in size. Still we believe it is representative as some type of "boundary example": in spite of its relative small scale, its evolution became unmanageable.…”

Section: Starting Pointmentioning

confidence: 94%

Observations from the Recovery of a Software Product Family

Lago

Vliet

2004

Software Product Lines

View full text Add to dashboard Cite

Abstract. The problem of managing the evolution of complex and large software systems is well known. Evolution implies reuse and modification of existing software artifacts, and this means that the related knowledge must be documented and maintained. This paper focuses on the evolution of software product families, although the same principles apply in other software development environments as well. We describe our experience gained in a case study recovering a family of six software products. We give an overview of the case study, and report a list of lessons learned, a list of implicit assumptions reconstructed during the case study, and some rules that we think are generally applicable. Our experience indicates that organizing architectural knowledge is a difficult issue. To properly serve the various uses of this knowledge, it needs to be organized along different dimensions. For effective use, tools are required. Our experience also indicates that, next to variability explicitly designed into the product family, there is a "variation creep", caused by different, and evolving, technical and organizational environments of the products. We propose to explicitly model invariabilities, next to variabilities, in software product lines to get a better grip on this variation creep.

show abstract

Section: Starting Pointmentioning

confidence: 94%

Observations from the Recovery of a Software Product Family

Lago

Vliet

2004

Software Product Lines

View full text Add to dashboard Cite

show abstract

“…According to Bosch, the different alternatives of adoption should be understood and evaluated, rather than blindly following a standard model [27]. The adoption itself starts with an assessment of the current state [7]. Therefore, it is essential to understand different challenges, strategies and models related to software product line adoption.…”

Section: Software Product Line Engineeringmentioning

confidence: 99%

“…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]. Organizations are typically hesitant to invest in changes if they do not have obvious, short-term Return on Investment (ROI) [2].…”

Section: Software Product Line Adoptionmentioning

confidence: 99%

“…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. Böckle et al [7] divide transition strategies into four groups, which are called incremental introduction, incremental investment, pilot first, and big bang. Bosch [6] divides the adoption process to two different approaches, evolutionary and revolutionary, for two different situations depending on are the existing items utilized or not.…”

Section: Software Product Line Adoption Strategiesmentioning

confidence: 99%

“…Böckle et al [7] has introduced a General Adoption Process Model for adopting a software product line. It has four main phases focusing on stakeholders, business cases, adoption plan, and launching and institutionalizing.…”

Section: Software Product Line Adoption Modelsmentioning

confidence: 99%

See 2 more Smart Citations

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

Staged adoption of software product families

Bosch

2005

Softw Process Imprv Pract

View full text Add to dashboard Cite

Several approaches to implement the concepts of software product families exist, but there is a tendency towards a revolutionary adoption. A revolutionary adoption of software product families is, however, a high-risk undertaking that may easily fail. Even if an iterative, evolutionary adoption is applied, there is a substantial risk that mismatches may develop in the organization due to a sub-optimal adoption approach. Mismatches between the optimal approach and the one currently used by an organization may lead to several problems, such as a high degree of erosion, mismatches between product needs and shared components, organizational 'noise' and inefficient knowledge management. This article (1) presents the problems resulting from the aforementioned mismatch, (2) presents the relevant decision dimensions that define the space of alternatives, (3) discusses the advantages and disadvantages of each alternative and (4) presents a framework for selecting the best alternative for each decision dimension based on a three-stage adoption model.

show abstract

Adopting and Institutionalizing a Product Line Culture

Cited by 25 publications

References 1 publication

Observations from the Recovery of a Software Product Family

Observations from the Recovery of a Software Product Family

Software Product Line Adoption – Guidelines from a Case Study

Staged adoption of software product families

Contact Info

Product

Resources

About