CRAFT A Framework for Evaluating Software Clustering Results in the Absence of Benchmark De.pdf

CRAFT A Framework for Evaluating Software Clustering Results in the Absence of Benchmark De.pdf

  1. 1、本文档共10页,可阅读全部内容。
  2. 2、有哪些信誉好的足球投注网站(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
  3. 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  4. 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
查看更多
CRAFT A Framework for Evaluating Software Clustering Results in the Absence of Benchmark De

CRAFT: A Framework for Evaluating Software Clustering Results in the Absence of Benchmark Decompositions Brian S. Mitchell and Spiros Mancoridis Department of Mathematics Computer Science Drexel University, Philadelphia, PA, USA {bmitchel, smancori}@ Abstract Software clustering algorithms are used to create high-level views of a system’s structure using source code-level artifacts. Software clustering is an active area of research that has produced many clustering al- gorithms. However, we have seen very little work that investigates how the results of these algorithms can be evaluated objectively in the absence of a benchmark de- composition, or without the active participation of the original designers of the system. Ideally, for a given system, an agreed upon refer- ence (benchmark) decomposition of the system’s struc- ture would exist, allowing the results of various clus- tering algorithms to be compared against it. Since such benchmarks seldom exist, we seek alternative methods to gain confidence in the quality of results produced by software clustering algorithms. In this paper we present a tool that supports the eval- uation of software clustering results in the absence of a benchmark decomposition. 1. Introduction Background Maintaining large and complex software systems is a daunting task. Poor software maintenance practices often lead to a system’s premature retirement, or ne- cessitates significant restructuring in order to keep the source code in manageable condition. There are many causes for these poor maintenance practices. Little can be done about practical issues such as limited main- tenance budgets, lack of access to the original devel- opers and designers of the system, and short devel- opment schedules. However, if software maintainers have a thorough understanding of the underlying sys- tem structure, it is more likely that changes to the source code can be performed without deviating from the system design and architecture. Additionally, i

文档评论(0)

l215322 + 关注
实名认证
内容提供者

该用户很懒,什么也没介绍

1亿VIP精品文档

相关文档