DevelopmentPlan.tex

\documentclass{article}

\usepackage{booktabs}
\usepackage{tabularx}
\usepackage{hyperref}

\hypersetup{colorlinks=true,urlcolor=cyan}

\title{SE 3XA3: Development Plan\\Mini-Arcade}

\title{SE 3XA3: Problem Statement \\ Mini-Arcade \\{\large Team \#4, Undetermined}}

\author{Andrew Hum \\ huma3 \\ 400138826 \and
		William Lei \\ leim5 \\ 400125240 \and
		Arshan Khan \\ khana172 \\ 400145605 \and
		Jame Tran \\ tranj52 \\ 400144141
}

\date{}

%\input{../Comments}

\begin{document}

\begin{table}[hp]
\caption{Revision History} \label{TblRevisionHistory}
\begin{tabularx}{\textwidth}{llX}
\toprule
\textbf{Date} & \textbf{Developer(s)} & \textbf{Change}\\
\midrule
1/29/2020 & Andrew Hum & Rough draft of sections 1 - 3\\
1/30/2020 & William Lei & Sections 4, 7\\
Date2 & Name(s) & Description of changes\\
... & ... & ...\\
\bottomrule
\end{tabularx}
\end{table}

\newpage

\maketitle

Put your introductory blurb here.

\section{Team Meeting Plan}

Typical meetings will occur during lab time on Mondays and Wednesdays from 9:30am - 11:20 am in room 236 in the Information Technology Building on campus. These meetings will occur weekly with the exceptions of breaks. During these meetings, Arshan leads the group as project manager, however, the group works as equals to assign appropriate work to each individual. If there is work left uncompleted after our allocated meeting slots, additional meetings will be scheduled amongst the team members. The individual in charge of the meeting agenda will switch each meeting and be in charge of recording minutes, written statement on decisions made and homework designations.

\section{Team Communication Plan}

The teams primary means of communication is through a group chat on Facebook. This allows easy communication to the entire group, as well as individual conversations if needed. For issues related to the software, we may use Git Issues to notify one another on current issues that need resolving. Each group member can contact one another through email if necessary.

\section{Team Member Roles}

\item Arshan Khan - Project Manager, Game Developer, Tester
\item Andrew Hum - Architect, Game Developer, Tester
\item William Lei - Git Expert, Launcher Developer
\item Jame Tran - Developer, Tester

\section{Git Workflow Plan}

The git workflow of the team will be centralized and branch based. There will a total of 6 branches: master; development; and a personal branch for each team member.\\
The master branch is the central and main branch, it will always contains production ready code. Team member cannot directly commit changes to the master branch, as it can only be updated by merging changes from the development branch. The main branch will be labelled by a version number along with a title, which will be updated after every merge.\\
The development branch is the main branch that will be used for the development of the project. It is initialized by branching off master and can be reset to master when needed. Similar to master branch, team members cannot directly commit to this branch, as it can only be updated by merging from their personal branch.\\
Each team member will have a personal branch which only that person have the permission to commit to. This is the branch that the team members commit their code to during the development.\\
Each member can update development branch anytime by merging their personal branch if the code in their personal branch is up to date with the changes made in development branch (by other team members) and fully operational. When a milestone or a certain checkpoint is met, upon the agreement of all team members, the master will then be updated by merging from development branch, and its label will be updated with a newer version number and a new title.

\section{Proof of Concept Demonstration Plan}

\section{Technology}

\section{Coding Style}

PEP 8 will be used as the coding style for this project. The detail style guide can be found on the official website of Python at \url{http://www.python.org/dev/peps/pep-0008}.\\
Doxygen will be used as the documentation and commenting style guide for this project. The detail style guide can be found on the official website of Doxygen at \url{http://www.doxygen.nl/}.

\section{Project Schedule}

Provide a pointer to your Gantt Chart.

\section{Project Review}

\end{document}