Economic Models and Value-Based Approaches for Product Line Architectures

Thurimella, Anil Kumar; Padmaja, T. Maruthi

doi:10.1016/b978-0-12-410464-8.00002-7

Cited by 5 publications

(3 citation statements)

References 31 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As several researchers have surveyed, multiple cost models for SPLE have been proposed (Khurum et al 2008;Thurimella and Padmaja 2014;Ali et al 2009;Krüger 2016). A cost model aims to support an organization while making an initial assessment whether a product line would pay off or not.…”

Section: Cost Models For Splementioning

confidence: 99%

Software product-line evaluation in the large

et al. 2021

View full text Add to dashboard Cite

Software product-line engineering is arguably one of the most successful methods for establishing large portfolios of software variants in an application domain. However, despite the benefits, establishing a product line requires substantial upfront investments into a software platform with a proper product-line architecture, into new software-engineering processes (domain engineering and application engineering), into business strategies with commercially successful product-line visions and financial planning, as well as into re-organization of development teams. Moreover, establishing a full-fledged product line is not always possible or desired, and thus organizations often adopt product-line engineering only to an extent that deemed necessary or was possible. However, understanding the current state of adoption, namely, the maturity or performance of product-line engineering in an organization, is challenging, while being crucial to steer investments. To this end, several measurement methods have been proposed in the literature, with the most prominent one being the Family Evaluation Framework (FEF), introduced almost two decades ago. Unfortunately, applying it is not straightforward, and the benefits of using it have not been assessed so far. We present an experience report of applying the FEF to nine medium- to large-scale product lines in the avionics domain. We discuss how we tailored and executed the FEF, together with the relevant adaptations and extensions we needed to perform. Specifically, we elicited the data for the FEF assessment with 27 interviews over a period of 11 months. We discuss experiences and assess the benefits of using the FEF, aiming at helping other organizations assessing their practices for engineering their portfolios of software variants.

show abstract

Section: Cost Models For Splementioning

confidence: 99%

Software product-line evaluation in the large

et al. 2021

View full text Add to dashboard Cite

show abstract

“…The tangible benefit is a benefit that can be measured by a number, such as; increasing process time, reducing costs, smoothing cash flow, increasing income, improving quality & accuracy process, etc. While intangible benefit is a benefit that can be felt but difficult to measure by monetary outcomes, such as; increasing customer satisfaction, increasing employee motivation & creativity, growing market share, improving the reputation of a company brand, and so on [17,18]. The implementation of RPA brings tangible & intangible benefits in many areas of the company (see Tab.…”

Section: D -1 St Step: Benefitmentioning

confidence: 99%

The Five Dimensions of Digital Technology Assessment with the Focus on Robotic Process Automation (RPA)

Axmann

Harmoko

2021

Teh. glas. (Online)

View full text Add to dashboard Cite

In Technology Management, the assessment of new digital technologies is a challenging process. Most assessments are focusing on cost & benefit. These approaches often fail because main points are neglected. In this paper, the holistic approach of "The Five Dimensions of Digital Technology Assessment" will be described with the example of RPA (Robotic Process Automation). RPA is one of the most promising technologies to save data processing efforts in the office. The Five Dimensions of RPA Assessment is performed by assessing the benefits, technology readiness, usability, company readiness, and the costs that burden the company in the RPA implementation.

show abstract

“…Cost-Benefit Analysis Method (CBAM) [Kazman et al 2002] and Economics-driven Software Architecture [Thurimella and Padmaja 2014] are examples of approaches that analyze the economic impact of architecture decisions. Value-based Software Engineering (VBSE) [Boehm and Huang 2013] and VALUE framework [Mendes et al 2018] address a broader view of value in software-related decisions.…”

Section: Related Workmentioning

confidence: 99%

Comparison and Choice of Computational Architectures Based on Cost-Value Approach

Ribeiro

Claro

Maciel

2021

iSys

View full text Add to dashboard Cite

Software engineers make use of several computational architectures (CA) to host an application, such as desktop, web, and cloud computing architectures. As the requirements vary according to the desired CA, developers may face two problems: determining which requirement better fulfills a CA and determining which CA fulfills a given set of requirements. This paper presents a new approach based on the Cost-Value Approach (CVA). We have slightly modified the CVA method (SCVA method) and also developed a new method for choosing the most appropriate CA (MMACA method). Our results provide a set of requirements ordered by priority for each CA. Finally, we discuss the current and most appropriate CA for a real project solution.

show abstract

Economic Models and Value-Based Approaches for Product Line Architectures

Cited by 5 publications

References 31 publications

Software product-line evaluation in the large

Software product-line evaluation in the large

The Five Dimensions of Digital Technology Assessment with the Focus on Robotic Process Automation (RPA)

Comparison and Choice of Computational Architectures Based on Cost-Value Approach

Contact Info

Product

Resources

About