Demo Data from EDBT 2026 / reviewers in the wild / expert
J. Michael Lake
dblp:51/2107
· DBLP profile ↗
2ranked-venue papers
1as first author
0since 2021 · last 2007
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1Databases, data management, data science and information retrieval · 1 · 1 first-authorGraphics, computer vision, multimedia, augmented reality and games · 1 · 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 |
Program analysis · 44% Software testing · 44% Software maintenance and evolution · 13% |
Topics — the 2 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Program analysis
static analysis |
0.1 | 1 | 2007 | Using groupings of static analysis alerts to identify files likely to contain field failures · ESEC/SIGSOFT FSE 2007 |
Software maintenance and evolution › software configuration management › software release management
software release |
0.0 | 1 | 2007 | Using groupings of static analysis alerts to identify files likely to contain field failures · ESEC/SIGSOFT FSE 2007 |
Methods — techniques the papers use, named apart from their topics
singular value decomposition · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2007 | Using groupings of static analysis alerts to identify files likely to contain field failuresabstractIn this paper, we propose a technique for leveraging historical field failure records in conjunction with automated static analysis alerts to determine which alerts or sets of alerts are predictive of a field failure. Our technique uses singular value decomposition to generate groupings of static analysis alert types, which we call alert signatures, that have been historically linked to field failure-prone files in previous releases of a software system. The signatures can be applied to sets of alerts from a current build of a software system. Files that have a matching alert signature are identified as having similar static analysis alert characteristics to files with known field failures in a previous release of the system. We performed a case study involving an industrial software system at IBM and found three distinct alert signatures that could be applied to the system. We found that 50% of the field failures reported since the last static analysis run could be discovered by examining the 10% of the files and static analysis alerts indicated by these three alert signatures. The remaining failures were either not detected by a signature which could be an indication of a new type of error in the field, or they were on areas of the code where no static analysis alerts were detected. Mark Sherriff, Sarah Smith Heckman, J. Michael Lake, Laurie A. Williams |
ESEC/SIGSOFT FSE | 3 |
| 2000 | Prediction by Grammatical MatchabstractWe present prediction by grammatical match (PGM), a new general purpose adaptive text compression framework successfully blending finite-context and general context-free models. A PGM compressor operates incrementally by parsing a prefix of the input text, generating a set of analyses; these analyses are scored according to encoding cost, the cheapest is selected, and sent through an order k PPM encoder. PGM's primary innovations include the use of a generalized PPM in selection and coding; the simultaneous use of multiple context-free grammars; the use of lexical left-corner derivations (LLCD); and an aggressive algorithm for constructing an LR(O) parsable metalanguage for LLCD. LLCD are a hybrid of bottom-up and top-down descriptions that represent grammatical information implicitly with each lexeme. The constructed metalanguage extends this to include explicit top-down steps to resolve local ambiguities in at most one strictly grammatical symbol. These properties combine to deliver excellent compression. On a test corpus of about 1 MB of Scheme program text, PGM with a generic Scheme grammar required about 26% fewer bits than PPM to represent the entire corpus, with reductions on individual files reaching as high as 55%. In addition, PGM enriches the time-compression-memory tradeoff options, since a low order PGM can achieve bpc rates comparable to high order PPM at considerable savings in space. PGM compression operates in expected linear time and space for many kinds of grammars. PGM decompression operates in guaranteed linear time and space. J. Michael Lake |
Data Compression Conference | 1 |