A Comparative Survey of Economic Models for Software Product Lines
---
paper_title: Software Product Line Engineering Foundations Principles And Techniques

paper_content:

Thank you for reading software product line engineering foundations principles and techniques. Maybe you have knowledge that, people have look numerous times for their favorite books like this software product line engineering foundations principles and techniques, but end up in malicious downloads. Rather than reading a good book with a cup of coffee in the afternoon, instead they are facing with some infectious bugs inside their desktop computer.
---
paper_title: An Initial Model of Product Line Economics

paper_content:

In this paper we describe an initial model of product line economics, which aims at filling exactly this gap. The model integrates characteristics of the software process with aspects of the market, where the later are used for valuation. We present the model in three layers, each adding a layer of issues that are taken into account to the previous one. This layering mirrors the levels of complexity in existing models of reuse economics.
---
paper_title: Developing, validating and evolving an approach to product line benefit and risk assessment

paper_content:

Product line engineering is usually a very beneficial, but sometimes also a very risky endeavor, as there is no guarantee for economic success. In this paper, we describe an assessment approach that is designed to address the problem of quantifying reuse risks by providing an efficient means for determining the benefits and risks associated with a specific product line development. In particular, the approach supports decomposition and individual assessment of the technical domains of the product line, thus also furthering the incremental introduction of product lines. At the core of this paper is the development of the underlying assessment technology and how this approach was evolved over time based on multiple case studies. This evolution approach is rather general. Thus, we see the potential of applying these techniques also for evolving other assessment approaches.
---
paper_title: Software reuse: metrics and models

paper_content:

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.
---
paper_title: Reuse economics: a comparison of seventeen models and directions for future research

paper_content:

The paper baselines the state of the art in reuse economic modeling by surveying and comparing seventeen economic models and presenting conclusions and recommendations for further research. The analyses indicate a great deal of commonality among the set of models. While this may indicate that researchers are arriving at similar models independently, it may also suggest that we should direct our efforts at forging new ground in reuse economics. Five areas for further research in reuse economics are recommended, and general guidelines for helping organizations decide on a suitable economic model are discussed.
---
paper_title: An Initial Model of Product Line Economics

paper_content:

In this paper we describe an initial model of product line economics, which aims at filling exactly this gap. The model integrates characteristics of the software process with aspects of the market, where the later are used for valuation. We present the model in three layers, each adding a layer of issues that are taken into account to the previous one. This layering mirrors the levels of complexity in existing models of reuse economics.
---
paper_title: An integrated cost model for software reuse

paper_content:

Several cost models have been proposed in the past for estimating, predicting, and analyzing the costs of software reuse. In this paper we analyze existing models, explain their variance, and propose a tool-supported comprehensive model that encompasses most of the existing models.
---
paper_title: Assessing the cost-effectiveness of software reuse: a model for planned reuse

paper_content:

Information systems development is typically acknowledged as an expensive and lengthy process, often producing code that is of uneven quality and difficult to maintain. Software reuse has been advocated as a means of revolutionizing this process. The claimed benefits from software reuse are reduction in development cost and time, improvement in software quality, increase in programmer productivity, and improvement in maintainability. Software reuse entails undeniable costs of creating, populating, and maintaining a library of reusable components. There is anecdotal evidence to suggest that some organizations benefit from reuse. However, many software developers practicing reuse claim these benefits without formal demonstration thereof. There is little research to suggest when the benefits are expected and to what extent they will be realized. For example, does a larger library of reusable components lead to increased savings? What is the impact of component size on the effectiveness of reuse? This research seeks to address some of these questions. It represents the first step in a series wherein the effects of software reuse on overall development effort and costs are modelled with a view to understanding when it is most effective.
---
paper_title: Reuse economics: a comparison of seventeen models and directions for future research

paper_content:

The paper baselines the state of the art in reuse economic modeling by surveying and comparing seventeen economic models and presenting conclusions and recommendations for further research. The analyses indicate a great deal of commonality among the set of models. While this may indicate that researchers are arriving at similar models independently, it may also suggest that we should direct our efforts at forging new ground in reuse economics. Five areas for further research in reuse economics are recommended, and general guidelines for helping organizations decide on a suitable economic model are discussed.
---
paper_title: An Initial Model of Product Line Economics

paper_content:

In this paper we describe an initial model of product line economics, which aims at filling exactly this gap. The model integrates characteristics of the software process with aspects of the market, where the later are used for valuation. We present the model in three layers, each adding a layer of issues that are taken into account to the previous one. This layering mirrors the levels of complexity in existing models of reuse economics.
---
paper_title: An integrated cost model for software reuse

paper_content:

Several cost models have been proposed in the past for estimating, predicting, and analyzing the costs of software reuse. In this paper we analyze existing models, explain their variance, and propose a tool-supported comprehensive model that encompasses most of the existing models.
---
paper_title: An Initial Model of Product Line Economics

paper_content:

In this paper we describe an initial model of product line economics, which aims at filling exactly this gap. The model integrates characteristics of the software process with aspects of the market, where the later are used for valuation. We present the model in three layers, each adding a layer of issues that are taken into account to the previous one. This layering mirrors the levels of complexity in existing models of reuse economics.
---
paper_title: Predicting return-on-investment for product line generations

paper_content:

The decision of an organization to introduce product line engineering depends on a sound and careful analysis of risks and return on investment. The latter is computed by an economic model, which relies on high quality input and must reflect the envisioned migration strategy sufficiently. To facilitate risk analysis, this paper applies Monte-Carlo simulation to an existing product line economic model. Additionally, the model is extended by the support of product line generations that is, considering the degeneration of product line infrastructures and taking reinvestment into an existing product line into account. The practical application of the model is demonstrated by an industrial case study
---
paper_title: Panel: a competition of software product line economic models

paper_content:

Proponents of different software product line and software reuse economic models will be given a real-world software product line scenario and asked to predict alternate outcomes and to justify – with hard data from their models – some of the difficult choices that need to be made in the scenario. The audience will have a chance to compare, side by side, the predictions, recommendations, insights, intuitive fidelity and ease-of-use of the different models.
---
paper_title: Software Product Line Engineering Foundations Principles And Techniques

paper_content:

Thank you for reading software product line engineering foundations principles and techniques. Maybe you have knowledge that, people have look numerous times for their favorite books like this software product line engineering foundations principles and techniques, but end up in malicious downloads. Rather than reading a good book with a cup of coffee in the afternoon, instead they are facing with some infectious bugs inside their desktop computer.
---
paper_title: Software reuse: metrics and models

paper_content:

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.
---
paper_title: Predicting return-on-investment for product line generations

paper_content:

The decision of an organization to introduce product line engineering depends on a sound and careful analysis of risks and return on investment. The latter is computed by an economic model, which relies on high quality input and must reflect the envisioned migration strategy sufficiently. To facilitate risk analysis, this paper applies Monte-Carlo simulation to an existing product line economic model. Additionally, the model is extended by the support of product line generations that is, considering the degeneration of product line infrastructures and taking reinvestment into an existing product line into account. The practical application of the model is demonstrated by an industrial case study
---
paper_title: Reuse economics: a comparison of seventeen models and directions for future research

paper_content:

The paper baselines the state of the art in reuse economic modeling by surveying and comparing seventeen economic models and presenting conclusions and recommendations for further research. The analyses indicate a great deal of commonality among the set of models. While this may indicate that researchers are arriving at similar models independently, it may also suggest that we should direct our efforts at forging new ground in reuse economics. Five areas for further research in reuse economics are recommended, and general guidelines for helping organizations decide on a suitable economic model are discussed.
---
paper_title: Impact of Architecture and Quality Investment in Software Product Line Development

paper_content:

Investment in architecture and quality improvement for a software product line can increase reuse, and consequently reduce effort, enhance product reliability, and shorten time- to-market. Such investments should be carefully chosen to be effective, to avoid over-investment, and to return benefits within the desired time. In this paper, we show how a stochastic simulation model can be used to explore the impacts of such investments. The model is validated by comparison to COPLIMO, a COCOMO II based effort estimation model for product line development, and by inspecting effort distributions of the generated unplanned work. For the illustrative model and scenarios in this paper, we show that the degree of architecture reuse has the largest impact. Preventing degraded architectural dependencies itself does not have a meaningful impact, but if such degradation is also associated with adverse effects on defect injection and detection, it can be significant. Process improvement has a meaningful impact, but over-investment is possible.
---
paper_title: Predicting When Product Line Investment Pays

paper_content:

Abstract : A product line approach may appear very attractive, with obvious benefits in speedier time to market and higher quality, however many organizations demand financial justification before proceeding. Without knowing costs, the decision makers won't budget funds or personnel to carry out the up-front asset construction tasks. In addition, not all organizations are ready to commit up front to a full asset set, one that covers most if not all product line features. Many managers favor an incremental approach to product line adoption, one that first tackles areas of highest and most readily available commonality, earning payback early in the adoption cycle. This report defines key factors to consider in taking an incremental approach to fielding a product line. An organization building a business case can apply these factors to show that product line investment can result in product development savings. The example presented here shows a net savings of almost $180 million in projects that would have cost about $600 million under traditional development approaches. The $180 million in savings takes into account an investment of $54 million in product line start-up costs. The example also illustrates ways to present the data needed to make a compelling business case.
---
paper_title: Economics of Software Product Lines

paper_content:

Software Product Lines (SPL) offer tremendous potential to improve a company's competitive position and responsiveness to changing market needs. However, unless the full benefits and costs are well understood by executive-level stakeholders, the probability of success will be low. An SPL economic analysis framework is presented that is based on the author's experience with SPL adoption at Convergys. While derived from the Convergys experience, it is hoped that this framework will be of value to other companies contemplating a transition to an SPL.
---
paper_title: InCoME: Integrated Cost Model for Product Line Engineering

paper_content:

A large number of software organizations are adopting the software product line approach in their reuse program. One fundamental factor to evaluate cost-benefit of this approach is the practical use of cost models to estimate if an investment is worthwhile for a family of products. This paper analyzes the most significant cost models for product line engineering and it highlights the set of features that makes an effective model. This work also presents an integrated cost model for product line engineering with its foundations and elements. At the end, is presented a discussion over the results of a case study where the model was applied.
---
paper_title: Comparing Costs and Benefits of Different Test Strategies for a Software Product Line: A Study from Testo AG

paper_content:

Quality assurance in general and testing in particular remains as an unsolved problem in product line engineering. It is unclear, from an economic point of view, whether one should test each product line member separately or test just product-specific parts and compose them with tested core assets from family engineering. While the former strategy introduces redundancy in testing, the latter strategy is also more difficult because of genericity. Ideally, we need to carefully calculate cost-benefits of both cases and define a test strategy accordingly. Currently, there is no economic model for testing in the context of product lines. Thus, we introduce an initial economic model, and then perform Monte-Carlo simulations to calculate cost-benefit of the two test strategies. For the Testo product line of climate and flue gas measurement devices, the results showed that, using an infrastructure-focused test strategy, on average a cost saving of 13% can be expected with 87% certainty.
---
paper_title: Software Product Lines: Practices and Patterns

paper_content:

Foreword. Preface. Acknowledgements. Dedication. Reader's Guide. I. SOFTWARE PRODUCT LINE FUNDAMENTALS. 1. Basic Ideas and Terms. What Is a Software Product Line? What Software Product Lines Are Not. Fortuitous Small-Grained Reuse. Single-System Development with Reuse. Just Component-Based Development. Just a Reconfigurable Architecture. Releases and Versions of Single Products. Just a Set of Technical Standards. A Note on Terminology. For Further Reading. Discussion Questions. 2. Benefits. Organizational Benefits. Individual Benefits. Benefits versus Costs. For Further Reading. Discussion Questions. 3. The Three Essential Activities. What Are the Essential Activities? Core Asset Development. Product Development. Management. All Three Together. For Further Reading. Discussion Questions. II. SOFTWARE PRODUCT LINE PRACTICE AREAS. Describing the Practice Areas. Starting versus Running a Product Line. Organizing the Practice Areas. 4. Software Engineering Practice Areas. Architecture Definition. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Architecture Evaluation. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Component Development. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. COTS Utilization. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Mining Existing Assets. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. Discussion Questions. Requirements Engineering. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Software System Integration. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Testing. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Understanding Relevant Domains. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. 5. Technical Management Practice Areas. Configuration Management. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Data Collection, Metrics, and Tracking. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Make/Buy/Mine/Commission Analysis. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Process Definition. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Scoping. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Technical Planning. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. Discussion Questions. Technical Risk Management. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Tool Support. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. 6. Organizational Management Practice Areas. Building a Business Case. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Customer Interface Management. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. Discussion Questions. Developing an Acquisition Strategy. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Funding. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. Discussion Questions. Launching and Institutionalizing. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. Discussion Questions. Market Analysis. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Operations. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Organizational Planning. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. Discussion Questions. Organizational Risk Management. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Structuring the Organization. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. Discussion Questions. Technology Forecasting. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. Training. Aspects Peculiar to Product Lines. Application to Core Asset Development. Application to Product Development. Specific Practices. Practice Risks. For Further Reading. Discussion Questions. III. PUTTING THE PRACTICE AREAS INTO ACTION. 7. Software Product Line Practice Patterns. The Value of Patterns. Software Product Line Practice Pattern Descriptions. The Curriculum Pattern. The Essentials Coverage Pattern. Each Asset Pattern. What to Build Pattern. Product Parts Pattern. Assembly Line Pattern. Monitor Pattern. Product Builder Pattern. Cold Start Pattern. In Motion Pattern. Process Pattern. Factory Pattern. Other Patterns. Practice Area Coverage. Discussion Questions. 8. Product Line Technical Probe. What Is the Product Line Technical Probe? Probe Interview Questions. Probe Participants. Probe Process. Using the Probe Results. Conducting a Mini Self-Probe. Discussion Questions. 9. Cummins Engine Company: Embracing the Future. Prologue. Company History. A Product Line of Engine Software. Getting off the Ground. An Organization Structured for Cooperation. Running the Product Line. Results. Lessons Learned. Epilogue. Practice Area Compendium. For Further Reading. Discussion Questions. 10. Control Channel Toolkit: A Software Product Line that Controls Satellites. Contextual Background. Organizational Profiles. Project History. Control Channels. Launching CCT. Developing a Business Case for CCT. Developing the Acquisition Strategy and Funding CCT. Structuring the CCT Organization. Organizational and Technical Planning. Operations. Engineering the CCT Core Assets. Domain Analysis. Architecture. Component Engineering. Testing: Application and Test Engineering. Sustainment Engineering: Product Line Evolution. Documentation. Managing the CCT Effort. Early Benefits from CCT. First CCT Product. Benefits beyond CCT Products. Lessons and Issues. Tool Support Is Inadequate. Domain Analysis Documentation Is Important. An Early Architecture Focus Is Best. Product Builders Need More Support. CCT Users Need Reuse Metrics. It Pays to Be Flexible, and Cross-Unit Teams Work. A Real Product Is a Benefit. Summary. For Further Reading. Discussion Questions. 11. Successful Software product Line Development in Small Organization. Introduction. The Early Years. The MERGER Software Product Line. Market Maker Software Product Line Practices. Architecture Definition. Component Development. Structuring (and Staffing) the Organization. Testing. Data Collection and Metrics. Launching and Institutionalizing the Product Line. Understanding the Market. Technology Forecasting. A Few Observations. Effects of Company Culture. Cost Issues. The Customer Paradox. Tool Support. Lessons Learned. Drawbacks. Conclusions: Software Product Lines in Small Organizations. For Further Reading. Discussion Questions. 12. Conclusions: Practices, Patterns and Payoffs. The Practices. The Patterns. The Success Factors. The Payoff. Finale. Glossary. Bibliography. Index.
---
paper_title: Reuse economics: a comparison of seventeen models and directions for future research

paper_content:

The paper baselines the state of the art in reuse economic modeling by surveying and comparing seventeen economic models and presenting conclusions and recommendations for further research. The analyses indicate a great deal of commonality among the set of models. While this may indicate that researchers are arriving at similar models independently, it may also suggest that we should direct our efforts at forging new ground in reuse economics. Five areas for further research in reuse economics are recommended, and general guidelines for helping organizations decide on a suitable economic model are discussed.
---
paper_title: Quality-Attribute Based Economic Valuation of Architectural Patterns

paper_content:

Architectural patterns generate value depending on the utility of the quality attributes that can be achieved from the application of those patterns. However, methods to rigorously evaluate the value-added of patterns do not exist. In this position paper, we make the case that architectural patterns carry economic value in the form of real options, providing designers with the right, but not the obligation, to take subsequent design actions in the future in the face of uncertainty. We summarize our observations in evaluating the relative value of patterns using real option valuation models on a model problem. We draw attention to how such economics-informed approaches can provide belter insights for the selection of situated design strategies.
---
paper_title: Predicting When Product Line Investment Pays

paper_content:

Abstract : A product line approach may appear very attractive, with obvious benefits in speedier time to market and higher quality, however many organizations demand financial justification before proceeding. Without knowing costs, the decision makers won't budget funds or personnel to carry out the up-front asset construction tasks. In addition, not all organizations are ready to commit up front to a full asset set, one that covers most if not all product line features. Many managers favor an incremental approach to product line adoption, one that first tackles areas of highest and most readily available commonality, earning payback early in the adoption cycle. This report defines key factors to consider in taking an incremental approach to fielding a product line. An organization building a business case can apply these factors to show that product line investment can result in product development savings. The example presented here shows a net savings of almost $180 million in projects that would have cost about $600 million under traditional development approaches. The $180 million in savings takes into account an investment of $54 million in product line start-up costs. The example also illustrates ways to present the data needed to make a compelling business case.
---
paper_title: Panel: a competition of software product line economic models

paper_content:

Proponents of different software product line and software reuse economic models will be given a real-world software product line scenario and asked to predict alternate outcomes and to justify – with hard data from their models – some of the difficult choices that need to be made in the scenario. The audience will have a chance to compare, side by side, the predictions, recommendations, insights, intuitive fidelity and ease-of-use of the different models.
---

Title: A Comparative Survey of Economic Models for Software Product Lines

Section 1: INTRODUCTION
Description 1: Introduce the importance of financial and economic aspects in adopting Software Product Line Engineering (SPLE) and summarize the need for economic models to make informed go/no-go decisions.

Section 2: RELATED WORK
Description 2: Discuss previous efforts in reviewing and comparing economic models, especially focusing on software reuse economics, and relate them to SPLE economic models.

Section 3: APPROACH
Description 3: Explain the methodology and criteria used for comparing the economic models for SPLE, including the perspectives considered for the comparison.

Section 4: Analysis
Description 4: Provide a detailed comparison of selected economic models based on various criteria such as scope, type of analysis, economic function, underlying model, viewpoints, scenario, market attributes, cost factors, and risk adjustment.

Section 5: Issues in Modeling SPL Economics
Description 5: Identify and discuss the challenges and limitations in existing SPL economic models, including the differences in cost accumulation methods and the inherent assumptions of the models.

Section 6: Need for Validation
Description 6: Emphasize the necessity of empirical validation for SPL economic models, noting the lack of quantitative data and the potential use of simulation models for sensitivity analysis.

Section 7: Future Directions
Description 7: Suggest potential areas for future research and improvements in SPL economic modeling, including market-oriented models, consideration of uncertainties, identification of cost drivers, and evaluation of reusable assets.

Section 8: CONCLUSION
Description 8: Summarize the key findings from the survey, the importance of understanding the strengths and limitations of different economic models, and the ongoing journey of product line economic modeling.