Software startup engineering: A systematic mapping study
Open accessThe DOI matches its Crossref record; 9 of the 9 references it cites were found in a registry or an index.
Abstract
Abstract Software startups have long been a significant driver in economic growth and innovation. The on-going failure of the major number of startups calls for a better understanding of state-of-the-practice of startup activities. Objective With a focus on engineering perspective, this study aims at identifying the change in focus of research area and thematic concepts operating startup research. A systematic mapping study on 74 primary papers (in which 27 papers are newly selected) from 1994 to 2017 was conducted with a comparison with findings from previous mapping studies. A classification schema was developed, and the primary studies were ranked according to their rigour. We discovered that most research has been conducted within the SWEBOK knowledge areas software engineering process, management, construction, design, and requirements, with the shift of focus towards process and management areas. We also provide an alternative classification for future startup research. We find that the rigour of the primary papers was assessed to be higher between 2013–2017 than that of 1994–2013. We also find an inconsistency of characterizing startups. Future work can focus on certain research themes, such as startup evolution models and human aspects, and consolidate the thematic concepts describing software startups.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Wohlin, C. (2014) · Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering · doi:10.1145/2601248.2601268 · Cited by 4,234 · cited 4×
“using the forward snowballing technique [42], to identify additional papers not discovered by the search string.”
BackgroundMethodInfluentialSystematic Mapping Studies in Software Engineering
Petersen, K., Feldt, R., Mujtaba, S., & Mattsson, M. (2008) · Electronic Workshops in Computing · doi:10.14236/ewic/ease2008.8 · Cited by 3,239 · cited 4×
“process for systematic mapping studies, as illustrated in figure 1 [41].”
BackgroundMethodInfluentialSoftware development in startup companies: A systematic mapping study
Paternoster, N., Giardino, C., Unterkalmsteiner, M., Gorschek, T., & Abrahamsson, P. (2014) · Information and Software Technology · doi:10.1016/j.infsof.2014.04.014 · Cited by 451 · cited 10×
“The chosen attributes were inspired by previous mapping studies discovered during the data collection process (Paternoster et al., 2014; Klotins et al., 2015; Tripathi et al., 2016), and from the process of finding keywords in the abstracts of the retrieved papers (Petersen et al.”
BackgroundMethodResultInfluentialManaging technical debt in software-reliant systems
Brown, N., Cai, Y., Guo, Y., Kazman, R., Kim, M., Kruchten, P., Lim, E., MacCormack, A., Nord, R., Ozkaya, I., et al. (2010) · Proceedings of the FSE/SDP workshop on Future of software engineering research · doi:10.1145/1882362.1882373 · Cited by 432
What Do We Know about Software Development in Startups?
Giardino, C., Unterkalmsteiner, M., Paternoster, N., Gorschek, T., & Abrahamsson, P. (2014) · IEEE Software · doi:10.1109/ms.2014.129 · Cited by 223 · cited 3×
“market and technology uncertainty, software startups need effective practices to face those unique challenges [11].”
BackgroundInfluentialColeman, G., & O’Connor, R. (2007) · Information and Software Technology · doi:10.1016/j.infsof.2007.02.011 · Cited by 204
Investigating software process in practice: A grounded theory perspective
Coleman, G., & O’Connor, R. (2008) · Journal of Systems and Software · doi:10.1016/j.jss.2007.07.027 · Cited by 202 · cited 4×
“Since startups have limited resources, focus is often directed towards product development, rather than focusing on the establishment of rigid processes (Coleman and O’Connor, 2008).”
BackgroundInfluentialKey Challenges in Early-Stage Software Startups
Giardino, C., Bajwa, S. S., Wang, X., & Abrahamsson, P. (2015) · Lecture Notes in Business Information Processing · doi:10.1007/978-3-319-18612-2_5 · Cited by 169 · cited 2×
“However, there are also identified unique challenges related to software development and innovation methods [4].”
BackgroundThe Developers Dilemma: Perfect Product Development or Fast Business Validation?
Terho, H., Suonsyrjä, S., & Systä, K. (2016) · Lecture Notes in Computer Science · doi:10.1007/978-3-319-49094-6_42 · Cited by 25 · cited 2×
“(Terho et al., 2016) Advice SW Quality, SW Construction Full Startup Philosophical paper No Springer”
Background
Cited by
An empirically based model of software prototyping: a mapping study and a multi-case study
Bjarnason, E., Lang, F., & Mjöberg, A. (2023) · Empirical Software Engineering · doi:10.1007/s10664-023-10331-w · Cited by 75
“The interview guide is based on the first version of our pro-totyping aspects model (Bjarnason et al. 2021a) and on previous research on software startups (progression model (Klotins et al. 2019), typical characteristics (Berg et al. 2018; Giardino et al. 2015)).”
MethodPrototyping Practices in Software Startups: Initial Case Study Results
Bjarnason, E. (2021) · 2021 IEEE 29th International Requirements Engineering Conference Workshops (REW) · doi:10.1109/rew53955.2021.00038 · Cited by 14
On the Pragmatics of Requirements Engineering Practices in a Startup Ecosystem
Alves, C., Cunha, J., & Araujo, J. (2020) · 2020 IEEE 28th International Requirements Engineering Conference (RE) · doi:10.1109/re48521.2020.00041 · Cited by 10
Kamei, F., Wiese, I., Pinto, G., Ferreira, W., Ribeiro, M., Souza, R., & Soares, S. (2022) · Journal of Software Engineering Research and Development · doi:10.5753/jserd.2022.1897 · Cited by 1
Metadata
- Authors
- Berg, V., Birkeland, J., Nguyen-Duc, A., Pappas, I. O., & Jaccheri, L.
- Venue
- Journal of Systems and Software
- Publisher
- Elsevier BV
- Published
- 2018-10
- Volume
- 144
- Pages
- 255-274
- ISSN
- 0164-1212 (ISSN-L)
- OpenAlex
- W2809034995
- Cited by
- 125
- References
- 9
- FWCI
- 26.92
- Type
- journal article
- Language
- en
- Open access
- green
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.