Write Approach, start Product quality

[tt2015.git] / 2approach.tex

diff --git a/2approach.tex b/2approach.tex
index 162a8ba..0b06e1e 100644 (file)
--- a/2approach.tex
+++ b/2approach.tex
@@ -1,4 +1,4 @@
-Hello world
+
 %6
 %7
 %8
@@ -6,3 +6,34 @@ Hello world
 %10
 %11
 %12
+
+The test process consists of several stages. The results of the first stage,
+planning, are descibed in this document. On the basis of this document actual
+test cases will be designed. Afterwards the actual tests will be implemented and
+executed. The results of these tests will then be evaluated against the exit
+criteria (see Section~\ref{sec:exitcriteria}) and depending on the outcome of
+these evaluations further tests might be deemed necessary.
+
+\subsection{Quality Characteristics}
+The quality characteristics that are to be tested are described using the
+ISO/IEC 25010 \cite{iso25010}. In the following sections we will discuss the
+relevant \textit{product quality} and \textit{quality in use} characteristics.
+
+\subsubsection{Product quality}
+Product quality is divided into eight main categories which are divided into several
+subcategories. Below we will discuss the qualities which are relevant to the SUT.
+\begin{itemize}
+       \item \textbf{Functional suitability}\\  
+       As descibed in Section~\ref{sec:risks} the SUT is core functioanlity of the
+       networking capable system. Because many other systems running on the
+       system could rely on it it is very important that the SUT is functionaly
+       suitable. Therefore all three subcharacteristics of Functional Suitability 
+       (\textit{Functional completeness, Functional correctness, Functional
+       appropriateness}) are of vital importance. As was previously mentioned
+       in Section~\ref{sec:risks} extra emphasis should be placed on testing
+       \emph{Functional Correctness} as recovery from Failures in 
+       computer-to-computer systems is problematic.
+
+\end{itemize}
+
+\subsubsection{Quality in use}
\ No newline at end of file