Demo Data from EDBT 2026 / reviewers in the wild / expert
Roope Kylmäkoski
dblp:45/1228
· DBLP profile ↗
2ranked-venue papers
1as 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 · 2 · 1 first-author
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 |
Software maintenance and evolution · 100% | |
| Human-computer interaction and pervasive computing
1 paper |
Collaborative and social computing · 100% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software maintenance and evolution
software documentation |
0.0 | 1 | 2003 | Efficient Authoring of Software Documentation Using RaPiD7 · ICSE 2003 |
Collaborative and social computing
team collaboration |
0.0 | 1 | 2003 | Efficient Authoring of Software Documentation Using RaPiD7 · ICSE 2003 |
Methods — techniques the papers use, named apart from their topics
rapid7 · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2005 | Comprehensive Documentation Made Agile - Experiments with RaPiD7 in Philips
Ko Dooms, Roope Kylmäkoski |
PROFES | 2 |
| 2003 | Efficient Authoring of Software Documentation Using RaPiD7abstractThis paper presents a method developed in Nokia, for efficient document authoring in software development projects. The method is called RaPiD7 (Rapid Production of Documentation, 7 steps). The method improves the traditional approach for document authoring in which the work is typically started by informal initiative, and the actual writing of a document is a task performed by a single individual. Traditional document authoring usually relies on inspections to verify the quality of the documentation. RaPiD7 addresses the document authoring problem by getting people involved in the documentation work earlier as a team in order to guarantee quality, calendar time efficiency, commitment and improved communication. This paper also compares RaPiD7 with some other similar approaches and presents results from a large-scale experiment with RaPiD7. Roope Kylmäkoski |
ICSE | 1 |