Demo Data from EDBT 2026 / reviewers in the wild / expert
Thomas Kiesgen
dblp:03/5469
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2005
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1
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
1 paper |
Requirements engineering and software design · 77% Software maintenance and evolution · 23% |
Topics — the 2 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design
software product lines |
0.1 | 1 | 2005 | Five years of product line engineering in a small company · ICSE 2005 |
Software maintenance and evolution
software process improvement |
0.0 | 1 | 2005 | Five years of product line engineering in a small company · ICSE 2005 |
Methods — techniques the papers use, named apart from their topics
case study · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2005 | Five years of product line engineering in a small companyabstractIn 1999, a new team at MARKET MAKER Software AG began to develop a software product line for managing and displaying stock market data and financial market news. The basic idea was to use web technology in all applications for delivering services to customers. It soon turned out that the company had to change both the processes and the organization. This report summarizes the changes made and the lessons learned over the past five years, when the product line idea was introduced into a small company which faced the pressure to quickly market the first product line instances. Martin Verlage, Thomas Kiesgen |
ICSE | 2 |