Requirements Elicitation Techniques Applied in Software Startups

Rafiq, Usman; Bajwa, Sohaib Shahid; Lunesu, Maria Ilaria

doi:10.1109/seaa.2017.73

Cited by 26 publications

(13 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Among other topics, engineering practices in start-ups is identified as an important research area. Rafiq and et al (2017) and Melegati et al (2016) have studied requirements engineering practices in start-ups and provide an insight into how product ideas evolve and what practices are used to connect founders' vision with customer needs.…”

Section: Introductionmentioning

confidence: 99%

Software engineering in start-up companies: An analysis of 88 experience reports

2018

View full text Add to dashboard Cite

Context Start-up companies have become an important supplier of innovation and softwareintensive products. The flexibility and reactiveness of start-ups enables fast development and launch of innovative products. However, a majority of software start-up companies fail before achieving any success. Among other factors, poor software engineering could be a significant contributor to the challenges experienced by start-ups. However, the state-ofpractice of software engineering in start-ups, as well as the utilization of state-of-the-art is largely an unexplored area. Objective In this study we investigate how software engineering is applied in start-up context with a focus to identify key knowledge areas and opportunities for further research. Method We perform a multi-vocal exploratory study of 88 start-up experience reports. We develop a custom taxonomy to categorize the reported software engineering practices and their interrelation with business aspects, and apply qualitative data analysis to explore influences and dependencies between the knowledge areas. Results We identify the most frequently reported software engineering (requirements engineering, software design and quality) and business aspect (vision and strategy development) knowledge areas, and illustrate their relationships. We also present a summary of how relevant software engineering knowledge areas are implemented in start-ups and identify potentially useful practices for adoption in start-ups. Conclusions The results enable a more focused research on engineering practices in startups. We conclude that most engineering challenges in start-ups stem from inadequacies in requirements engineering. Many promising practices to address specific engineering challenges exists, however more research on adaptation of established practices, and validation of new start-up specific practices is needed.

show abstract

Section: Introductionmentioning

confidence: 99%

Software engineering in start-up companies: An analysis of 88 experience reports

2018

View full text Add to dashboard Cite

show abstract

“…Start-up [19], [35], [36], [68], [70], [74], [78], [79], [81], [84], [98]- [100], [109], [119]- [121] 3…”

Section: B Knowledge Area Characteristics and Frameworkmentioning

confidence: 99%

“…Unfortunately, they are not utilised and this will affect the basic understanding of applying them, knowing the challenges, what should be improved and hence the development of tools to support the processes. This, therefore, calls for efforts to factor investigating these knowledge areas deliberately and the practice in the corresponding practice to generate useful insights after all literature reveals that processes like requirements [19], [36], [131] and software testing [123], [132] are responsible for lots of challenges of software development process in practice of the SSCs. It would still be interesting to know if perhaps the practitioner's skill set is responsible for this maybe because of choice the practitioners tend to skew their skills and practice to other areas other than requirements, software testing and maintenance.…”

Section: A How Has Software Practice In Small Software Companies Utilised the Software Engineering Knowledge Areas In The Iso/iec Tr 1975mentioning

confidence: 99%

“…This leads to the unestablished process that has been existent in software practice, especially for small companies that continuously try to find a fitting in vain as eluded to by [23], [34]. This has led to the development of several tools to streamline processes suggested by different researchers, for example, [19], [35], [36] for requirements and for [37], [38] project management. Solutions for process adoption are fragmented in the different empirical literature on software processes and hence the need to consolidate and integrate the fragmented findings for comprehensive theory development in software processes adoption for SSCs.…”

Section: Introductionmentioning

confidence: 99%

“…SME [56], [57], [63], [66], [76], [85], [86], [93]- [95], [104], [105], [108], [110], [118], [123], [124] (c) Framework/standards 1 None [19], [23], [32], [35], [36], [63], [66], [68], [70], [78], [81], [83]- [87], [93], [94], [96]- [102], [104], [109], [118]…”

mentioning

confidence: 99%

See 2 more Smart Citations

Software Engineering in Small Software Companies: Consolidating and Integrating Empirical Literature Into a Process Tool Adoption Framework

Tuape¹,

Hasheela-Mufeti

Kayanda

et al. 2021

IEEE Access

View full text Add to dashboard Cite

Small software companies face numerous challenges of complexity, unstructured software development processes and scarce resources. This notwithstanding, the companies have dominated the software market by 80 percent. The practice and products of these companies are still persistently marred by quality issues arising from the processes, with evidence indicating that process tools do not fit the unique contexts in which they operate. Significant strides have been made in transforming software development practice; however, the challenges are still evidently apparent. Hence the need to establish how knowledge areas are applied in process practice, understand the context of software development and its implication in practice, how process tools are utilised in practice and evaluate quality of research in software literature The researchers undertook a systematic mapping study to determine the state of practice in empirical literature on software engineering of SSCs by examining and classifying 1096 publications. Other than the finding that research quality was low and affecting generalisation and transferability, the results also revealed interesting findings which we finally consolidated and integrated to develop two contributions (i) a software development process adoption theoretical framework which provides new insights of understanding software development and (ii) a 3-point guideline for research quality.

show abstract

Lessons Learned from Applying Requirements and Design Techniques in the Development of a Machine Learning System for Predicting Lawsuits Against Power Companies

Rivero

Portela

Boaro

et al. 2021

Human Interface and the Management of Information. Information Presentation and Visualization

View full text Add to dashboard Cite

Requirements Elicitation Techniques Applied in Software Startups

Cited by 26 publications

References 10 publications

Software engineering in start-up companies: An analysis of 88 experience reports

Software engineering in start-up companies: An analysis of 88 experience reports

Software Engineering in Small Software Companies: Consolidating and Integrating Empirical Literature Into a Process Tool Adoption Framework

Lessons Learned from Applying Requirements and Design Techniques in the Development of a Machine Learning System for Predicting Lawsuits Against Power Companies

Contact Info

Product

Resources

About