Demo Data from SIGIR 2026 / reviewers in the wild / expert
Detlef Kips
dblp:75/6049
· DBLP profile ↗
4ranked-venue papers
0as first author
0since 2021 · last 2016
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 4
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
2 papers |
Software maintenance and evolution · 62% Empirical software engineering · 38% |
Topics — the 5 heaviest of 6, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Empirical software engineering › collaborative software development
inner source |
0.2 | 1 | 2016 | Inner Source in Platform-Based Product Engineering · IEEE Trans. Software Eng. 2016 |
Software maintenance and evolution
software ecosystems |
0.2 | 1 | 2016 | Inner Source in Platform-Based Product Engineering · IEEE Trans. Software Eng. 2016 |
Software maintenance and evolution
software reuse |
0.2 | 1 | 2016 | Inner Source in Platform-Based Product Engineering · IEEE Trans. Software Eng. 2016 |
Software maintenance and evolution › software configuration management
consistency management |
0.0 | 1 | 1996 | A New Approach to Consistency Control in Software Engineering · ICSE 1996 |
Software maintenance and evolution
software configuration management |
0.0 | 1 | 1996 | A New Approach to Consistency Control in Software Engineering · ICSE 1996 |
Methods — techniques the papers use, named apart from their topics
multiple-case case study · 0.2
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2016 | Inner Source in Platform-Based Product EngineeringabstractInner source is an approach to collaboration across intra-organizational boundaries for the creation of shared reusable assets. Prior project reports on inner source suggest improved code reuse and better knowledge sharing. Using a multiple-case case study research approach, we analyze the problems that three major software development organizations were facing in their product line engineering efforts. We find that a root cause, the separation of product units as profit centers from a platform organization as a cost center, leads to delayed deliveries, increased defect rates, and redundant software components. All three organizations assume that inner source can help solve these problems. The article analyzes the expectations that these companies were having towards inner source and the problems they were experiencing in its adoption. Finally, the article presents our conclusions on how these organizations should adapt their existing engineering efforts. Dirk Riehle, Maximilian Capraro, Detlef Kips, Lars Horn |
IEEE Trans. Software Eng. | 3 |
| 2011 | A FUML-Based Distributed Execution Machine for Enacting Software Process Models
Ralf Ellner, Samir Al-Hilank, Johannes Drexler, Martin Jung 0006, Detlef Kips, Michael Philippsen |
ECMFA | 5 |
| 2010 | eSPEM - A SPEM Extension for Enactable Behavior Modeling
Ralf Ellner, Samir Al-Hilank, Johannes Drexler, Martin Jung 0006, Detlef Kips, Michael Philippsen |
ECMFA | 5 |
| 1996 | A New Approach to Consistency Control in Software Engineering
Georg Heidenreich, Mark Minas, Detlef Kips |
ICSE | 3 |