% -*- coding: utf-8; -*-
% vim: set fileencoding=utf-8 :
\documentclass[english,submission]{programming}
%% First parameter: the language is 'english'.
%% Second parameter: use 'submission' for initial submission, remove it for camera-ready (see 5.1)

\usepackage[backend=biber]{biblatex}
\usepackage{longtable}
\addbibresource{bib.bib}


%
% Packages and Commands specific to article (see 3)
%
% These ones  are used in the guide, replace with your own.
%
\usepackage{multicol}
\lstdefinelanguage[programming]{TeX}[AlLaTeX]{TeX}{%
  deletetexcs={title,author,bibliography},%
  deletekeywords={tabular},
  morekeywords={abstract},%
  moretexcs={chapter},%
  moretexcs=[2]{title,author,subtitle,keywords,maketitle,titlerunning,authorinfo,affiliation,authorrunning,paperdetails,acks,email},
  moretexcs=[3]{addbibresource,printbibliography,bibliography},%
}%
\lstset{%
  language={[programming]TeX},%
  keywordstyle=\firamedium,
  stringstyle=\color{RosyBrown},%
  texcsstyle=*{\color{Purple}\mdseries},%
  texcsstyle=*[2]{\color{Blue1}},%
  texcsstyle=*[3]{\color{ForestGreen}},%
  commentstyle={\color{FireBrick}},%
  escapechar=`,}
\newcommand*{\CTAN}[1]{\href{http://ctan.org/tex-archive/#1}{\nolinkurl{CTAN:#1}}}
%%

\def\tightlist{}

\begin{document}

\title{Exploratory and Live, Programming and Coding}
\subtitle{A Literature Study} % optional
\titlerunning{Exploratory and Live, Programming and Coding} %optional, in case that the title is too long; the running title should fit into the top page column

\author[a]{Patrick Rein}
\authorinfo{Contact him at \email{patrick.rein@hpi.uni-potsdam.de}.}
\affiliation[a]{Hasso Plattner Institute, University of Potsdam, Germany}

\author[a]{Stefan Ramson}
\authorinfo{Contact him at \email{stefan.ramson@hpi.uni-potsdam.de}.}

\author[a]{Jens Lincke}
\authorinfo{Contact him at \email{jens.lincke@hpi.uni-potsdam.de}.}

\author[a]{Robert Hirschfeld}
\authorinfo{Contact him at \email{robert.hirschfeld@hpi.uni-potsdam.de}.}

% \authorrunning{T. Pape, C. Lopes, R. Hirschfeld} % Optional, for long author lists

\keywords{TODO} % please provide 1--5 keywords


%%%%%%%%%%%%%%%%%%
%% These data MUST be filled for your submission. (see 5.3)
\paperdetails{
  %% perspective options are: art, sciencetheoretical, scienceempirical, engineering.
  %% Choose exactly the one that best describes this work. (see 2.1)
  perspective=scienceempirical,
  %% State one or more areas, separated by a comma. (see 2.2)
  %% Please see list of areas in http://programming-journal.org/cfp/
  %% The list is open-ended, so use other areas if yours is/are not listed.
  area={TODO},
  %% You may choose the license for your paper (see 3.)
  %% License options include: cc-by (default), cc-by-nc
  % license=cc-by,
}
%%%%%%%%%%%%%%%%%%

%%%%%%%%%%%%%%%%%%
%% These data are provided by the editors. May be left out on submission.
%\paperdetails{
%  submitted=2016-08-10,
%  published=2016-10-11,
%  year=2016,
%  volume=1,
%  issue=1,
%  articlenumber=1,
%}
%%%%%%%%%%%%%%%%%%

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Please go to https://dl.acm.org/ccs/ccs.cfm and generate your Classification
% System [view CCS TeX Code] stanz and copy _all of it_ to this place.
%% From HERE
\begin{CCSXML}
<ccs2012>
<concept>
<concept_id>10002944.10011122.10003459</concept_id>
<concept_desc>General and reference~Computing standards, RFCs and guidelines</concept_desc>
<concept_significance>300</concept_significance>
</concept>
<concept>
<concept_id>10010405.10010476.10010477</concept_id>
<concept_desc>Applied computing~Publishing</concept_desc>
<concept_significance>300</concept_significance>
</concept>
</ccs2012>
\end{CCSXML}

\ccsdesc[300]{General and reference~Computing standards, RFCs and guidelines}
\ccsdesc[500]{Applied computing~Publishing}

% To HERE
%%%%%%%%%%%%%%%%%%%%%%%

\maketitle

% Please always include the abstract.
% The abstract MUST be written according to the directives stated in
% http://programming-journal.org/submission/
% Failure to adhere to the abstract directives may result in the paper
% being returned to the authors.
\begin{abstract}
  % Context: What is the broad context of the work? What is the importance of the general research area?
  Various programming tools, languages, and environments give programmers the \emph{impression of changing a program while it is running}. 
  This experience of \emph{liveness} has been discussed since the 1950s and a broad spectrum of research on this topic exists.
  Amongst other, this work has been carried out in the communities around three major ideas which incorporate liveness as an important aspect: \emph{live programming}, \emph{exploratory programming}, and \emph{live coding}.
  
  % Inquiry: What problem or question does the paper address? How has this problem or question been addressed by others (if at all)?
  While there have been publications on the focus of each single community, the overall spectrum of liveness across these three communities has not been investigated yet. Thus, we want to delineate the variety of research on liveness. At the same time, we want to investigate overlaps and differences in the values and contributions between the three communities.
  
  % Approach: What was done that unveiled new knowledge?
  Therefore, we conducted a literature study with a sample of 191 publications on the terms retrieved from three major indexing services. 
  On this sample, we conducted a thematic analysis regarding the following aspects: motivation for liveness, application domains, modes of running a program, and types of contributions.
  We also gathered bibliographic information such as related keywords and prominent cited works.
  %
  % Grounding: What argument, feasibility proof, artifacts, or results and evaluation support this work?
  
  % Knowledge: What new facts were uncovered? If the research was not results oriented, what new capabilities are enabled by the work?
  Besides other characteristics the results show that the field of \emph{exploratory programming} is mostly about technical designs and empirical studies on tools for general-purpose programming.
  In contrast, works on \emph{live coding} have the most variety in their motivations and methodologies with a majority being empirical studies with users. As expected, most works on live coding are applied to performance art.
  Finally, work on \emph{live programming} is mostly motivated by making programming more accessible and easier to understand, evaluating their tool designs through empirical studies with users.
  
  % Importance: Why does this work matter?
  In delineating the spectrum of work on liveness, we hope to make the individual communities more aware of the work of the others. Further, by giving an overview of the values and methods of the individual communities, we hope to provide researchers new to the field of \emph{liveness} with an initial overview.
\end{abstract}

\include{body}


\printbibliography

\end{document}

% Local Variables:
% TeX-engine: luatex
% End:
