From: pimjager <pim@pimjager.nl>
Date: Tue, 29 Sep 2015 11:11:26 +0000 (+0200)
Subject: Write Approach, start Product quality
X-Git-Url: https://git.martlubbers.net/?a=commitdiff_plain;ds=sidebyside;h=12f34d11f316bcb7b2cd63732515d55d37a1d6ad;p=tt2015.git

Write Approach, start Product quality
---

diff --git a/1intro.tex b/1intro.tex
index ea70356..eca8c06 100644
--- a/1intro.tex
+++ b/1intro.tex
@@ -32,7 +32,7 @@ ACCEPT	tcp	--	anywhere	anywhere	tcp flags:PSH/PSH
 DROP	tcp	--	anywhere	anywhere	tcp flags:RST/RST
 \end{lstlisting}
 
-\subsection{Risks}
+\subsection{Risks} \label{sec:risks}
 %5. Risks
 Risks can be divided into two categories. Project risks and product risks. 
 Because an existing implementation is used the project risk are non applicable.
diff --git a/2approach.tex b/2approach.tex
index 162a8ba..0b06e1e 100644
--- 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
diff --git a/3eval.tex b/3eval.tex
index a1032bb..76da37c 100644
--- a/3eval.tex
+++ b/3eval.tex
@@ -2,3 +2,5 @@ Hello world
 %13
 %14
 %15
+
+\label{sec:exitcriteria}
\ No newline at end of file