Predicting return-on-investment for product line generations

Ganesan, Dharmalingam; Muthig, Dirk; Yoshimura, Kazuyoshi

doi:10.1109/spline.2006.1691573

Cited by 20 publications

(16 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We experienced difficulties collecting historical data (as in [20]), especially for the "before" state of adopting an RA. We noted that C prod and C evo were seldom available since the "before" state did not exist.…”

Section: Execution Of the Methods For Formulating The Economic Modelmentioning

confidence: 99%

“…On the other hand, potential weaknesses of this approach are:  It does not consider RA's software elements degeneration over time [20].  The risk increases when neither real nor historical data are available.…”

Section: Conclusion and Next Stepsmentioning

confidence: 99%

“…As future work, we plan to enrich the economic model by: (1) adding more metrics (such as technical debt [24], degeneration over time [20], risk metrics, homogeneity metrics [10]), and (2) validating it for bigger applications and in more organizations.…”

Section: Conclusion and Next Stepsmentioning

confidence: 99%

“…These cost factors and benefit functions can be used to construct equations that can answer a number of questions such as whether the SPL approach is the best option for development and what is the ROI for this approach. Ganesan et al extended SIMPLE by considering infrastructure degeneration over time [20].…”

mentioning

confidence: 99%

See 3 more Smart Citations

REARM: A Reuse-Based Economic Model for Software Reference Architectures

Martínez‐Fernández

Ayala

Franch

et al. 2013

Safe and Secure Software Reuse

View full text Add to dashboard Cite

Abstract. To remain competitive, organizations are challenged to make informed and feasible value-driven design decisions in order to ensure the quality of their software systems. However, there is a lack of support for evaluating the economic impact of these decisions with regard to software reference architectures. This damages the communication among architects and management, which can result in poor decisions. This paper aims at ameliorating this problem by presenting a pragmatic preliminary economic model to perform cost-benefit analysis on the adoption of software reference architectures as a key asset for optimizing architectural decision-making. The model is based on existing value-based metrics and economics-driven models used in other areas. A preliminary validation based on a retrospective study showed the ability of the model to support a cost-benefit analysis presented to the management of an IT consulting company. This validation involved a cost-benefit analysis related to reuse and maintenance; other qualities will be integrated as our research progresses.

show abstract

Section: Execution Of the Methods For Formulating The Economic Modelmentioning

confidence: 99%

Section: Conclusion and Next Stepsmentioning

confidence: 99%

Section: Conclusion and Next Stepsmentioning

confidence: 99%

mentioning

confidence: 99%

See 2 more Smart Citations

REARM: A Reuse-Based Economic Model for Software Reference Architectures

Martínez‐Fernández

Ayala

Franch

et al. 2013

Safe and Secure Software Reuse

View full text Add to dashboard Cite

show abstract

“…The main difficulties concerning the later are the confidentiality of financial data and lack of support from executives. As an alternative, some researchers use simulation models [86]. Among the directions for future research, Ali Babar et al [5] mention the need for market-oriented economic models, the identification of cost drivers on finer levels of granularity, as well as the need to evaluate assets from the perspective of their quality attributes to determine whether reuse will result in an economic gain or loss.…”

Section: Economical Aspectsmentioning

confidence: 99%

Software diversity: state of the art and perspectives

Schaefer

Rabiser²,

Clarke

et al. 2012

Int J Softw Tools Technol Transfer

136

View full text Add to dashboard Cite

Abstract. Diversity is prevalent in modern software systems to facilitate adapting the software to customer requirements or the execution environment. Diversity has an impact on all phases of the software development process. Appropriate means and organizational structures are required to deal with the additional complexity introduced by software variability. This introductory article to the special section "Software Diversity -Modeling, Analysis and Evolution" provides an overview of the current state of the art in diverse systems development and discusses challenges and potential solutions. The article covers requirements analysis, design, implementation, verification and validation, maintenance and evolution as well as organizational aspects. It also provides an overview of the articles which are part of this special section and address particular issues of diverse systems development.

show abstract

Scoping software process lines

Armbrust

Katahira

Miyamoto

et al. 2009

Softw Process Imprv Pract

View full text Add to dashboard Cite

Defining organization-specific process standards by integrating, harmonizing, and standardizing heterogeneous and often implicit processes is an important task, especially for large development organizations. On the one hand, such a standard must be generic enough to cover all of the organization's development activities; on the other hand, it must be as detailed and precise as possible to support employees' daily work. Today, organizations typically maintain and advance a plethora of individual processes, each addressing specific problems. This requires enormous effort, which could be spent more efficiently. This article introduces an approach to developing a Software Process Line that, similar to a Software Product Line, promises to reduce the complexity and thus, the effort required for managing the processes of a software organization. We propose as majors steps Scoping, Modeling, and Architecting the Software Process Line, and describe in detail the Scoping approach werecommend, based on an analysis of the potential products to be produced in the future, the projects expected for the future, and the respective process capabilities needed. In addition, the article sketches experience from determining the scope of space process standards for satellite software development. Finally, it discusses the approach, and related work, conclusions, and an outlook on future work are presented

show abstract

Predicting return-on-investment for product line generations

Cited by 20 publications

References 4 publications

REARM: A Reuse-Based Economic Model for Software Reference Architectures

REARM: A Reuse-Based Economic Model for Software Reference Architectures

Software diversity: state of the art and perspectives

Scoping software process lines

Contact Info

Product

Resources

About