%XXX why mann whitnet
%XXX why did others not report this earlier
%XXX change conclusion
%XXX walk the reviews looking for comments
%\documentclass[onecolumn,12pt,journal,compsoc]{IEEEtran}
%\renewcommand{\baselinestretch}{1.41}
\documentclass[cite,journal,12pt,compsoc, onecolumn]{IEEEtran}
\usepackage{pifont}
\usepackage{times}
\newcommand{\ed}{\end{description}}
\newcommand{\fig}[1]{Figure~\ref{fig:#1}}
\newcommand{\eq}[1]{Equation~\ref{eq:#1}}
\newcommand{\hyp}[1]{Hypothesis~\ref{hyp:#1}}
\newcommand{\tion}[1]{\S\ref{sec:#1}}

\usepackage{rotating}
\usepackage{alltt}
\usepackage{graphicx}
\usepackage{url}
\newcommand{\bi}{\begin{itemize}}
\newcommand{\ei}{\end{itemize}}
\newcommand{\be}{\begin{enumerate}}
\newcommand{\ee}{\end{enumerate}}
\newcommand{\bdd}{\begin{description}}
\newcommand{\edd}{\end{description}}
% IEEE Computer Society needs nocompress option
% requires cite.sty v4.0 or later (November 2003)
\usepackage[nocompress]{cite}
% normal IEEE
 % \usepackage{cite}

% correct bad hyphenation here
\hyphenation{op-tical net-works semi-conduc-tor}

\begin{document}

\title{Automatic Estimation Techniques
are Useful?}

\author{Tim~Menzies,~\IEEEmembership{Member,~IEEE,}
        Omid Jalali,
		Jairus Hihn,
	    Dan Baker,
		and Karen Lum
\thanks{ 
Tim Menzies, Omid Jalali, and Dan Baker
are with the Lane Department of
Computer Science and Electrical Engineering, West
Virginia University, USA: 
\protect\url{tim@menzies.us},
\protect\url{ojalali@mix.wvu.edu}, \protect\url{danielryanbaker@gmail.com}.}
\thanks{Jairus Hihn and Karen Lum at with NASA's Jet Propulsion Laboratory:
\protect\url{jhihn@mail3.jpl.nasa.gov},
\protect\url{karen.t.lum@jpl.nasa.gov}.}
\thanks{
The research described in this paper was carried out at West Virginia University
and the Jet 
Propulsion Laboratory, California Institute of Technology, under a contract with the US National Aeronautics and 
Space Administration. Reference herein to any specific 
commercial product, process, or service by trade name, 
trademark, manufacturer, or otherwise does not constitute 
or imply its endorsement by the US Government.}
}

\markboth{Journal Submission}%
{Menzies \MakeLowercase{\textit{et al.}}: Automatic Estimation Techniques are Useful?}

\IEEEaftertitletext{\vspace{-1\baselineskip}
\noindent\begin{abstract}
Best practices for software effort estimation can include
the use of automatic techniques to summarize past data.
There exists a large and growing number of techniques.
Which are useful?
In this study, 158 techniques were applied to
some COCOMO data.
$\frac{154}{158}=97\%$ of the variants
explored below
add little or nothing to 
a standard linear model (with  simple column and row pruning).
For example, learners
that assume multiple linear models  (such as model trees)
or no parametric form at all (such as nearest neighbor
estimation) perform relatively poorly.
Also,  elaborate searches did not add value to effort
estimation.  Exponential time   searching  for the best subsets of
the columns performed no better than near-linear-time column pruning.
It is possible that other techniques, not included in the 158 techniques
studied here, might perform better. 
However, based on current evidence,
this study concludes that when technique learners are used for effort estimation,
a linear model with simple column and row pruning will suffice
(at least, for COCOMO-style
data).
\end{abstract}\noindent
\begin{keywords}COCOMO, effort estimation, data mining, evaluation
\end{keywords}\vspace{1\baselineskip}}\maketitle
%-------------------------------------------------------------------------

\end{document}
