Choosing Component Origins for Software Intensive Systems: In-House, COTS, OSS or Outsourcing?—A Case Survey

Petersen, Kai; Badampudi, Deepika; Shah, Syed Muhammad Ali; Wnuk, Krzysztof; Gorschek, Tony; Papatheocharous, Efi; Axelsson, Jakob; Sentilles, Séverine; Crnković, Ivica; Cicchetti, Antonio

doi:10.1109/tse.2017.2677909

Cited by 42 publications

(77 citation statements)

References 55 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We use a case survey method to collect and analyze primary data from start-up companies. The method is aimed to balance studying a few cases in depth with traditional (multi) case studies and quantitatively studying many cases [35]. Case studies offer greater level of detail and internal validity by closely examining multiple data sources.…”

Section: Methodsmentioning

confidence: 99%

See 1 more Smart Citation

A Progression Model of Software Engineering Goals, Challenges, and Practices in Start-Ups

Klotins

Unterkalmsteiner

Chatzipetrou

et al. 2021

IIEEE Trans. Software Eng.

Self Cite

View full text Add to dashboard Cite

Context: Software start-ups are emerging as suppliers of innovation and software-intensive products. However, traditional software engineering practices are not evaluated in the context, nor adopted to goals and challenges of start-ups. As a result, there is insufficient support for software engineering in the start-up context. Objective: We aim to collect data related to engineering goals, challenges, and practices in start-up companies to ascertain trends and patterns characterizing engineering work in start-ups. Such data allows researchers to understand better how goals and challenges are related to practices. This understanding can then inform future studies aimed at designing solutions addressing those goals and challenges. Besides, these trends and patterns can be useful for practitioners to make more informed decisions in their engineering practice. Method: We use a case survey method to gather first-hand, in-depth experiences from a large sample of software start-ups. We use open coding and cross-case analysis to describe and identify patterns, and corroborate the findings with statistical analysis. Results: We analyze 84 start-up cases and identify 16 goals, 9 challenges, and 16 engineering practices that are common among startups. We have mapped these goals, challenges, and practices to start-up life-cycle stages (inception, stabilization, growth, and maturity). Thus, creating the progression model guiding software engineering efforts in start-ups. Conclusions: We conclude that start-ups to a large extent face the same challenges and use the same practices as established companies. However, the primary software engineering challenge in start-ups is to evolve multiple process areas at once, with a little margin for serious errors.

show abstract

Section: Methodsmentioning

confidence: 99%

“…The main advantages of the case survey method are its ability to collect richer information than conventional survey, and extendibility to study more cases. That said, the data collected by a case survey are limited by the scope of the questionnaire instrument [33], [35]. Validity threats of our study are discussed in Section 3.3.…”

Section: Methodsmentioning

confidence: 99%

A Progression Model of Software Engineering Goals, Challenges, and Practices in Start-Ups

Klotins

Unterkalmsteiner

Chatzipetrou

et al. 2021

IIEEE Trans. Software Eng.

Self Cite

View full text Add to dashboard Cite

show abstract

“…Surveys are an obvious method to conduct such breadth search and breadth selection. A research approach that combines case study and survey study is already available: the case survey, for example . We are developing a variant of the case‐survey methodology intended specifically for blog‐like documents.…”

Section: Directions For Further Researchmentioning

confidence: 99%

Using blog‐like documents to investigate software practice: Benefits, challenges, and research directions

Rainer

Williams

2019

J Software Evolu Process

View full text Add to dashboard Cite

Background An emerging body of research is using grey literature to investigate software practice. One frequently occurring type of grey literature is the blog post. Whilst there are prospective benefits to using grey literature and blog posts to investigate software practice, there are also concerns about the quality of such material.Objectives To identify and describe the benefits and challenges to using blog-like content to investigate software practice, and to scope directions for further research. MethodsWe conduct a review of previous research, mainly within software engineering, to identify benefits, challenges, and directions and use that review to complement our experiences of using blog posts in research. Results and ConclusionWe identify and organise benefits and challenges of using blog-like documents in software engineering research. We develop a definition of the type of blog-like document that should be of (more) value to software engineering researchers. We identify and scope several directions in which to progress research into and with blog-like documents.We discuss similarities and differences in secondary and primary studies that use blog-like documents and similarities and differences between the use of blog-like documents and the use of already established research methods, eg, interview and survey.

show abstract

“…It uses metrics based on clustering analysis [13]. Recently, a case survey was presented [14] for making the choice among the different component sourcing options like in-house components, COTS, Open Source Software or outsourcing the components. Their results showed that the most of the solutions are deterministic and based on optimization.…”

Section: Related Workmentioning

confidence: 99%

Clustering based Architecture for Software Component Selection

Kaur¹,

Tomar²

2018

IJMECS

View full text Add to dashboard Cite

Abstract-The component-based software engineering (CBSE) consists of component selection, qualification, adaptation, assembly and updating of components according to the requirements. The focus of this paper is software component selection only. Now-a-days many selection processes, techniques and algorithms are proposed for this task. This paper presents generalized software component selection architecture using clustering. The architecture is divided into four tiers namely Component Requirements and Component Selection Tier, Query and Decision Tier, Application logic tier with Clustering and Component Cluster Tier. The architecture offers manifold advantages like i) presenting a generalized architecture where the existing techniques can be applied, reducing the search space for the component selection. ii) It also illustrates the usage of clustering in the software component selection without the need for pre-specification of number of clusters and considering more than two features while clustering.iii)The cluster validation is performed to check the correctness of the clusters. This complete selection process is validated on a representative instance of set of components.

show abstract

Choosing Component Origins for Software Intensive Systems: In-House, COTS, OSS or Outsourcing?—A Case Survey

Abstract: This is the accepted version of a paper published in IEEE Transactions on Software Engineering. This paper has been peer-reviewed but does not include the final publisher proof-corrections or journal pagination.

Cited by 42 publications

References 55 publications

A Progression Model of Software Engineering Goals, Challenges, and Practices in Start-Ups

A Progression Model of Software Engineering Goals, Challenges, and Practices in Start-Ups

Using blog‐like documents to investigate software practice: Benefits, challenges, and research directions

Clustering based Architecture for Software Component Selection

Contact Info

Product

Resources

About