\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{Towards Abstraction and Automation in Software Engineering}



\author[1]{Michael  Gurschler}%
\author[1]{Henry  Edison}%
\author[2]{Kalle Launiala}%
\author[1]{Pekka Abrahamsson}%
\affil[1]{Free University of Bozen-Bolzano, Italy}%
\affil[2]{ProtonIT, Finland}%


\vspace{-1em}



  
  \date{May 29, 2024}


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





\selectlanguage{english}
\begin{abstract}
Novel software development approaches are embracing abstraction and
automation techniques. It is claimed that abstraction and automation
techniques increase the productivity, improve the reusability and lower
the complexity of the projects. In this study we address these new
frontiers of software development by investigating on one novel
proposal, namely the Ball. The Ball is an information ecosystem for
authorised information containing web content, digital content as well
as service development and integration. It is claimed to improve the
reusability, productivity and security of software development while
lowering the complexity. While improving the software developer's
productivity it should produce smaller and more reasonable software
systems, leading to a better reusability and a shorter learning phase
for new developers. Up to now there exists no evidence to support these
claims. In this study we analyse the Ball ecosystem from multiple
perspectives. We compare it to related approaches in order to find its
advantages and disadvantages. In order to provide empirical data we
replicated a study where a mobile information system was developed using
three different technologies. The results of this study show that the
Ball ecosystem has the potential to improve the productivity of software
development. However, it still needs further development and
improvements before being competitive with traditional ways of
developing software.%
\end{abstract}%



\sloppy




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

