Together provides a wide variety of audits, ranging from design issues to naming conventions. The process of running audits begins with your selecting the specific rules to which your source code should conform. Together generates an audit report that displays only the violations of those rules. You can examine each violation and decide whether to correct the source code.
For most violations, the audit report generated by Together indicates the line of code that causes the violation. For some audits, however, such a line number is inappropriate. These are called problem detection audits. An example is the Misplaced Class audit, in which the package of the class is deemed inappropriate because of the dependency between the class and a different package. For problem detection audits, Together uses one or more of detection metrics to analyze the code to determine audit violations.
Together audit reports show problem detection audits along with the other, line-oriented audits.