November 11, 2016 & 2.0 & Divided sections between group members \\
November 13, 2016 & 3.0 & Created format for Module Guide and added sections 2 and 4 \\
November 13, 2016 & 4.0 & Final version with all sections and subsections added \\
\bottomrule
\end{tabularx}
\end{table}
\clearpage
\section{Introduction}
The purpose of this report is to verify that the software has been tested properly and that it was implemented correctly.
\section{Anticipated and Unlikely Changes}
\subsection{Anticipated Changes}
\paragraph{AC1:} The specific hardware on which the game is running.
\paragraph{AC2:} The format of the input data. (left and right keys can be changed to different keys inside the GameController class without it affecting the rest of the project)
\paragraph{AC3:} The constraints on the input parameters.
\paragraph{AC4:} Game features. (Number of people added on the highscores list, number of lives given to the user)
\paragraph{AC5:} Additional features. (Advanced single player mode with obstacles added, different speeds of the ball)
\paragraph{AC6:} Magnitude of game controls and media (size of the buttons, ball etc.).
\subsection{Unlikely Changes}
\paragraph{UC1:} Input and output devices. (Input: mouse clicks and keyboard presses, Output: screen/console)
\paragraph{UC2:} There will always be a source of input data external to the software.
\paragraph{UC3:} Game mechanics. (Formulas to calculate when ball should change direction)
\paragraph{UC4:} Execution environment. (Must be java-based)
\section{Connection Between Requirements and Design}
The design of the system is intended to satisfy the requirements developed in the SRS. In this stage, the system is decomposed into modules. The connection between requirements and modules is listed in Table 3.
