Naming the pain in requirements engineering

Méndez, Daniel; Wagner, Stefan; Kalinowski, Marcos; Felderer, Michael; Mafra, P.; Vetrò, Antonio; Conte, Tayana; Christiansson, Marie-Therese; Greer, Des; Lassenius, Casper; Männistö, Tomi; Nayabi, M.; Oivo, Markku; Penzenstadler, Birgit; Pfahl, Dietmar; Prikladnicki, Rafael; Ruhe, Guenther; Schekelmann, André; Sen, Sagar; Spínola, Rodrigo O.; Tuzcu, Ahmed; Vara, José Luis de la; Wieringa, Roel

doi:10.1007/s10664-016-9451-7

Cited by 200 publications

(124 citation statements)

References 30 publications

Supporting

Mentioning

114

Contrasting

Unclassified

Order By: Relevance

“…1 on page 11). The full data set is published in addition as a technical report [29], which we used to inform the participants about the results. We interpreted those results with basic descriptive statistics and reasoning.…”

Section: Previously Published Materialsmentioning

confidence: 99%

Naming the pain in requirements engineering: A design for a global family of surveys and first results from Germany

Fernández

Wagner

2015

Information and Software Technology

View full text Add to dashboard Cite

Context: For many years, we have observed industry struggling in defining a high quality requirements engineering (RE) and researchers trying to understand industrial expectations and problems. Although we are investigating the discipline with a plethora of empirical studies, those studies either concentrate on validating specific methods or on single companies or countries. Therefore, they allow only for limited empirical generalisations. Objective: To lay an empirical and generalisable foundation about the state of the practice in RE, we aim at a series of open and reproducible surveys that allow us to steer future research in a problem-driven manner. Method: We designed a globally distributed family of surveys in joint collaborations with different researchers from different countries. The instrument is based on an initial theory inferred from available studies. As a long-term goal, the survey will be regularly replicated to manifest a clear understanding on the status quo and practical needs in RE. In this paper, we present the design of the family of surveys and first results of its start in Germany. Results: Our first results contain responses from 30 German companies. The results are not yet generalisable, but already indicate several trends and problems. For instance, a commonly stated problem respondents see in their company standards are artefacts being underrepresented, and important problems they experience in their projects are incomplete and inconsistent requirements. Conclusion: The results suggest that the survey design and instrument are well-suited to be replicated and, thereby, to create a generalisable empirical basis of RE in practice.

show abstract

Section: Previously Published Materialsmentioning

confidence: 99%

Naming the pain in requirements engineering: A design for a global family of surveys and first results from Germany

Fernández

Wagner

2015

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…4). These OrdEval results might be surprising since Requirements acquisition is considered one of the basic building blocks of the software development (Kruchten 2009;Maglyas et al 2017) with high importance to software project success (Fernandez et al 2017). The results can be explained by the fact that recently many new requirement acquisition techniques and approaches have been developed (Ernst et al 2014;Lauesen & Kuhail 2012;Lucassen et al 2016;Raspotnig & Opdahl 2013) and are probably perceived as innovations by the CIOs of the studied enterprises.…”

Section: Project Managementmentioning

confidence: 96%

Exploring the Relations Between Net Benefits of IT Projects and CIOs’ Perception of Quality of Software Development Disciplines

2019

View full text Add to dashboard Cite

Software development enterprises are under consistent pressure to improve their management techniques and development processes. These are comprised of several disciplines like requirements acquisition, design, coding, testing, etc. that must be continuously improved and individually tailored to suit specific software development project. This paper presents an evaluation approach that enables the enterprises to increase development process net benefits by improving disciplines' quality and increasing developers' satisfaction. Our approach builds on Kano's model of quality. Based on an empirical study of top 1000 enterprises from Slovenia we find that application of software development methodologies in individual development disciplines significantly relates to net benefits of IT projects. The results show that different types of Kano quality are present in individual disciplines. Enterprises should be cautious when altering must-be quality disciplines like testing or deployment as they can significantly disrupt the established routines, cause great dissatisfaction between developers and significantly reduce benefits. On the other hand, changing the attractive quality disciplines like requirements acquisition can notably increase developers' satisfaction and benefits but is less likely to disrupt the established routines.

show abstract

“…The study will be conducted by invitation only to have a better control over the individual respondents. The strategy to define an invitation list is two-fold, i) requirements engineers, business analysts, and software developers within companies in the NaPiRE network [20] and among our contacts, and ii) software developers sampled from the app stores (e.g., Google Play Store, Apple Store). The latter are especially important to assess Type 0 ReD as they usually have direct access to users through the stores feedback and review functionalities.…”

Section: Future Assessment a Red Concept Preliminary Validationmentioning

confidence: 99%

Towards a Holistic Definition of Requirements Debt

Lenarduzzi

Fucci

2019

2019 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)

View full text Add to dashboard Cite

When not appropriately managed, technical debt is considered to have negative effects to the long term success of software projects. However, how the debt metaphor applies to requirements engineering in general, and to requirements engineering activities in particular, is not well understood. Grounded in the existing literature, we present a holistic definition of requirements debt which includes debt incurred during the identification, formalization, and implementation of requirements. We outline future assessment to validate and further refine our proposed definition. This conceptualization is a first step towards a requirements debt monitoring framework to support stakeholders decisions, such as when to incur and eventually pay back requirements debt, and at what costs.

show abstract

Naming the pain in requirements engineering

Cited by 200 publications

References 30 publications

Naming the pain in requirements engineering: A design for a global family of surveys and first results from Germany

Naming the pain in requirements engineering: A design for a global family of surveys and first results from Germany

Exploring the Relations Between Net Benefits of IT Projects and CIOs’ Perception of Quality of Software Development Disciplines

Towards a Holistic Definition of Requirements Debt

Contact Info

Product

Resources

About