VLDB 2026 Research / reviewers in the wild / expert
Erik Kamsties
dblp:79/1672
· DBLP profile ↗
13ranked-venue papers
4as first author
2since 2021 · last 2025
0000-0002-7373-8466ORCID · corroborated
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 13 · 4 first-author · 2 since 2021Artificial intelligence and machine learning · 1Databases, data management, data science and information retrieval · 1Applied, interdisciplinary, general and emerging computing · 1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | Exploring and Characterizing Ad-Hoc Requirements - A Case Study at a Large-Scale Systems Provider
Andrea Wohlgemuth, Fabiano Dalpiaz, Erik Kamsties |
REFSQ | 3 |
| 2021 | AdaptationExplore - A Process for Elicitation, Negotiation, and Documentation of Adaptive Requirements
Fabian Kneer, Erik Kamsties, Klaus Schmid |
REFSQ | 2 |
| 2019 | Special section: Extended papers from REFSQ 2018
Erik Kamsties, Jennifer Horkoff |
Inf. Softw. Technol. | 1 |
| 2017 | Do Words Make a Difference? An Empirical Study on the Impact of Taxonomies on the Classification of RequirementsabstractRequirements taxonomies help to classify and channel the requirements in a project. A very simple taxonomy is the distinction between functional and non-functional requirements. Furthermore, a taxonomy helps to decide if a statement is a requirement at all or just something else (e.g., 'information'). The quality of a taxonomy is important as we do not want to put a statement in the wrong category.In this paper, we argue that we need to take cognitive psychology into account in this task of requirements classification. Cognitive psychology focuses on the abilities and limitations of the human mind. We present a controlled experiment and a replication in which we compare three requirements taxonomies.The participants had to evaluate a set of requirements based on the given taxonomies. The results of these experiments show that there are differences between the taxonomies: Interestingly, the question whether a statement is identified as a requirement or not depends on the taxonomy. These experiments present initial results, we assume that these results are related to phenomena of cognitive psychology.We conclude that the wording should be carefully taken into account in the definition of the categories of a high quality requirements taxonomy. Kim Lauenroth, Erik Kamsties, Oliver Hehlert |
RE | 2 |
| 2017 | The Impact of Specification Structure on Human Memory Performance - Experiences from a First Experiment
Kim Lauenroth, Erik Kamsties, Tim Pfeiffer |
REFSQ | 2 |
| 2016 | People's Capabilities are a Blind Spot in RE Research and Practice
Kim Lauenroth, Erik Kamsties |
REFSQ | 2 |
| 2014 | Feedback-Aware Requirements Documents for Smart Devices
Erik Kamsties, Fabian Kneer, Markus Völter, Burkhard Igel, Bernd Kolb |
REFSQ | 1 |
| 2008 | Editors' Introduction
Vincenzo Gervasi, Peter Sawyer, Barbara Paech, Erik Kamsties |
Inf. Softw. Technol. | 4 |
| 2005 | Model-Based System Testing of Software Product Families
Andreas Reuys, Erik Kamsties, Klaus Pohl, Sacha Reis |
CAiSE | 2 |
| 2005 | Guest editorial: 10th anniversary workshop on Requirements Engineering: Foundation for Software Quality (REFSQ'2004)
Björn Regnell, Erik Kamsties, Vincenzo Gervasi |
Requir. Eng. | 2 |
| 2004 | Software Product Family Evaluation
Frank van der Linden 0001, Jan Bosch, Erik Kamsties, Kari Känsälä, J. Henk Obbink |
SPLC | 3 |
| 2003 | A controlled experiment to evaluate how styles affect the understandability of requirements specifications
Erik Kamsties, Antje von Knethen, Ralf Reussner |
Inf. Softw. Technol. | 1 |
| 1998 | Requirements engineering in small and medium enterprises
Erik Kamsties, Klaus A. Hörmann, Maud Schlich |
Requir. Eng. | 1 |