"How do people decide?": A Model for Software Library Selection

TL;DR

This paper addresses how developers choose third-party software libraries by deriving a comprehensive library selection model from 24 global semi-structured interviews using Straussian grounded theory. It identifies six decision patterns that govern library adoption, supported by a rich set of 28 factors, 23 conditions, and eight barriers that shape and constrain these patterns. The study connects library selection to marketing theory, offering five actionable recommendations (e.g., OSPO setup, upgrade ownership, licensing/security cut-offs, inclusive team culture, and learning incentives) and proposes a toolkit concept for automated library comparison. The findings provide both theoretical insight and practical guidance for organizations seeking to formalize and improve their library selection processes, with implications for policy, process design, and tooling in software development.

Abstract

Modern-day software development is often facilitated by the reuse of third-party software libraries. Despite the significant effort to understand the factors contributing to library selection, it is relatively unknown how the libraries are selected and what tools are still needed to support the selection process. Using Straussian grounded theory, we conducted and analyzed the interviews of 24 professionals across the world and derived a model of library selection process which is governed by six selection patterns (i.e., rules). The model draws from marketing theory and lays the groundwork for the development of a library selection tool which captures the technical and non-technical aspects developers consider.

Figures (8)

• Figure 1: Overall research method for developing theoretical model and conceptual tools. Grounded theory is applied from data collection to the model evaluation. The rounded boxes denote the activity and the rectangles denote the outcome.
• Figure 2: Majors steps taken during the library selection process. In every step, there are multiple actions. Each row denotes a step.
• Figure 3: Information sources from where developers collect library-related data, reviews, or opinions.
• Figure 4: Technical and non-technical aspects of libraries considered by developers during library selection
• Figure 5: Six library selection related decision patterns found in the industry. Each selection pattern is presented using the scenario, dev team response, and consequences. The scenario is further explained using the conditions. The dev team response is explained by providing the consideration factors (F), specific sources (S), or special processes (P). The primary actor of each selection pattern is shown under the pattern name in parentheses. Orange boxes show example traces from the interviewees.