\documentclass[a4paper,10pt]{article}

\usepackage[latin1]{inputenc}
\usepackage{graphicx}
\usepackage{url}
\usepackage{palatino}
%%\usepackage{rotating}



% A java class name
\newcommand{\cn}[1]{{\sf #1}}
% A java method name or call
\newcommand{\mn}[1]{{\sf #1}}

% A scenario
\newcommand{\scenario}[1]{{\em #1}}

% A TDD pattern in text
\newcommand{\tp}[1]{{\em #1}}


% A design pattern pattern in text
\newcommand{\dpn}[1]{{\scshape #1}}


% Partition box
\newenvironment{partition}{%
\begin{center}%
\begin{tabular}{l|c|c}%
Condition & Invalid ECs & Valid ECs \\%
\hline\hline}%
{\hline\end{tabular}\end{center}}

% Equivalence class box
\newenvironment{ec}{%
\begin{center}%
\begin{tabular}{l|c|c}%
ECs covered & Test case & Expected output \\%
\hline\hline}%
{\hline\end{tabular}\end{center}}


\begin{document}

\title{SWEA Iteration 9:\\Distribution using Broker I}

\author{
  \texttt{<<Group name>>}\\
  Computer Science, University of Aarhus\\
  8200 {\AA}rhus N, Denmark\\
  \makeatletter
  $<<$Names$>>$\\
}

\date{$<<$Date$>>$}

\maketitle

% =====================================================================
\section{Broker 1.1: TDD of pass-by-value Game methods}

[Shortly outline your group's process with developing the missing
  broker roles: which test stubs did you use and for what purpose, use
  of visual clues (System.out) during the process, etc.?]

\subsection{ClientProxy Implementation}

[Insert one/two examples of your ClientProxy implementation of Game methods]

[Short explanation of the code]

\subsection{Invoker Implementation}

[Insert fragments of your Invoker code, ideally matching those
  selected above]

[Short explanation of the code]

\subsection{Testing}

[Insert a few of the most important JUnit test code]

[Short explanation of the test code, and the doubles used]

% =====================================================================
\section{Broker 1.2: TDD of Card and Hero methods}

[Shortly outline your group's process with developing the missing
  broker roles: which test stubs did you use and for what purpose?]

\subsection{ClientProxy Implementations}

[Insert one/two examples of your ClientProxy implementation of Card
  and Hero methods]

[Short explanation of the code]

\subsection{Invoker Implementation}

[Insert fragments of your Invoker code, ideally matching those
  selected above]

[Short explanation of the code]

\subsection{Testing}

[Insert a few of the most important JUnit test code]

[Short explanation of the test code, and the doubles used]

% =====================================================================
\section{Broker 1.3}

\subsection{Screenshots and Explanation of Story Test}

[Create and include screenshots of the following user story:]

First, we start the server on a computer with IP [what is the ip, if
  you are not using 'localhost'?].

[include image of shell on server computer in which IP is clearly
  visible; and next the start command of the server]

Next, we start the 'hotstoneStorytest' on another computer/another shell
and connect it to the server

[include image of shell on client computer which connects to the
  server, executes the story, and print the relevant method return
  values]

After the client has executed the story, the server has printed
relevant received requests and returned replies as log messages:

[include image of log output on the server computer]



% =====================================================================
\section{EC test of SigmaStone augmentMinion()}

\subsection{Conditions}
Regarding the $augmentMinion()$ function

\[
(attack, health) = augmentMinion(minion, field, hero)
\]
the following conditions are relevant:

\begin{itemize}
  \item minion class
\item field support
\item \emph{(Your group's further analysis here)}
\end{itemize}

\subsection{EC tables}
These leads to a first version of the \emph{equivalence class table}:

\begin{partition}
minion class (set type) & - & Medi [a1]; Nord [a2]; Asia [a3]; Cent [a4] \\
\ldots & \ldots & \ldots \\
\end{partition}

(You may provide elaborations of the table in the likely event that
some ECs require further partitioning. Hint: As the function includes
aritmetic computation, be sure to read the FRS computation
heuristics.)

The found ECs have the \emph{representation} and \emph{coverage}
properties because [argument here].
 
\subsection{Test case table}

We use the heuristics generate test cases as outlined in the extended
test case table:

\begin{ec}
\ldots & \ldots & \ldots \\
\end{ec}

% =====================================================================
\section{Backlog}

[Outline backlog items if any]

\end{document}


