···55555656Scenarios:
5757\begin{itemize}
5858- \item Waiting for players scenario: the process which waits for 5 players in the system
5858+ \item Welcome players scenario: the process which waits for 5 players in the system
5959 \item Begin game scenario: The process which shuffles and start giving the cards
6060 \item Partner selection scenario: The process which handles the partern selection phase
6161 \item Game scenario: The process which handles the whole game phase
···78787979% Analysis overview diagram here
80808181-\section{Design}\label{sec:design}
8181+\subsection{Scenarios}
8282+8383+Scenarios are an example of the dynamics, the process of how something can happen. Conversely, the goal hierarchy is a static representation - it tries to break down all the high level goals into subgoals. Each scenario must be associated with some goal, that represents what that scenario is trying to achieve.
8484+8585+\paragram{Welcome players scenario}
8686+8787+This scenario covers the necessary processes to subscribe a user to the system. First, the user must make the subscription attempt. This subscription is received by the system, passed to the appropriate agent and stored appropriately. ....
8888+8989+\subsection{Goal overview}
9090+9191+\subsection{System roles}
9292+The next stage of the process is to group similar goals together into roles. Each role should be limited in scope, and be able to be described fully be 1-2 sentences. Grouping is done using the System Roles diagram.
9393+9494+\section{Architectural Design}\label{sec:design}
9595+9696+\subsection{Data Coupling}
9797+9898+\subsection{Agent-Role Grouping}
9999+100100+\subsection{Agent Acquaintance}
821018383-Design choices
102102+\subsection{System overview}
8410385104\section{Prototype}\label{sec:proto}
861058787-Description. Pieces of code.
106106+Description. Excerpt from the code.
8810789108\section{Conclusion}\label{sec:concl}
90109