A decision-making process-line for selection of software asset origins and components

Badampudi, Deepika; Wnuk, Krzysztof; Wohlin, Claes; Franke, Ulrik; Šmite, Darja; Cicchetti, Antonio

doi:10.1016/j.jss.2017.09.033

Cited by 20 publications

(28 citation statements)

References 37 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As future work, we aim to validate the effectiveness of our approach by testing it on more sophisticated systems of different architectures. Moreover, we are interested in identifying additional metrics to refine the cost estimation function [22] by taking organizational factors in concern [23]. Finally, we aim to integrate our approach in a global software product line environment [24] to benefit from systematic reuse of existing products and variability management during configuration.…”

Section: Discussionmentioning

confidence: 99%

Clone-and-Own software product derivation based on developer preferences and cost estimation

Ghabach

Blay–Fornarino

Khoury

et al. 2018

2018 12th International Conference on Research Challenges in Information Science (RCIS)

View full text Add to dashboard Cite

Clone-and-own is a common reuse practice that is widely adopted for evolving a family of software systems. However, this practice loses its effectiveness if not supported with valuable indicators that guide the derivation of new products. In this paper, we propose an approach to support the derivation of new product variants based on clone-and-own, by providing the possible scenarios in terms of operations to perform to accomplish the derivation. We generate a constraints system prior to a product derivation, to facilitate the software engineer selection of the suitable scenario and operations based on his preferences. In addition, we propose a cost estimation for each operation and respectively for each scenario, thus, a software engineer can rely on it as an additional parameter to achieve the derivation. The proposed scenarios and cost estimation are based on indicators retrieved after an automated identification of the mappings between the features implemented by the family of software products and the assets in which they are implemented. We preliminarily validate our approach on a case study where results show that the provided support can considerably reduce the amount of time and efforts that can be required to achieve a product derivation. Index Terms-Clone-and-own, product derivation, software reuse.

show abstract

Section: Discussionmentioning

confidence: 99%

Clone-and-Own software product derivation based on developer preferences and cost estimation

Ghabach

Blay–Fornarino

Khoury

et al. 2018

2018 12th International Conference on Research Challenges in Information Science (RCIS)

View full text Add to dashboard Cite

show abstract

“…A majority of the questions consisted of three Likert scales, addressing: 1) development process, 2) sourcing strategies, and 3) development context, in total encompassing 25 Likert items. e selection of statements was in uenced by SWEBOK v. 3.0 [46], ISO/IEC 25010 on quality requirements [12], Murhphy-Hill et al's comparison between game development and traditional so ware engineering [31], and Badampudi et al's research on sourcing options [3]. We calculated descriptive statistics for the survey, including Spearman's rankorder correlation coe cients.…”

Section: Methodsmentioning

confidence: 99%

“…A recurring strategic consideration in so ware projects is whether to develop an asset internally or acquire it from external sources. In so ware projects, the decision involves choosing between several di erent sourcing options [3]. First, a GovAg can develop a so ware asset in-house.…”

Section: Sourcing Strategies (Rq2)mentioning

confidence: 99%

“…GovAgs o en have needs unlike any other actor, and when procuring speci c IT services a GovAg might nds itself a single buyer on the market. Moreover, sometimes only a few providers on the market o er services geared speci cally towards the public sector, thus limiting procurement and sourcing options [3,24]. Previous work on Swedish GovAgs reports that both so ware scaling and general so ware process improvement have been ongoing in recent years [6,20], but there is no overview available of the current state-of-practice in the GovAgs' so ware projects.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Digitalization of swedish government agencies

Borg

Olsson

Franke

et al. 2018

Proceedings of the 40th International Conference on Software Engineering: Software Engineering in Society

Self Cite

View full text Add to dashboard Cite

So ware engineering is at the core of the digitalization of society. Ill-informed decisions can have major consequences, as made evident in the 2017 government crisis in Sweden, originating in a data breach caused by an outsourcing deal made by the Swedish Transport Agency. Many Government Agencies (GovAgs) in Sweden are rapidly undergoing a digital transition, thus it is important to overview how widespread, and mature, so ware development is in this part of the public sector. We present a so ware development census of Swedish GovAgs, complemented by document analysis and a survey. We show that 39.2% of the GovAgs develop so ware internally, some matching the number of developers in large companies. Our ndings suggest that the development largely resembles private sector counterparts, and that established best practices are implemented. Still, we identify improvement potential in the areas of strategic sourcing, openness, collaboration across GovAgs, and quality requirements. e Swedish Government has announced the establishment of a new digitalization agency next year, and our hope is that the so ware engineering community will contribute its expertise with a clear voice.

show abstract

“…The study presented in this paper is part of a research project, named ORION 1 that has exclusively studied decision-making on asset selection. The project has utilized decision theory (Starmer 2000) as a foundation to produce a taxonomy for decision-making as well as decision models and frameworks (Wohlin et al 2016;Badampudi et al 2018). The taxonomy, GRADE (Goals, Roles, Assets, Decisions and Environment) (Martens and Teuteberg 2012;Papatheocharous et al 2015), takes a wider view at decision-making and the many diverse factors that asset selection includes, e.g., asset origin and asset qualities.…”

Section: Introductionmentioning

confidence: 99%

Characteristics that affect preference of decision models for asset selection: an industrial questionnaire survey

et al. 2019

View full text Add to dashboard Cite

Modern software development relies on a combination of development and re-use of technical asset, e.g., software components, libraries, and APIs. In the past, re-use was mostly conducted with internal assets but today external; open source, customer off-the-shelf (COTS), and assets developed through outsourcing are also common. This access to more asset alternatives presents new challenges regarding what assets to optimally chose and how to make this decision. To support decision-makers, decision theory has been used to develop decision models for asset selection. However, very little industrial data has been presented in literature about the usefulness, or even perceived usefulness, of these models. Additionally, only limited information has been presented about what model characteristics determine practitioner preference toward one model over another. The objective of this work is to evaluate what characteristics of decision models for asset selection determine industrial practitioner preference of a model when given the choice of a decision model of high precision or a model with high speed. An industrial questionnaire survey is performed where a total of 33 practitioners, of varying roles, from 18 companies are tasked to compare two decision models for asset selection. Textual analysis and formal and descriptive statistics are then applied on the survey responses to answer the study's research questions. The study shows that the practitioners had clear preference toward the decision model that emphasized speed over the one that emphasized decision precision. This conclusion was determined to be because one of the models was perceived faster, had lower complexity, was more flexible in use for different decisions, and was more agile on how it could be used in operation, its emphasis on people, its emphasis on "good enough" precision and ability to fail fast if a decision was a failure. Hence, we found seven characteristics that the practitioners considered important for their acceptance of the model. Industrial practitioner preference, which relates to acceptance, of decision models for asset selection is dependent on multiple characteristics that must be considered when developing a model for different types of decisions such as operational day-today decisions as well as more critical tactical or strategic decisions. The main contribution of this work are the seven identified characteristics that can serve as industrial requirements for future research on decision models for asset selection.

show abstract

A decision-making process-line for selection of software asset origins and components

Cited by 20 publications

References 37 publications

Clone-and-Own software product derivation based on developer preferences and cost estimation

Clone-and-Own software product derivation based on developer preferences and cost estimation

Digitalization of swedish government agencies

Characteristics that affect preference of decision models for asset selection: an industrial questionnaire survey

Contact Info

Product

Resources

About