Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page
Demo Data from VLDB 2026 / reviewers in the wild / expert

Abdullah Ustuner

dblp:63/809 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2006
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 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
Program analysis · 46% Operating systems · 46% Program verification · 7%

Topics — the 5 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Program analysis › error detection
API usage error detection		 0.112006
Thorough static analysis of device drivers · EuroSys 2006
Operating systems › i/o › i/o subsystem
device drivers		 0.112006
Thorough static analysis of device drivers · EuroSys 2006
Operating systems › i/o › i/o subsystem › device drivers
device driver verification		 0.112006
Thorough static analysis of device drivers · EuroSys 2006
Program analysis
static analysis		 0.112006
Thorough static analysis of device drivers · EuroSys 2006
Program verification
model checking		 0.012006
Thorough static analysis of device drivers · EuroSys 2006

Methods — techniques the papers use, named apart from their topics

static analysis engine · 0.1API usage rules · 0.1
YearPublicationVenuePosition
2006 Thorough static analysis of device drivers
abstract
Bugs in kernel-level device drivers cause 85% of the system crashes in the Windows XP operating system [44]. One of the sources of these errors is the complexity of the Windows driver API itself: programmers must master a complex set of rules about how to use the driver API in order to create drivers that are good clients of the kernel. We have built a static analysis engine that finds API usage errors in C programs. The Static Driver Verifier tool (SDV) uses this engine to find kernel API usage errors in a driver. SDV includes models of the OS and the environment of the device driver, and over sixty API usage rules. SDV is intended to be used by driver developers "out of the box." Thus, it has stringent requirements: (1) complete automation with no input from the user; (2) a low rate of false errors. We discuss the techniques used in SDV to meet these requirements, and empirical results from running SDV on over one hundred Windows device drivers.
Thomas Ball 0001, Ella Bounimova, Byron Cook, Vladimir Levin, Jakob Lichtenberg, Con McGarvey, Bohus Ondrusek, Sriram K. Rajamani, Abdullah Ustuner
 EuroSys9