Abstract
Static source code analysis tools output several warning messages, which are useful to detect software faults before testing and prevent further fault injections through coding. However, a flood of warning messages sometimes burdens developers to confirm all of the messages to judge whether an action should be taken for each one or not. In this paper a technical idea is shown to group warning messages by using code clone information to reduce the cognitive load of developers. A set of practically developed source code files and its relevant code clone information were investigated to evaluate the applicability of the idea. The result showed that the grouped warning messages were treated in almost the same manner within the group.
