C
Christian Schallhart
Researcher at University of Oxford
Publications - 78
Citations - 3271
Christian Schallhart is an academic researcher from University of Oxford. The author has contributed to research in topics: Model checking & Test suite. The author has an hindex of 22, co-authored 78 publications receiving 2993 citations. Previous affiliations of Christian Schallhart include Technische Universität Darmstadt & Technische Universität München.
Papers
More filters
Book ChapterDOI
How the minotaur turned into ariadne: ontologies in web data extraction
TL;DR: First results from the DIADEM project illustrate that high quality, fully automated data extraction at a web scale is possible, if the authors combine domain ontologies with a phenomenology describing the representation of domain concepts.
Book ChapterDOI
Proving reachability using FSHELL
TL;DR: FShell as discussed by the authors is an automated white-box test-input generator for C programs, computing test data with respect to user-specified code coverage criteria, and using bounded model checking to solve the reachability problem posed in SV-COMP.
Journal ArticleDOI
Don’t care in SMT: building flexible yet efficient abstraction/refinement solvers
TL;DR: This paper describes a method for combining “off-the-shelf” SAT and constraint solvers for building an efficient Satisfiability Modulo Theories (SMT) solver for a wide range of theories and shows that it results in considerably smaller and less complex constraint problems.
Book ChapterDOI
New challenges in the development of critical embedded systems: an aeromotive perspective
TL;DR: The automotive and avionics domains are prominent examples of classical engineering disciplines where conflicts between costs, short product cycles and legal requirements concerning dependability, robustness, security, carbon footprint and spatial demands have become a pressing problem.
Posted Content
Verification Across Intellectual Property Boundaries
TL;DR: In this paper, the authors present a protocol in which a dedicated server (called the "amanat") is controlled by both parties: the customer controls the verification task performed by the amanat, while the supplier controls the communication channels of the AMANAT to ensure that the amANat does not leak information about the source code.