ACM Home Page
Please provide us with feedback. Feedback
Toward automatic artifact matching for tool evaluation
Full text PdfPdf (212 KB)
Source ACM Southeast Regional Conference archive
Proceedings of the 47th Annual Southeast Regional Conference table of contents
Clemson, South Carolina
SESSION: Software engineering I table of contents
Article No. 15  
Year of Publication: 2009
ISBN:978-1-60558-421-8
Author
Yan Liang  The University of Alabama, Tuscaloosa, AL
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 10,   Downloads (12 Months): 20,   Citation Count: 0
Additional Information:

abstract   references   index terms  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1566445.1566466
What is a DOI?

ABSTRACT

Before performing software maintenance and evolution tasks, developers must expend significant effort to understand the design of the subject software system. Reverse engineering and reengineering tools can extract artifacts, such as class diagrams, from source code so that the effort expended on program comprehension can be greatly reduced. Choosing suitable and appropriate tools is itself a difficult process. Many metrics and benchmarks have been proposed to evaluate the quality of reengineering tools, but the process is still complicated and requires much human effort. Furthermore, ignored by most evaluation experiments and approaches is the understanding of differences and similarities of the output artifacts produced by different tools. This paper proposes a novel approach for tool evaluation making a direct comparison of the output artifacts of the chosen tools. We apply our methodology on class diagrams extracted from source code. We utilize a class matching model to automate the process. In this study, we use ten open-source programs as test cases and two open source reverse engineering tools Doxygen and StarUML. We evaluate the output of these two tools based on class matching given the same input. This approach, we believe, provides developers with good guidance in tool selection.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
 
3
Sabrina Fortsch and Bernhard Westfechtel, DIFFERENCING AND MERGING OF SOFTWARE DIAGRAMS; State of the Art and Challenges. International Conference on software and data technologies ICSOFT 2007.
 
4
 
5
Steven Kearney, James F. Power. Benchmarking the accuracy of reverse engineering tools for Java programs: a study of eleven UML tools. Technical Report: NUIM-CS-TR-2007-1. June 6, 2007.
 
6
 
7
 
8
 
9
 
10
Daniel L. Moise, Kenny Wong. Issues in Integrating Schemas for Reverse Engineering. Proceedings of the International Workshop on Meta-Models and Schemas for Reverse Engineering (ateM 2003).
 
11