\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 4: Code Quality and State Pattern}

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

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

\maketitle

% =====================================================================
\section{Clean Code Method One}

\subsection{Before Code}

[Include a screenshot/listing of your method(s) BEFORE cleaning up]

\subsection{Analysis}

[Insert the Clean Code Template here, fill in the 'is OK' column with
  'yes/no/not applicable' and fill in the 'Explain' column for the
  BEFORE code - outlining shortly why the property is OK or not; OR a
  reference to a longer discussion below]

[Provide further analysis/argumentation in case the 'Explain'
  column is too small to provide a sufficient analysis]

\subsection{After Code}

[Include a screenshot/listing of your method AFTER cleaning up]

\subsection{Conclusion}

[Insert the Clean Code Template here, fill in the 'is OK' column with
  'yes/no/not applicable' and fill in the 'Explain' column for the
  AFTER code]

[Provide further analysis/argumentation in case the 'Explain'
  column is too small to provide a sufficient analysis]

% =====================================================================
\section{Clean Code Method Two}

\subsection{Before Code}

[Include a screenshot/listing of your method(s) BEFORE cleaning up]

\subsection{Analysis}

[Insert the Clean Code Template here, fill in the 'is OK' column with
  'yes/no/not applicable' and fill in the 'Explain' column for the
  BEFORE code]

[Provide further analysis/argumentation in case the 'Explain'
  column is too small to provide a sufficient analysis]

\subsection{After Code}

[Include a screenshot/listing of your method AFTER cleaning up]

\subsection{Conclusion}

[Insert the Clean Code Template here, fill in the 'is OK' column with
  'yes/no/not applicable' and fill in the 'Explain' column for the
  AFTER code]

[Provide further analysis/argumentation in case the 'Explain'
  column is too small to provide a sufficient analysis]


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

\subsection{Design and UML}

[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{State Selection Code}

[Include 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{Backlog}

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

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


\end{document}


