refine rqs
This commit is contained in:
parent
68887669dc
commit
0bde6c01d7
|
|
@ -1,21 +1,49 @@
|
|||
\section{Systematic Review Procedure}
|
||||
|
||||
To carry out the systematic review,
|
||||
To carry out the systematic review of GitHub pull request,
|
||||
we followed the established guideline from prior studies~\cite{}.
|
||||
Specifically,
|
||||
the procedure consists of the following four steps.
|
||||
|
||||
\subsection{Question formulation}
|
||||
|
||||
The following three research questions:
|
||||
Our research purpose is to \textit{identify, summarize and synthesize the research topics and metrics studied in relation to GitHub Pull request}.
|
||||
To achieve this,
|
||||
we have defined the following as our main research questions.
|
||||
|
||||
\textbf{RQ1: What is trend in the study of GitHub pull requests?}
|
||||
|
||||
\textbf{RQ2: What topics have been studied in relation to GitHub pull requests?}
|
||||
|
||||
\textbf{RQ3: What metrics have been used to study GitHub pull requests?}
|
||||
\vspace{1em}
|
||||
\noindent\textbf{RQ1: What is trend in the study of GitHub pull requests?}
|
||||
|
||||
\textit{Motivation:}
|
||||
We expect to present the ** of primary studies
|
||||
by ** their publication year, venue and research type.
|
||||
This can ***.
|
||||
|
||||
|
||||
\vspace{1em}
|
||||
\noindent\textbf{RQ2: What topics have been studied in relation to GitHub pull requests?}
|
||||
|
||||
\textit{Motivation:}
|
||||
We aim to create a systematic view of existing research topics about GitHub pull request,
|
||||
and build a research map revealing
|
||||
what topics have been studied
|
||||
and to which extent these topics have been investigated,
|
||||
and what topics receive no attention yet from the research community.
|
||||
This benefits researchers interested in GitHub pull request to
|
||||
by providing a readily-available summary of prior related studies,
|
||||
and pointing to potential research directions.
|
||||
|
||||
\vspace{1em}
|
||||
\noindent\textbf{RQ3: What metrics have been used to study GitHub pull requests?}
|
||||
|
||||
\textit{Motivation:}
|
||||
We hope to construct a complete list of metrics related to GitHub pull request,
|
||||
which can act as a reference and guidance for feature selection in future research.
|
||||
|
||||
|
||||
|
||||
\textbf{RQ4: How many pull requests are used for the study?}
|
||||
|
||||
\subsection{Literature search}
|
||||
|
||||
|
|
|
|||
|
|
@ -66,10 +66,10 @@
|
|||
|
||||
\multirow{2}*{dataset}
|
||||
& & Dataset & \\
|
||||
& & Dataset quality & \\\hline
|
||||
& & Dataset quality & \\
|
||||
|
||||
\bottomrule
|
||||
\end{tabular}
|
||||
\label{tab:tuple_sta}
|
||||
\label{tab:topics}
|
||||
|
||||
\end{table*}
|
||||
|
|
|
|||
|
|
@ -1,2 +1,22 @@
|
|||
\section{Metrics Used to Study Pull Request}
|
||||
|
||||
\begin{table*}[h]
|
||||
|
||||
\centering
|
||||
\caption{Metrics studied in previous research.}
|
||||
\begin{tabular}{@{}l l l l@{}}
|
||||
\toprule
|
||||
\textbf{Category} & \textbf{Sub-Category} & \textbf{Metric} & \textbf{Description} \\ \midrule
|
||||
\multirow{4}*{Project characteristics}
|
||||
& & \texttt{proj\_name}& \\
|
||||
& & \texttt{language}& \\
|
||||
& & \texttt{domain}& \\
|
||||
& & \texttt{proj\_age}& \\
|
||||
& & \texttt{hotness}& \\
|
||||
& & \texttt{proj\_sloc}& \\\hline
|
||||
|
||||
\bottomrule
|
||||
\end{tabular}
|
||||
\label{tab:metrics}
|
||||
|
||||
\end{table*}
|
||||
|
|
@ -0,0 +1,18 @@
|
|||
\section{Dataset size}
|
||||
|
||||
\begin{table}[h]
|
||||
|
||||
\centering
|
||||
\caption{The statistics of dataset size}
|
||||
\begin{tabular}{@{}l ccccc c @{}}
|
||||
\toprule
|
||||
Studied ***&\textbf{Min} &\textbf{25\%} &\textbf{Median} &\textbf{75\%} &\textbf{Max} &\textbf{Mean} \\ \midrule
|
||||
\#Project & 1 & 1 & 2 & 3 & 35 & 2.30 \\
|
||||
\#PR & 1 & 2 & 3 & 6 & 148 & 5.68 \\
|
||||
\#Interviewee & 1 & 2 & 3 & 6 & 148 & 5.68 \\
|
||||
\#Survey respondents & 1 & 2 & 3 & 6 & 148 & 5.68 \\
|
||||
\bottomrule
|
||||
\end{tabular}
|
||||
\label{tab:dtsize}
|
||||
|
||||
\end{table}
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Loading…
Reference in New Issue