Today, software-engineering research and industry alikerecognize the need for practical tools to support reverse-engineering activities. Most of the well-known CASE tools support reverse engineering in some way. The Uni-fied Modeling Language (UML) has emerged as the defacto standard for graphically representing the design ofobject-oriented software systems. However, there does notyet exist a standard scheme for representing the reverse-engineered models of these systems. The various CASEtools usually adopt proprietary extensions to UML and,as a result, it is difficult, or even impossible, to ensurethat model semantics remains unambiguous when workingwith different tools at the same time. In this paper, we examine the capabilities of the two most successful industrial-strength CASE-tools in reverseengineering the static structure of software systems andcompare them to the results produced by two academicprototypes. The comparisons are carried out both manuallyand automatically using a research prototype for manipu-lating and comparing UML models.