From 11916450177b46ec1cea4209ac2c04fbf7d76f93 Mon Sep 17 00:00:00 2001
From: Markus Quaritsch <markus.quaritsch@tugraz.at>
Date: Wed, 11 Nov 2015 18:08:34 +0100
Subject: [PATCH] authors, screenshots unit tests, complexity
---
.../Vecto_3.0.1.312/ReleaseNotes.tex | 34 +++++++++++++++++--
.../ReleaseNotes/preamble_handout.tex | 3 +-
2 files changed, 33 insertions(+), 4 deletions(-)
diff --git a/Documentation/ReleaseNotes/Vecto_3.0.1.312/ReleaseNotes.tex b/Documentation/ReleaseNotes/Vecto_3.0.1.312/ReleaseNotes.tex
index f4ca92d7e4..69f7ac3982 100644
--- a/Documentation/ReleaseNotes/Vecto_3.0.1.312/ReleaseNotes.tex
+++ b/Documentation/ReleaseNotes/Vecto_3.0.1.312/ReleaseNotes.tex
@@ -116,11 +116,39 @@ In case you find a bug or Vecto 3.0 does not behave as expected \textbf{please f
\item Software Tests: 258 successful unit- and integration tests
\begin{itemize}
\item Code coverage: 84\,\% \\
- The main parts of the code are covered by tests, the main parts with low coverage are tests of auto-generated equality methods and parsing of input data
+ The main parts of the code are covered by tests, parts with low coverage are mainly auto-generated equality methods and parsing of input data (cf.~\Cref{fig:Vecto301_TestCoverage})
\end{itemize}
- \item Code complexity\footnote{According to \textit{SourceMonitor}}: currently the max. complexity is 20 (single method) and 10 methods have a complexity $>$10. The most complex methods are in the ShiftStrategy, the DriverStrategy, and the Powertrain builder
+ \item Code complexity\footnote{According to \textit{SourceMonitor}}: currently the max. complexity is 20 (single method) and 10 methods have a complexity $>$10. The most complex methods are in the ShiftStrategy, the DriverStrategy, and the Powertrain builder; see \Cref{fig:Vecto301_Komplexity} and \Cref{fig:Vecto301_Kiviat}
\end{itemize}
+\begin{figure}
+ \centering
+ \includegraphics[width=0.8\textwidth]{img/Vecto3_0_1_TestCoverage.png}
+ \caption{Screenshot of Test-coverage Report (Microsoft Visual Studio)}
+ \label{fig:Vecto301_TestCoverage}
+\end{figure}
+
+\begin{figure}
+ \centering
+ \includegraphics[width=0.6\textwidth]{img/Vecto3_0_1-Checkpoints.png}\\[1cm]
+
+ \includegraphics[width=0.6\textwidth]{img/Vecto3_0_1-ClassComplexity.png}\\[1cm]
+
+ \includegraphics[width=0.6\textwidth]{img/Vecto3_0_1-MethodComplexity.png}
+
+ \caption{Screenshots of code metrics (SourceMonitor): Checkpoints over time (top), list of classes sorted by complexity (middle), List of methods sorted by complexity (bottom)}
+ \label{fig:Vecto301_Komplexity}
+\end{figure}
+
+\begin{figure}
+ \centering
+
+ \includegraphics[width=0.6\textwidth]{img/Vecto3_0_1-Kiviat.png}
+ \caption{Kiviat Metrics Graph (SourceMonitor)}
+ \label{fig:Vecto301_Kiviat}
+\end{figure}
+
+
%=========================================================================
\subsection{Open Issues} % (fold)
\label{sub:open_issues}
@@ -136,7 +164,7 @@ In case you find a bug or Vecto 3.0 does not behave as expected \textbf{please f
% subsection open_issues (end)
-
+\FloatBarrier
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{How to Submit a Bug Report} % (fold)
\label{sec:how_to_submit_a_bug_report}
diff --git a/Documentation/ReleaseNotes/preamble_handout.tex b/Documentation/ReleaseNotes/preamble_handout.tex
index ef5154f643..9a84024fac 100644
--- a/Documentation/ReleaseNotes/preamble_handout.tex
+++ b/Documentation/ReleaseNotes/preamble_handout.tex
@@ -23,11 +23,12 @@
% \institute{Institute for Technical Informatics, TU Graz}
\title{Vecto 3.x Release Notes} % Kurztitel in []
-\author{DI Dr. Markus Quaritsch}
+\author{DI Dr. Markus Quaritsch, DI Dr. Christian Kreiner, Michael Krisper}
\date{\today} % \today für heutiges Datum verwenden
\usepackage{pdfpages}
\usepackage{pifont}
+\usepackage{placeins}
\usepackage{array}
\newcolumntype{L}[1]{>{\raggedright\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
--
GitLab