Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
An anatomy of requirements engineering in software startups using multi-vocal literature and case survey
Oulun Yliopisto, M3S Research Group, FIN.
Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.ORCID iD: 0000-0002-1987-2234
Pontificia Universidade Catolica do Rio Grande do Sul, BRA.
Oulun Yliopisto, M3S Research Group, FIN.
Show others and affiliations
2018 (English)In: Journal of Systems and Software, ISSN 0164-1212, E-ISSN 1873-1228, Vol. 146, p. 130-151Article in journal (Refereed) Published
Abstract [en]

Context: Software startups aim to develop innovative products, grow rapidly, and thus become important in the development of economy and jobs. Requirements engineering (RE) is a key process area in software development, but its effects on software startups are unclear. Objective: The main objective of this study was to explore how RE (elicitation, documentation, prioritization and validation) is used in software startups. Method: A multi-vocal literature review (MLR) was used to find scientific and gray literature. In addition, a case survey was employed to gather empirical data to reach this study's objective. Results: In the MLR, 36 primary articles were selected out of 28,643 articles. In the case survey, 80 respondents provided information about software startup cases across the globe. Data analysis revealed that during RE processes, internal sources (e.g., for source), analyses of similar products (e.g., elicitation), uses of informal notes (e.g., for documentation), values to customers, products and stakeholders (e.g., for prioritization) and internal reviews/prototypes (e.g., for validation) were the most used techniques. Conclusion: After an analysis of primary literature, it was concluded that research on this topic is still in early stages and more systematic research is needed. Furthermore, few topics were suggested for future research. © 2018 Elsevier Inc.

Place, publisher, year, edition, pages
Elsevier Inc. , 2018. Vol. 146, p. 130-151
Keywords [en]
Case survey, Multi-vocal literature review, Requirements engineering, Software startups, Software design, Case surveys, Empirical data, Innovative product, Internal source, Key process areas, Literature reviews, Prioritization, Systematic research, Surveys
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-17083DOI: 10.1016/j.jss.2018.08.059ISI: 000451488900010Scopus ID: 2-s2.0-85053782208OAI: oai:DiVA.org:bth-17083DiVA, id: diva2:1253595
Available from: 2018-10-05 Created: 2018-10-05 Last updated: 2021-05-24Bibliographically approved

Open Access in DiVA

No full text in DiVA

Other links

Publisher's full textScopus

Authority records

Klotins, EriksUnterkalmsteiner, MichaelGorschek, Tony

Search in DiVA

By author/editor
Klotins, EriksUnterkalmsteiner, MichaelGorschek, Tony
By organisation
Department of Software Engineering
In the same journal
Journal of Systems and Software
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar

doi
urn-nbn

Altmetric score

doi
urn-nbn
Total: 350 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf