Demo Data from VLDB 2026 / reviewers in the wild / expert
M. Kang
dblp:47/4366
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2001
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 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.
| Theoretical computer science
1 paper |
Automated reasoning and model checking · 100% | |
| Software engineering, system software, and programming languages
1 paper |
Program verification · 100% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Embedded and real-time systems · 100% |
Topics — the 3 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Automated reasoning and model checking
model checking |
0.0 | 1 | 2001 | JMOCHA: A Model Checking Tool that Exploits Design Structure · ICSE 2001 |
Program verification
modular verification |
0.0 | 1 | 2001 | JMOCHA: A Model Checking Tool that Exploits Design Structure · ICSE 2001 |
Embedded and real-time systems › embedded software engineering
embedded software verification |
0.0 | 1 | 2001 | JMOCHA: A Model Checking Tool that Exploits Design Structure · ICSE 2001 |
Methods — techniques the papers use, named apart from their topics
symbolic model checking · 0.1enumerative model checking · 0.1assume-guarantee reasoning · 0.1BDD · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2001 | JMOCHA: A Model Checking Tool that Exploits Design StructureabstractModel checking is a practical tool for automated debugging of embedded software. In model checking, a high-level description of a system is compared against a logical correctness requirement to discover inconsistencies. Since model checking is based on exhaustive state-space exploration and the size of the state space of a design grows exponentially with the size of the description, scalability remains a challenge. We have thus developed techniques for exploiting modular design structure during model checking, and the model checker jMocha (Java MOdel-CHecking Algorithm) is based on this theme. Instead of manipulating unstructured state-transition graphs, it supports the hierarchical modeling framework of reactive modules. jMocha is a growing interactive software environment for specification, simulation and verification, and is intended as a vehicle for the development of new verification algorithms and approaches. It is written in Java and uses native C-code BDD libraries from VIS. jMocha offers: (1) a GUI that looks familiar to Windows/Java users; (2) a simulator that displays traces in a message sequence chart fashion; (3) requirements verification both by symbolic and enumerative model checking; (4) implementation verification by checking trace containment; (5) a proof manager that aids compositional and assume-guarantee reasoning; and (6) SLANG (Scripting LANGuage) for the rapid and structured development of new verification algorithms. jMocha is available publicly at; it is a successor and extension of the original Mocha tool that was entirely written in C. Rajeev Alur, Luca de Alfaro, Radu Grosu, Thomas A. Henzinger, M. Kang, Christoph M. Kirsch, Rupak Majumdar, Freddy Y. C. Mang, Bow-Yaw Wang |
ICSE | 5 |