% the test architecture.

% Develop a test environment or test architecture which will be used 
% for model-based testing of your SUT. Give a sketch of the test 
% architecture, i.e., the positioning of the SUT, test tool(s), 
% adapter(s), logging tool(s), ..., and their connections and 
% interfaces; explain your choices. Try to reuse (parts of) the 
% test-execution automation environment that you developed during the 
% second assignment.

To test the SUT \GAST needs to be able to send input to the SUT and receive its
output. To simplify the input and output handled by \GAST an adapter is added
between \GAST and the SUT. This adapter abstracts away from parts of the 
specification that are not needed for these tests, such as the payload, 
sequence number, etc. Essentially reducing each segment to only its flags (SYN,
ACK, FIN, etc.)

An EchoServer will connect to the SUT to offer an application which will accept
the incoming connection. However, since no data will be exchanged the EchoServer
will not be used for anything else.

Figure~\ref{fig:architecture_down} shows the flow of data from \GAST to the SUT
and Figure~\ref{fig:architecture_up} shows the flow of data from the SUT back
to \GAST.

Hier zou dus een plaatje van ``digraph TestSetupDown'' uit ``graphs.viz'' moeten komen. \label{fig:architecture_down}

Hier zou dus een plaatje van ``digraph TestSetupUp'' uit ``graphs.viz'' moeten komen. \label{fig:architecture_up}

% Hier moet nog meer over het automationdeel, maar ik weet neit hoe we dat
% gaan fixen