\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{An Approach Based on Metadata to Implement Convention over Configuration
Decoupled from Framework Logic}



\author[1]{Everaldo Gomes}%
\author[2]{Eduardo Guerra}%
\author[3]{Phyllipe Lima}%
\author[1]{Paulo Meirelles}%
\affil[1]{Universidade de Sao Paulo}%
\affil[2]{Libera Universita di Bolzano}%
\affil[3]{Universidade Federal de Itajuba}%


\vspace{-1em}



  
  \date{May 27, 2024}


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





\selectlanguage{english}
\begin{abstract}
Frameworks are essential for software development, providing code design
and reuse for its users. Well-known Java frameworks and APIs such as
Spring, JUnit, and JPA rely on metadata usage, commonly defined by code
annotations. Those frameworks use the Java Reflection API for consuming
and processing these annotations. Code elements usually have some
similarities and can also have the same annotation. This paper proposes
a model for defining conventions over configuration for annotations
usage decoupled from the metadata reading logic. With this model, if a
convention is present, the framework will consider that the element is
configured by a specific target annotation, even if the code element
does not have the annotation. We implemented this model in the metadata
reading framework Esfinge Metadata API. The model implementation was
evaluated refactoring an existing framework to add support to
conventions using our approach. As a result, it was possible to
introduce the conventions only by adding configurations to the
annotations. The model was further evaluated in an experiment in which
participants implemented the Conventions over Configuration pattern
using the Esfinge Metadata API and Java Reflection API. Based on the
results, approach fulfilled its goal of supporting the definition of
conventions decupled from the framework logic, making the code more
readable and easier to maintain according to the participants
perception.%
\end{abstract}%



\sloppy




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

