%
% Fill only lines marked with dots  
% 
%
%
\documentclass[10pt,a4paper,twoside]{article}
\usepackage{latexsym,amssymb}
\usepackage{amssymb,amsmath}
\usepackage{graphicx}
\usepackage{color}
\usepackage{fancyhdr}
\pagestyle{fancy}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%  PLEASE, ONLY IN ENGLISH                                         %
%  PLEASE, ONLY ONE PAGE                                           %
%  PLEASE, USE LATEX2E                                             %
%                                                                  %
%  PLEASE, DO NOT DEFINE NEW COMMANDS                              %
%  USE NEWTHEOREMS BELOW, PLEASE, IF YOU WRITE THEOREMS AND SUCH   % %                                                                  %
%  PLEASE, CONTROL THE SIZE OF YOUR ABSTRACT BEFORE YOU SEND IT    %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
\newtheorem{thm}{Theorem}
\newtheorem{defi}[thm]{Definition}
\newtheorem{axi}[thm]{Axiom}
\newtheorem{clm}[thm]{Claim}
\newtheorem{col}[thm]{Corollary}
\newtheorem{lem}[thm]{Lemma}
\newtheorem{con}[thm]{Conjecture}
\newtheorem{hyp}[thm]{Hypothesis}
\newtheorem{rem}[thm]{Remark}
\newcommand{\proof}{\noindent{\bf Proof:}\hspace{0.2cm}}
\setcounter{thm}{0}
\newcommand{\N}{{\mathbb N}}
\newcommand{\R}{{\mathbb R}}
\newcommand{\W}{W_0^{1,p}(\Omega)}
\newcommand{\eps}{{\varepsilon}}
\newcommand{\ds}{\displaystyle}

\newcommand{\F}{\mathcal F}
\newcommand{\E}{\mathscr E}
\newcommand{\J}{\mathscr{J}}
\newcommand{\Pl}{(\mathscr{P})}
\newcommand{\CC}{\mathbb C}
\newcommand{\into}{\int\limits_{\Omega}}
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\textwidth 15.0cm
\textheight 22.0cm
\oddsidemargin 0.4cm
\evensidemargin 0.4cm
\topmargin  0.0cm

\frenchspacing

\headwidth=\textwidth 	
\fancyhead[HCO]{8th Int. Conf. on Mathematics and Informatics,
	September 9-10, 2021, T\^argu Mure\c s, Romania}
\lhead{}\rhead{}
\fancyfoot{}
%


\begin{document}

\begin{center}{\Large\bf
Influencing factors in developers' code comprehension
}\end{center}
%
\begin{center}{\large\bf\noindent
Anett Fekete
}\\[2mm]
%%
Eötvös Loránd University, Faculty of Informatics
%%
\\[1mm]\texttt{
%%	
afekete@inf.elte.hu
%%
}\end{center}
%

\vspace*{7mm}
%
Long-term projects will inevitably face the problem of changing team members - especially in large development teams - and the neglect of certain components of the source code. Such projects tend to grow to a size where it becomes nearly impossible to know and understand the entire project. It is crucial to keep track of who is competent in each unit of the code in order to avoid information loss.

The contributions made by developers to the source code offer an obvious starting point when we try to map and quantify the software related knowledge of each developer. However, the contributions are diverse: apart from the quantity and significance of modifications, other factors also play an important role in code comprehension and software related knowledge, such as code reviews, pull request reviews, knowledge in documentation, or forgetting. In this talk, I present the different results derived from 3 important factors in code comprehension: the quantity and significance of modifications in the source code, and the inevitable forgetting.

\end{document}


