From 99f92f59d9b4f703376708066a40a6dd655ad319 Mon Sep 17 00:00:00 2001 From: pimjager Date: Sun, 20 Dec 2015 23:35:28 +0100 Subject: [PATCH] Added a bit of discussion --- a3/1modelingTCP.tex | 2 +- a3/5discussion.tex | 11 ++++++++++- a3/tt3.bib | 6 +++++- 3 files changed, 16 insertions(+), 3 deletions(-) diff --git a/a3/1modelingTCP.tex b/a3/1modelingTCP.tex index a841b87..10e4110 100644 --- a/a3/1modelingTCP.tex +++ b/a3/1modelingTCP.tex @@ -1,7 +1,7 @@ In previous assignments our group has viewed the SUT as a stateful input-output system. -\subsection{Behaviour of the SUT}\label{subsec:behaviour} +\subsection{Behaviour of the SUT} \label{subsec:behaviour} When considering the behaviour of the SUT we abstract away from some details to limit the scope of the project. We will only consider the behaviour as the sequence of input output flags. All other details required will be implemented diff --git a/a3/5discussion.tex b/a3/5discussion.tex index 87a78c1..7a4a96a 100644 --- a/a3/5discussion.tex +++ b/a3/5discussion.tex @@ -32,4 +32,13 @@ exhaustive search will also generate huge tests for big models. Both JTorX and \GAST use on-line checking. They test the SUT on the fly by syncing state transitions in the internal model of the SUT with observed output (after input) from the SUT. -%iets over ease of use van test model generation \ No newline at end of file +For JTorX test generation was very simple since it accepts models in GraphViz +DOT language, which is also the language used for describing the models for this +report. For \GAST the model generation required a bit more work, as the model +is written as a function in Clean. This translation is however easily done by +hand. Because the model for \GAST is written as a function in Clean it is very +expressive, the modeling method chosen for JTorX however is a lot less +expressive, as it just allows for specification of states and transition labels +between them. However JTorX allows for many different modeling languages, which +can be more expressive than modeling using GraphViz models \cite{JTorXSite}. +However, for our tests GraphViz models were expressive enough. \ No newline at end of file diff --git a/a3/tt3.bib b/a3/tt3.bib index 28a90fc..cd67d5d 100644 --- a/a3/tt3.bib +++ b/a3/tt3.bib @@ -78,4 +78,8 @@ Updated by RFCs 1122, 3168, 6093, 6528}, year={2003}, publisher={Springer} } - +@misc{JTorXSite, + title = {JTorX - FMT Tools}, + howpublished = {\url{https://fmt.ewi.utwente.nl/redmine/projects/jtorx/wiki/}}, + note = {Accessed: 2015-12-26} +} -- 2.20.1