We use a few cookies

Essential cookies keep the library working. With your permission, we'd also like to use analytics to see what's useful and improve the experience. Read our Privacy Policy or Cookie Policy.

Skip to main content
Home/e-Resources/Electronics & Telecommunication Engineering/Software Development Effort Estimation Using Ensemble Machine Learning
PeriodicalsElectronics & Telecommunication Engineering

Software Development Effort Estimation Using Ensemble Machine Learning

Checking your access to this record.

Abstract & Overview

In software engineering, the main aim is to develop a high quality project that fall within scheduled time and budget, this procedure is called effort estimation.Effort estimation is crucial and important for a company to do because hiring more people than needed will lead to loss of income, and hiring less people than needed will lead to delay of project delivery.The aim of this study is to estimate software effort objectively by using machine learning techniques instead of subjective and time consuming estimation methods.Models using two machine learning techniques which are Support Vector Machine (SVM) and K-Nearest Neighbor (k-NN) separately and combining those together using ensemble learning were tried on two public datasets namely Desharnais and Maxwell.Results show that svm technique outperform k-nn technique, also ensemble learning improves the results.

Cite this record

(2017). Software Development Effort Estimation Using Ensemble Machine Learning. International journal of computing, communication and instrumentation engineering, 4(1). https://doi.org/10.15242/ijccie.e0317026

Copy in another style

Software Development Effort Estimation Using Ensemble Machine Learning. (2017). International journal of computing, communication and instrumentation engineering, 4(1). https://doi.org/10.15242/ijccie.e0317026
Author names are used as deposited, so check their order before you submit.

Metadata is harvested from open-access indexes and can be incomplete. Check a citation against the published version before relying on it — see our open access & attribution policy.