Overleaf sync

parent ccc48781
\section{Sources of knowledge}
\label{sec:sources}
......@@ -24,9 +23,8 @@ Figures~\ref{fig:papers-per-year}~and~\ref{fig:source_types-per-year} depicts th
\end{minipage}
\end{figure}
Most of the works published on \devops are in the ``IEEE Software'' magazine, and they are mostly short papers describing experiences in real life faced by organizations. Therefore,
it is advisable for practitioners to follow this source to get future updates on \devops, since it has become a reference on the subject.
A common source of papers on \devops is the ``IEEE Software'' magazine. Among the 50 main selected studies, 13 were published in this magazine, being mostly short papers describing experiences in real life faced by organizations. Therefore,
it is advisable for practitioners to follow this source to get future updates on \devops since it has become a reference on the subject.
We did not find many peer-reviewed publications or events dedicated to the theme of \devops. The closest related events to the subject we found are the ``International Workshop on Release Engineering'' and the ``International Workshop on Quality-Aware DevOps''. For researchers starting their work on \devops, these are two potential targets for publishing their first results. For the academic community
interested in the subject, this shows that it could be valuable to foster the organization of dedicated \devops events or journal special issues.
......@@ -35,25 +33,21 @@ We found \numberofselectedpapers papers from peer-reviewed sources, of which we
\input{tabs/papers-classification.tex}
\myparagraph{Impact} explores the impact of \devops in other aspects of software development. For example, impact of \devops on architecture~\citesel{shahin2016architecting}, security~\citesel{yasar2016security}, quality assurance~\citesel{roche2013quality}, or the impact of \devops on software development in specific scenarios, such as the development of software for research~\citesel{cerqueira2015researchops}.
\myparagraph{Practices} provides tools, practices, patterns and approaches that can enhance the \devops experience. Support for selecting deployment technology~\citesel{wettinger2015knowledge}, explanation about the usage of metrics~\citesel{forsgren2018metrics}, communication of global peers through specialized social networks~\citesel{magoutis2015social}, and causing infrastructure faults at production to ensure system reliability~\citesel{basiri2016chaos} are examples.
\myparagraph{Experience Report} refers to concrete experience accounts of organizations adopting \devops or continuous delivery/deployment. For example, the report of Siqueira~\emph{et al.} that describes the role of a \devops team in the context of a governmental project~\citesel{siqueira2018gov}.
\myparagraph{Challenges} focuses on the challenges derived from the effort of adopting \devops or continuous delivery / deployment. Some papers focus on specific challenges, such as \devops in regulated domains~\citesel{laukkarinen2017medical}, embedded systems~\citesel{lwakatare2016towards}, and communication~\citesel{diel2016distributed}.
\myparagraph{Support} provides new tools and practices that can enhance the \devops experience. Support for selecting deployment technology~\citesel{wettinger2015knowledge}, explanation about the usage of metrics~\citesel{forsgren2018metrics}, and communication of global peers through specialized social networks~\citesel{magoutis2015social} are examples.
\myparagraph{Education} investigates the challenges in teaching \devops. They propose teaching methods for it~\citesel{christensen2016teaching}, as well explore the knowledge, skills, and abilities (KSA) necessary for \devops professionals~\citesel{chung2016ksa,hussain2017zealand}.
\myparagraph{Impact} explores the impact of \devops in other aspects of software development. For example, impact of \devops on architecture~\citesel{shahin2016architecting}, security~\citesel{yasar2016security}, quality assurance~\citesel{roche2013quality}, or the impact of \devops on software development in specific scenarios, such as the development of software for research~\citesel{cerqueira2015researchops}.
\myparagraph{Tools} provides some overview of \devops technologies~\citesel{ebert2016devops} or focus on specific tools~\citesel{kang2016docker}.
\myparagraph{Concepts} introduces basic concepts for \devops and continuous delivery, such as the deployment pipeline~\citesel{humble2011devops}.
\myparagraph{Patterns and Practices} provides collections of patterns used in \devops context. Examples are patterns on microservices~\citesel{brown2016microservices} and cloud services~\citesel{cukier2013patterns} usage.
\myparagraph{Challenges} focuses on the challenges derived from the effort of adopting \devops or continuous delivery / deployment. Some papers focus on specific challenges, such as \devops in regulated domains~\citesel{laukkarinen2017medical}, embedded systems~\citesel{lwakatare2016towards}, and communication~\citesel{diel2016distributed}.
\myparagraph{Introduction} introduces the concepts of \devops and continuous delivery.
\myparagraph{Education} investigates the challenges in teaching \devops. They propose teaching methods for it~\citesel{christensen2016teaching}, as well explore the knowledge, skills, and abilities (KSA) necessary for \devops professionals~\citesel{chung2016ksa,hussain2017zealand}.
\myparagraph{Adoption patterns} deals with the different models of \devops adoption~\citesel{nybom2016mixing}, which is further discussed on Section~\ref{sec:devosp-adoption-approaches}, and describe how a specific organization used metrics to evaluate its \devops adoption process~\citesel{snyder2018analytics}. \\
\myparagraph{Adoption} deals with the different models of \devops adoption~\citesel{nybom2016mixing}, which is further discussed on Section~\ref{sec:devosp-adoption-approaches}, and describe how a specific organization used metrics to evaluate its \devops adoption process~\citesel{snyder2018analytics}. \\
In the ``Main Selected Studies'' listing, each article is listed with a code, where the letter of the code indicates how we found the article: ``A'' for the ACM Digital Library\swurl{dl.acm.org}, ``I'' for the IEEE Xplore Digital Library\swurl{https://ieeexplore.ieee.org}, ``S'' for Springer Link\swurl{link.springer.com}, and ``B'' for the snowballing process.
In the ``Main Selected Studies'' listing (page \pageofmainselecetdstudies), each article is listed with a code, where the letter of the code indicates how we found the article: ``A'' for the ACM Digital Library\swurl{dl.acm.org}, ``I'' for the IEEE Xplore Digital Library\swurl{https://ieeexplore.ieee.org}, ``S'' for Springer Link\swurl{link.springer.com}, and ``B'' for the snowballing process.
In the next section, we detail other surveys on \devops and how this work differentiates from them.
......@@ -153,11 +147,11 @@ This point is the major contribution of our survey, where we propose a conceptua
\subsection{Books}
Books are a popular source of knowledge on \devops among practitioners. Although they usually have more pages than academic papers, usually they are easier to read and to assimilate. Searching at Amazon.com for books written in English containing ``\devops'' in the title, we observed one year delay from papers trending on the topic to books following the same pattern. We have conducted this search at Amazon on 11 April 2018 and Figure~\ref{fig:books-per-year} presents the annual distribution of total of 137 books found in this search.
Books are a popular source of knowledge on \devops among practitioners. Although they usually have more pages than academic papers, usually they are easier to read and to assimilate. Searching at Amazon.com for books written in English containing ``\devops'' in the title, we observed one year delay from papers trending on the topic to books following the same pattern. We conducted this search at Amazon on 11 April 2018 and Figure~\ref{fig:books-per-year} presents the annual distribution of total of 137 books found in this search.
\begin{figure}[ht]
\includegraphics[scale=0.55]{figs/books-per-year}
\caption{Distribution of books about DevOps by year according to Amazon.com}
\caption{Distribution of books about DevOps by publication year according to Amazon.com}
\label{fig:books-per-year}
\end{figure}
......
......@@ -65,9 +65,11 @@
% End of macros for proof-reading
% ---------------------------------------------------------------------------- %
% Text macros
\newcommand\devops{DevOps\xspace}
\newcommand\numberofselectedpapers{167\xspace}
\newcommand\numberofmainselectedpapers{50\xspace}
\newcommand\pageofmainselecetdstudies{31\xspace}
\newcommand{\myparagraph}[1]{\vspace{.5em}\noindent\textit{\textbf{#1:}}\hspace{.3em}}
\newcommand{\swurl}[1]{\footnote{\url{#1}}}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment