EDBT 2026 Demo / reviewers in the wild / expert
Omkar Pendse
dblp:87/3164
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2003
—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 · 30% Debugging and program repair · 30% Empirical software engineering · 30% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Debugging and program repair › automated debugging
assertion-based debugging |
0.0 | 1 | 2003 | End-User Software Engineering with Assertions in the Spreadsheet Paradigm · ICSE 2003 |
Empirical software engineering
developer studies |
0.0 | 1 | 2003 | End-User Software Engineering with Assertions in the Spreadsheet Paradigm · ICSE 2003 |
Requirements engineering and software design
end-user software engineering |
0.0 | 1 | 2003 | End-User Software Engineering with Assertions in the Spreadsheet Paradigm · ICSE 2003 |
Program verification
assertions |
0.0 | 1 | 2003 | End-User Software Engineering with Assertions in the Spreadsheet Paradigm · ICSE 2003 |
Methods — techniques the papers use, named apart from their topics
controlled experiment · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2003 | End-User Software Engineering with Assertions in the Spreadsheet ParadigmabstractThere has been little research on end-user program development beyond the activity of programming. Devising ways to address additional activities related to end-user program development may be critical, however, because research shows that a large proportion of the programs written by end users contain faults. Toward this end, we have been working on ways to provide formal "software engineering" methodologies to end-user programmers. This paper describes an approach we have developed for supporting assertions in end-user software, focusing on the spreadsheet paradigm. We also report the results of a controlled experiment, with 59 end-user subjects, to investigate the usefulness of this approach. Our results show that the end users were able to use the assertions to reason about their spreadsheets, and that doing so was tied to both greater correctness and greater efficiency. Margaret M. Burnett, Curtis R. Cook, Omkar Pendse, Gregg Rothermel, Jay Summet, Christine Wallace |
ICSE | 3 |