Knowing that a design violates its specification is only the first step towards a correct system. The violation may be caused by a fault in the design, but also by an error in the specification or in the environment constraints. A designer needs to understand the violation and to locate and correct the fault that causes it. Industrial experience shows that fault localization and rectification take much more time, effort, and expense than fault detection. Also, debugging often takes place late in the design cycle, which makes it a high–risk activity that may, if not done quickly and correctly, delay the release of a product. The workshop addresses the technologies and methodologies that need to be employed after verification has detected the presence of a bug. It aims to combine the efforts of the computer–aided verification and software engineering communities, attracting work in the areas of algorithms, tools, and methodologies for failure analysis. We welcome submissions addressing debugging of software, circuit designs, or combinations of the two. <b>Keywords:</b> explanation and simplification of error traces,<br>fault localization,<br>rectification of the design, the specification, or the environment description,<br>test case generation for debugging,<br>debugging techniques,<br>methodologies that facilitate debugging,<br>overviews that provide a novel view of the state of the art and stimulate discussion and further research, and empirical studies on debugging.<br>
Abbrevation
V&D
City
SeattleWA
Country
United States
Deadline Paper
Start Date
End Date
Abstract