Most application code evolves incrementally, and especially so when being maintained after
the applications have been deployed. Yet, most data-flow analyses do not take advantage of …

Incremental static analyses provide up-to-date analysis results in time proportional to the
size of a code change, not the entire code base. This promises fast feedback to …

Dependencies between program elements need to be modeled from different perspectives
reflecting architectural, design, and implementation level decisions. To avoid erosion of the …

Program analyses detect errors in code, but when code changes frequently as in an IDE,
repeated re-analysis from-scratch is unnecessary: It leads to poor performance unless we …

Instead of repeatedly re-analyzing from scratch, an incremental static analysis only analyzes
a codebase once completely, and then it updates the previous results based on the code …

These notes are an introduction to. QL, an object-oriented query language for any type of
structured data. We illustrate the use of. QL in assessing software quality, namely to find …

Implementations of static analyses are usually tailored toward a single goal to be efficient,
hampering reusability and adaptability of the components of an analysis. To solve these …

Static checker frameworks support software developers by automatically discovering bugs
that fit general-purpose bug patterns. These frameworks ship with hundreds of detectors for …

An incremental computation updates its result based on a change to its input, which is often
an order of magnitude faster than a recomputation from scratch. In particular …

Context-sensitive global analysis of large code bases can be expensive, which can make its
use impractical during software development. However, there are many situations in which …