Value of ranked voting methods for estimation by analogy. Issue 4 (1st August 2013)

• Record Type: Journal Article
• Authors: Azzeh, Mohammad; Alseid, Marwan
• Is Part Of: IET software. Volume 7:Issue 4(2013)
• Page Start: 195
• Page End: 202
• Publication Date: 2013-08-01
• Subjects: least mean squares methods -- regression analysis -- software engineering -- trees (mathematics); categorical regression tree -- ordinary least-square regression -- stepwise regression -- regular K-based EBA -- Jack-knifing procedure -- similarity measure -- estimation by analogy -- ranked voting method; Computer software -- Periodicals; Software engineering -- Periodicals; 005.1
• DOI: 10.1049/iet-sen.2012.0119
• Languages: English
• ISSNs: 1751-8806

Abstract

Abstract : One long‐standing issue in estimation by analogy (EBA) is finding closest analogies. Prior studies revealed that existing similarity measures are easily influenced by extreme values and irrelevant features. Instead of identifying closest projects based on the aggregated similarity degrees, the authors propose to use ranked voting methods that rank projects per feature, and then aggregate those ranks over all features using voting count rules. The project(s) with highest score will be the winners and form new estimate for the target project. This also enables us to automatically come up with the preferred number of analogies for each target project, since the winner set may contain more than a single winner. Empirical evaluation with Jack‐knifing procedure has been carried out, in which nine datasets come from two repositories (PROMISE and ISBSG) were used for benchmarking. The proposed models are compared with some well known estimation methods: regular K ‐based EBA, stepwise regression, ordinary least‐square regression and categorical regression tree. The performance figures of the proposed models were promising. The use of voting methods present some useful advantages: (i) saving time in finding appropriate K number of analogies for each individual project, (ii) no need for project pruning and (iii) no data standardisation are required.