Demo Data from EDBT 2026 / reviewers in the wild / expert
Chris Feulner
dblp:78/2390
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 1994
—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 |
Software maintenance and evolution · 100% | |
| Human-computer interaction and pervasive computing
1 paper |
Collaborative and social computing · 100% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software maintenance and evolution
software inspection |
0.0 | 1 | 1994 | CAIS: Collaborative Asynchronous Inspection of Software · SIGSOFT FSE 1994 |
Collaborative and social computing
computer-supported cooperative work |
0.0 | 1 | 1994 | CAIS: Collaborative Asynchronous Inspection of Software · SIGSOFT FSE 1994 |
Collaborative and social computing › computer-supported cooperative work
distributed collaboration |
0.0 | 1 | 1994 | CAIS: Collaborative Asynchronous Inspection of Software · SIGSOFT FSE 1994 |
Methods — techniques the papers use, named apart from their topics
pilot study · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1994 | CAIS: Collaborative Asynchronous Inspection of SoftwareabstractMany software engineering tasks have a synchronous component that requires the participants to assemble together at the same time and place. This approach is expensive in terms of traveling, scheduling and human resources. Existing computer tools mitigate these constraints by adding structure to the meeting, providing on-line document support, and distributing the participants over geographic boundaries. The constraint remains, however, that all participants participate at the same timeWe propose relaxing the time constraint in software engineering tasks to resolve issues non-concurrently, in effect reducing (and in some cases eliminating) the need for the synchronous meeting. We hypothesize that support for asynchrony will enable software engineering teams to work together as effectively in different times as in same time.We have chosen software inspection as our candidate software engineering task because it is well-understood, highly-structured, and widely-practiced. We have designed and developed a Collaborative Asynchronous Inspection of Software (CAIS) meeting prototype that supports the meeting part of inspection. CAIS allows participants to effectively "meet" even when separated by time zones and working schedules. We have conducted a pilot study comparing the manual and CAIS meetings and present our results and lessons learned. Vahid Mashayekhi, Chris Feulner, John Riedl |
SIGSOFT FSE | 2 |