\documentclass[10pt]{article}

\usepackage{fullpage}
\usepackage{setspace}
\usepackage{parskip}
\usepackage{titlesec}
\usepackage[section]{placeins}
\usepackage{xcolor}
\usepackage{breakcites}
\usepackage{lineno}
\usepackage{hyphenat}





\PassOptionsToPackage{hyphens}{url}
\usepackage[colorlinks = true,
            linkcolor = blue,
            urlcolor  = blue,
            citecolor = blue,
            anchorcolor = blue]{hyperref}
\usepackage{etoolbox}
\makeatletter
\patchcmd\@combinedblfloats{\box\@outputbox}{\unvbox\@outputbox}{}{%
  \errmessage{\noexpand\@combinedblfloats could not be patched}%
}%
\makeatother


\usepackage{natbib}




\renewenvironment{abstract}
  {{\bfseries\noindent{\abstractname}\par\nobreak}\footnotesize}
  {\bigskip}

\titlespacing{\section}{0pt}{*3}{*1}
\titlespacing{\subsection}{0pt}{*2}{*0.5}
\titlespacing{\subsubsection}{0pt}{*1.5}{0pt}


\usepackage{authblk}


\usepackage{graphicx}
\usepackage[space]{grffile}
\usepackage{latexsym}
\usepackage{textcomp}
\usepackage{longtable}
\usepackage{tabulary}
\usepackage{booktabs,array,multirow}
\usepackage{amsfonts,amsmath,amssymb}
\providecommand\citet{\cite}
\providecommand\citep{\cite}
\providecommand\citealt{\cite}
% You can conditionalize code for latexml or normal latex using this.
\newif\iflatexml\latexmlfalse
\providecommand{\tightlist}{\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}%

\AtBeginDocument{\DeclareGraphicsExtensions{.pdf,.PDF,.eps,.EPS,.png,.PNG,.tif,.TIF,.jpg,.JPG,.jpeg,.JPEG}}

\usepackage[utf8]{inputenc}
\usepackage[english]{babel}



\usepackage{float}








\begin{document}

\title{Security-based code smell definition, detection, and impact
quantification in Android}



\author[1]{Mengyu Shi}%
\author[1]{Yi Zhong}%
\author[1]{Jiawei He}%
\author[1]{Chunrong Fang}%
\author[1]{Zhenyu Chen}%
\affil[1]{State Key Laboratory of Novel Software Technology}%


\vspace{-1em}



  
  \date{June 15, 2024}


\begingroup
\let\center\flushleft
\let\endcenter\endflushleft
\maketitle
\endgroup





\selectlanguage{english}
\begin{abstract}
Android occupies a high market share, and its broad functions make
Android security matter. Research reveals that many security issues are
caused by insecure coding practices. As a poor design indicator, code
smell threatens the safety and quality assurance of Android applications
(apps). Although previous works revealed specific problems associated
with code smells, the field still lacks research reflecting Android
features. Moreover, the cost and time limit developers to repairing
numerous smells timely. We conducted a study, including definition,
detection, and impact quantification for Android code smell (DefDIQ):
(1) define 15 novel code smells in Android from a security programming
perspective; meanwhile, we provide suggestions on how to eliminate or
mitigate them; (2) implement DACS to automatically detect the custom
code smells based on ASTs; (3) investigate the correlation between
individual smells with DACS detection results, and select suitable code
smells to construct fault counting models, then quantify their impact on
quality, and thereby generating code smell repair priorities. We
conducted experiments on 4,575 open-source apps, and the findings are:
(i) Lin's CCC between DACS and manual detection results reaches 0.9994,
verifying the validity; (ii) the fault counting model constructed by
ZINB is superior to NB (AIC = 517.32, BIC = 522.12); some smells do
indicate fault-proneness, and we identify such avoidable poor designs;
(iii) different code smells have different importance and the repair
priorities constructed provide a practical guideline for researchers and
inexperienced developers.%
\end{abstract}%



\sloppy




\selectlanguage{english}
\FloatBarrier
\end{document}

