EDBT 2026 Demo / reviewers in the wild / expert
Tudor Antoniu
dblp:99/2209
· DBLP profile ↗
2ranked-venue papers
1as first author
0since 2021 · last 2004
—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
2 papers |
Program analysis · 38% Software testing · 26% Programming languages and type systems · 26% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Program analysis
static analysis |
0.1 | 2 | 2004 | Validating the Unit Correctness of Spreadsheet Programs · ICSE 2004 A Type System for Statically Detecting Spreadsheet Errors · ASE 2003 |
Software testing › fault detection
spreadsheet error detection |
0.0 | 1 | 2003 | A Type System for Statically Detecting Spreadsheet Errors · ASE 2003 |
Programming languages and type systems
type systems |
0.0 | 1 | 2003 | A Type System for Statically Detecting Spreadsheet Errors · ASE 2003 |
Debugging and program repair › fault localization
spreadsheet debugging |
0.0 | 1 | 2004 | Validating the Unit Correctness of Spreadsheet Programs · ICSE 2004 |
Methods — techniques the papers use, named apart from their topics
unit checking · 0.0static analysis · 0.0unit inference · 0.0type checking · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2004 | Validating the Unit Correctness of Spreadsheet ProgramsabstractFinancial companies, engineering firms and even scientists create increasingly larger spreadsheets and spreadsheet programs. The creators of large spreadsheets make errors and must track them down. One common class of errors concerns unit errors, because spreadsheets often employ formulas with physical or monetary units. In this paper, we describe XeLda, our tool for unit checking Excel spreadsheets. The tool highlights cells if their formulas process values with incorrect units and if derived units clash with unit annotations. In addition, it draws arrows to the sources of the formulas for debugging. The tool is sensitive to many of the intricacies of Excel spreadsheets including tables, matrices, and even circular references. Using XeLda, we have detected errors in some published scientific spreadsheets. Tudor Antoniu, Paul A. Steckler, Shriram Krishnamurthi, Erich Neuwirth, Matthias Felleisen |
ICSE | 1 |
| 2003 | A Type System for Statically Detecting Spreadsheet ErrorsabstractWe describe a methodology for detecting user errors in spreadsheets, using the notion of units as our basic elements of checking. We define the concept of a header and discuss two types of relationships between headers, namely is-a and has-a relationships. With these, we develop a set of rules to assign units to cells in the spreadsheet. We check for errors by ensuring that every cell has a well-formed unit. We describe an implementation of the system that allows the user to check Microsoft Excel spreadsheets. We have run our system on practical examples, and even found errors in published spreadsheets. Yanif Ahmad, Tudor Antoniu, Sharon Goldwater, Shriram Krishnamurthi |
ASE | 2 |