The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
An anatomy of requirements engineering in software startups using multi-vocal literature and case survey
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
Within startups, an early version of the final product is often used to validate product ideas with users, e.g. by demonstrating mock-ups to customers, as a cost-effective way to obtain market feedback.
“Within startups, an early version of the final product is often used to validate product ideas with users (Alves et al. 2020;Tripathi et al. 2018), e.g. by demonstrating mock-ups to customers, as a cost-effective way to obtain market feedback.”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Tripathi et al. 2018
Citations
Cites
Garousi, V., Felderer, M., & Mäntylä, M. V. (2016) · Proceedings of the 20th International Conference on Evaluation and Assessment in Software Engineering · doi:10.1145/2915970.2916008 · Cited by 210
Flagged first, then by citations
Research works printed but not linked: 22
- Achimugu, 2014, A systematic literature review of software requirements prioritization research, Inf. Softw. Technol., 56, 568, 10.1016/j.infsof.2014.02.001 · DOI
- Alves, 2010, Requirements engineering for software product lines: a systematic literature review, Inf. Softw. Technol., 52, 806, 10.1016/j.infsof.2010.03.014 · DOI
- Babar, 2014, Systematic reviews in requirements engineering: a systematic review, 43
- Bajwa, 2017, “Failures” to be celebrated: an analysis of major pivots of software startups, Empir. Softw. Eng., 22, 2373, 10.1007/s10664-016-9458-0 · DOI
- Coleman, 2008, An investigation into software development process formation in software start-ups, J. Enterp. Inf. Manag., 21, 633, 10.1108/17410390810911221 · DOI
- Easterbrook, S., Singer, J., Storey, M.-A., Damian, D., 2008. Selecting empirical methods for software engineering research. In: Guide to Advanced Empirical Software Engineering, 285–311. · DOI · Paper page
- Fagerholm, 2017, The right model for continuous experimentation, J. Syst. Softw., 123, 292, 10.1016/j.jss.2016.03.034 · DOI
- Giardino, 2016, Software development in startup companies: the greenfield startup model, IEEE Trans. Softw. Eng., 42, 585, 10.1109/TSE.2015.2509970 · DOI
- Holl, 2012, A systematic review and an expert survey on capabilities supporting multi product lines, Inf. Softw. Technol., 54, 828, 10.1016/j.infsof.2012.02.002 · DOI
- Kane, T. J., 2010. The Importance of Startups in Job Creation and Job Destruction. doi:10.2139/ssrn.1646934. · DOI
- Klotins, 2018, Software engineering in start-up companies: an analysis of 88 experience reports, Empir. Softw. Eng., 1
- Large, 2005, Best marketing and sales practices for technology start-ups: a review and fresh evidence, 1, 339
- Larsson, 1993, Case survey methodology: quantitative analysis of patterns across case studies, Acad. Manag. J., 36, 1515, 10.2307/256820 · DOI
- Marion, 2009, New product development practice application to an early-stage firm: the case of the paperpro® stackmaster™, Des. Studies, 30, 561, 10.1016/j.destud.2009.02.001 · DOI
- Melegati, J., Goldman, A., Paulo, S., 2016. Requirements engineering in software startups: a grounded theory approach. In: Proceedings of the 2nd International Startups Workshop on Software StartupsTrondheim, Norway. · DOI
- Pacheco, 2012, A systematic literature review of stakeholder identification methods in requirements elicitation, J. Syst. Softw., 85, 2171, 10.1016/j.jss.2012.04.075 · DOI
- Paternoster, 2014, Software development in startup companies: a systematic mapping study, Inf. Softw. Technol., 56, 1200, 10.1016/j.infsof.2014.04.014 · DOI · Paper page
- Rabiser, 2010, Requirements for product derivation support: results from a systematic literature review and an expert survey, Inf. Softw. Technol., 52, 324, 10.1016/j.infsof.2009.11.001 · DOI
- Runeson, 2009, Guidelines for conducting and reporting case study research in software engineering, Empir. Softw. Eng., 14, 131, 10.1007/s10664-008-9102-8 · DOI · Paper page
- Tripathi, 2016, Exploring processes in small software companies: a systematic review, 150
- Verner, 2007, State of the practice: an exploratory analysis of schedule estimation and software project success prediction, Inf. Softw. Technol., 49, 181, 10.1016/j.infsof.2006.05.001 · DOI
- Wieringa, 2006, Requirements engineering paper classification and evaluation criteria: a proposal and a discussion, Requir. Eng., 11, 102, 10.1007/s00766-005-0021-6 · DOI · Paper page
Cited by
Sorted by citations
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
Metadata
- Authors
- Tripathi, N., Klotins, E., Prikladnicki, R., Oivo, M., Pompermaier, L. B., Kudakacheril, A. S., Unterkalmsteiner, M., Liukkunen, K., & Gorschek, T.
- Affiliations
- University of Oulu (FI)
- Blekinge Institute of Technology (SE)
- Pontifícia Universidade Católica do Rio Grande do Sul (BR)
- Corresponding author
- Tripathi, Nirnaya
- ORCID
- Venue
- Journal of Systems and Software
- Publisher
- Elsevier BV
- Published
- 2018-12
- Volume
- 146
- Pages
- 130-151
- ISSN
- 0164-1212 (ISSN-L)
- OpenAlex
- W2888929421
- Cited by
- 55
- References
- 1
- Citations by year
- 2026: 3 · 2025: 7 · 2024: 8 · 2023: 5 · 2022: 6 · 2021: 11 · 2020: 8 · 2019: 6 · 2018: 1
- FWCI
- 7.25
- Type
- journal article
- Language
- en
- Open access
- closed
- Locations
- Journal of Systems and Software (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
- Physical Sciences › Engineering › Control and Systems Engineering › Systems Engineering Methodologies and Applications
- Keywords
- requirements engineering, software startups, requirements analysis, requirements documentation, requirements prioritization, requirements validation
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