\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}}


\begin{document}

\title{SWEA Iteration 5: Test Doubles and More Patterns}

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

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

\maketitle

% =====================================================================
\section{EpsilonStone}

\subsection{Design and UML}

[Short argumentation for your EpsilonStone design: Refer to the UML
  diagram, and emphasize how indirect input are encapsulated; which
delegates are the Test Doubles and the real production implementation.]

\vspace{0.5cm}

[INCLUDE UML DIAGRAM HERE - A GOOD PICTURE OF HANDRAWN IS OK.]

\subsection{JUnit test cases}

[Write the full path of the JUnit test file, that configure Game with
  your test doubles(s), and tests the EpsilonStone behaviour.]

[Include screenshot/contents of the JUnit tests.]

% =====================================================================
\section{ZetaStone}

\subsection{Design and UML}

[Write a short argumentation for which roles (game/winner strategy/??)
  stores which state (hero health/attack output) and how this state is
  passed/access so your ZetaStone winner strategy can correctly
  determine the winner; and the collaborating roles have high
  cohesion.]

\vspace{0.5cm}

[Include a UML diagram that shows the design of the ZetaStone part of
  HotStone, with emphasis on the State pattern introduced and the
  existing winner strategies that are reused. (A good quality picture
  of a hand-drawn UML diagram is OK.) ]

\subsection{Unit/Integration Testing}

[Include short argumentation for your decision to either TDD using
  unit testing the strategy using a Game test double; or by
  integration testing with your standard game implementation.]

\subsection{State Selection Code}

[Write the full path of the implementation file of your State pattern
  for ZetaStone.]

\vspace{0.5cm}

[Write a short argumentation for how state selection is made, refering
to the code below.]

\vspace{0.5cm}

[A screenshot of the (JaCoCo-painted\footnote{It would be fine if you present JaCoCo or IntelliJ Code Coverage painted code to show your tests cover both states.}) state selection code in the
  Context implementation of the State pattern, showing that correct
  behaviour of ZetaStone has been tested. ]


% =====================================================================
\section{EtaStone}

\subsection{Design and UML}

[Short argumentation for your EtaStone design with reference to the
  UML diagram.]

\vspace{0.5cm}

[INCLUDE UML DIAGRAM HERE - A GOOD PICTURE OF HANDRAWN IS OK.]


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

The following features and requirements are still not implemented in
our HotStone software:

\begin{itemize}
\item \ldots
\item \ldots
\end{itemize}


\end{document}


