Bugs in software are costly and difficult to find and fix. In recent years, many tools and techniques have been developed for automatically finding bugs by analyzing source code or intermediate code statically (at compile time). Different tools and techniques have different tradeoffs, but the practical impact of these tradeoffs is not well understood. In this paper, we apply five bug finding tools, specifically Bandera, ESC/Java 2, FindBugs, JLint, and PMD, to a variety of Java programs. By using a variety of tools, we are able to cross-check their bug reports and warnings. Our experimental results show that none of the tools strictly subsumes another, and indeed the tools often find non-overlapping bugs. We discuss the techniques each of the tools is based on, and we suggest how particular techniques affect the output of the tools. Finally, we propose a meta-tool that combines the output of the tools together, looking for particular lines of code, methods, and classes that many tools warn about.

First responders need to be able to have the most amount of situational awareness of the operations they perform while not being overwhelmed by all of the information that may be made available to them. This paper presents the Rover integration and fusion platform to alleviate the fusing of multiple information sources, which may not be known prior to the beginning of an operation. Rover can aid fusing sources by providing as much contextual information which often will be forgotten when designing programs, mapping contextual information into a view in which programs and users can use, and automate well-known and designed tasks. All of this occurs while deploying Rover to first responder incident scenes without the need for an existing network infrastructure prior to an incident.