diff --git a/Doc/SRS/SRS.pdf b/Doc/SRS/SRS.pdf
new file mode 100644
index 0000000000000000000000000000000000000000..2091ad1bdb83c15a0f74a5910a0211d047b7d6b7
Binary files /dev/null and b/Doc/SRS/SRS.pdf differ
diff --git a/Doc/SRS/SRS.tex b/Doc/SRS/SRS.tex
new file mode 100644
index 0000000000000000000000000000000000000000..e49717d5b99b475b31075244d38ae83f087663e5
--- /dev/null
+++ b/Doc/SRS/SRS.tex
@@ -0,0 +1,403 @@
+\documentclass{article}
+
+\usepackage[dvipsnames]{xcolor}
+\usepackage{booktabs}
+\usepackage {graphicx}
+\usepackage {tabularx}
+\usepackage{mdframed}
+\usepackage{tabto}
+\usepackage{keyval}
+
+% ============= Requirements Table =============
+\makeatletter
+
+\define@key{req}{event}{\def\req@event{#1}}
+\define@key{req}{description}{\def\req@description{#1}}
+\define@key{req}{rationale}{\def\req@rationale{#1}}
+\define@key{req}{fitcrit}{\def\req@fitcrit{#1}}
+\define@key{req}{satisfaction}{\def\req@satisfaction{#1}}
+\define@key{req}{priority}{\def\req@priority{#1}}
+\define@key{req}{dissatisfaction}{\def\req@dissatisfaction{#1}}
+\define@key{req}{conflicts}{\def\req@conflicts{#1}}
+\define@key{req}{supportingmats}{\def\req@supportingmats{#1}}
+\define@key{req}{history}{\def\req@history{#1}}
+
+\newcounter{reqNum}
+\newcommand{\requirement}[1] {
+ \setkeys{req}{#1}
+ \stepcounter{reqNum}
+ \begin{mdframed}
+ \textbf{Requirement \#:} \arabic{reqNum} \tabto{4cm}
+ \textbf{Requirement Type:} \arabic{section}.\arabic{subsection} \tabto{9.5cm}
+ \textbf{Event \#:} \req@event \\ [\baselineskip]
+ \begin{tabularx}{\textwidth}{@{}lX@{}}
+ \textbf{Description:} & \req@description \\
+ \textbf{Rationale:} & \req@rationale \\
+ \textbf{Fit Criterion:} & \req@fitcrit \\ [\baselineskip]
+ \end{tabularx}
+ \begin{tabularx}{0.5\textwidth}{@{}lX@{}}
+ \textbf{Customer Satisfaction:} & \req@satisfaction \\
+ \textbf{Priority:} & \req@priority \\[\baselineskip]
+ \end{tabularx}
+ \begin{tabularx}{0.5\textwidth}{@{}lX@{}}
+ \textbf{Customer Dissatisfaction:} & \req@dissatisfaction \\
+ \textbf{Conflicts:} & \req@conflicts \\[\baselineskip]
+ \end{tabularx}
+ \begin{tabularx}{\textwidth}{@{}lX@{}}
+ \textbf{Supporting Materials:} & \req@supportingmats \\
+ \textbf{History:} & \req@history
+ \end{tabularx}
+ \end{mdframed}
+}
+
+\makeatother
+
+% ================ Title ===============
+
+\title{
+ \vspace{40mm}
+ \textbf {
+ \Huge {\color[rgb]{0.9,0,0}Blaze} Brigade \\
+ \large - Software Requirements Specification -}}
+
+\date{October 11, 2016}
+
+\author{SFWR ENG 3XA3 - Section L02 \\
+ 007 (Group 7) \\ \\
+ Jeremy Klotz - klotzjj \\
+ Asad Mansoor - mansoa2 \\
+ Thien Trandinh - trandit \\
+ Susan Yuen - yuens2}
+
+
+% =============== Document ===============
+
+\begin{document}
+
+\maketitle
+\pagenumbering{gobble}
+\newpage
+\pagenumbering{arabic}
+
+\tableofcontents
+\listoftables
+\listoffigures
+
+\begin{table}[bp]
+\caption{\bf Revision History}
+\begin{tabularx}{\textwidth}{p{3cm}p{2cm}X}
+\toprule {\bf Date} & {\bf Version} & {\bf Notes}\\
+\midrule
+October 10, 2016 & 1.0 & Revision 0 of Requirements Document\\
+\bottomrule
+\end{tabularx}
+\end{table}
+
+\newpage
+
+\section{Project Drivers}
+
+\subsection{The Purpose of the Project}
+
+Blaze Brigade serves as a tribute and adaptation of a popular genre: tactical simulation role-playing games. The game aims to provide a form of entertainment to the general public, presenting a fun strategical challenge to its players. The purpose of the project is to recreate an already existing tactical role-playing game, Tactics Heroes, and to ultimately further improve on the overall user experience by implementing additional features not already included in Tactics Heroes.
+
+\subsection{The Stakeholders}
+
+\subsubsection{The Client}
+The client of the project is Dr. Spencer Smith in the Computing and Software Department at McMaster University.
+
+\subsubsection{The Customers}
+The customers of the game include members of the general public who are interested in the tactical role-playing game genre and are willing to play the game.
+
+\subsubsection{Other Stakeholders}
+Other stakeholders of the project include:
+\begin{itemize}
+ \item The Blaze Brigade team
+ \item[] The project will serve as a means of entertainment and project development experience to its developers.
+ \item Tactics Heroes developers
+ \item[] The game may serve as a guideline to the original developers of Tactics Heroes to further improve their game by incorporating our project’s additional add-on features, as well as modern software development tools and concepts.
+\end{itemize}
+
+\subsection{Mandated Constraints}
+
+\subsubsection{Solution Constraints}
+\textbf{Description:} The game shall support Windows, Mac, and Linux OS. \\
+\textbf{Rationale:} The client will access the game using a device running Windows, Mac, or Linux. \\
+\textbf{Fit Criterion:} The game shall be developed to support these three operating systems, and testing will ensure that the game runs smoothly on all three operating systems.
+
+\subsubsection{Off-the-Shelf Software}
+The product will be utilizing Unreal Engine 4 for game development, as well as Adobe Photoshop for graphic editing. A device that is able to run Unreal Engine 4 is also required for project development. Customers must be in possession of an operating system to be able to play the game, and a pointing device to be able to select items on the screen.
+
+\subsubsection{Schedule Constraints}
+Full development of the game does not have any applicable schedule constraints. However, the basic functions of the game must be fully completed by December 2016.
+
+\subsubsection{Budget Constraints}
+The budget for the project is \$0 as all software required for development is provided for free. In addition, all hardware required is already owned by the project's respective developers.
+
+\subsection{Naming Conventions and Terminology}
+
+{\renewcommand{\arraystretch}{1.4}
+\begin{tabularx}{\textwidth}{lX}
+ \toprule
+ \textbf{Term} & \textbf{Definition} \\
+ \midrule
+ \textbf{RPG} & Role-playing game, in which the player plays the game as a character. \\
+ \textbf{AI} & Artificial Intelligence. \\
+ \textbf{Unit} & A single character in the game. \\
+ \textbf{Enemy} & Units that are hostile to the player's units and may attack the player's units when in range. \\
+ \textbf{Critical hit} & Causes the user to deal more damage than expected from a normal hit. \\
+ \textbf{HP} & Health points; the amount of damage a unit may take before being defeated. \\
+ \textbf{STR} & Strength; Used in calculating physical damage dealt by the unit. \\
+ \textbf{INT} & Intelligence; Used in calculating magical damage dealt by the unit. \\
+ \textbf{SKILL} & Used to calculate unit's hit rate and critical hit rate. \\
+ \textbf{SPEED} & Used to calculate a unit's number of hits on the enemy. \\
+ \textbf{DEFENSE} & Used to calculate the melee damage dealt to the unit. \\
+ \textbf{RESISTANCE} & Used to calculate the magic damage dealt to the unit. \\
+ \bottomrule
+\end{tabularx}
+
+\subsection{Relevant Facts and Assumptions}
+
+\subsubsection{Relevant Facts}
+The game that Blaze Brigade will re-implement, Tactics Heroes, was initially named Fire Emblem Factory. The game is heavily influenced from a Japanese game series called "Fire Emblem", which was released in 1990 by Intelligent Systems and Nintendo. Fire Emblem revolutionized the genre by incorporating RPG elements,
+and as such, the success of the genre in modern day can largely be attributed to this series. In addition, Tactics Heroes is still in alpha stage, and only the basic gameplay mechanics have been fully implemented. Future content for additional features in Tactics Heroes is still under works by its developers.
+
+\subsubsection{Assumptions}
+It is assumed that upon project launch, the host site for the game's download will be free. It is also assumed that members of the general public will not use any aspect of the project or its source code for malicious intent or for resale for monetary value.
+
+\newpage
+
+\section{Functional Requirements}
+
+\subsection{The Scope of the Work and the Product}
+The developers of Blaze Brigade must create a tactical turn-based game, in which the objective is to eliminate all of the enemy units.
+
+\subsubsection{The Context of the Work}
+The game will be available to play on all desktop and laptop platforms (Windows, Mac, Linux OS), and will be packaged and deployed using Unreal Engine 4. The developers will first develop a working game, and will then allow others to use and evaluate the prototype. Afterwards, the developers will use the feedback to refine the code further and repeat the evaluation process. These evaluation stages are crucial for developing software that meets the customers' desires, as the game should be fun and entertaining for those who play it.
+
+\subsubsection{Work Partitioning}
+
+\begin{tabularx}{\textwidth}{lllX}
+ \toprule
+ Event \# & Event Name & Input & Output \\
+ \midrule
+ 1 & Mapping System & Developer Code & Executable File \\
+ 2 & Mechanics & Developer Code & Executable File \\
+ 3 & Units & Developer Code & Executable File \\
+ 4 & Terrain Types & Developer Code & Executable File \\
+ 5 & Sprites & Developer Code/Graphics & Executable File \\
+ 6 & Map Creation & Developer Code & Executable File \\
+ 7 & Audio & Microphone & Audio Output Device \\
+ 8 & Deployment & Developer Code & Executable File \\
+ \bottomrule
+\end{tabularx}
+
+\bigskip
+
+\noindent
+\begin{tabularx}{\textwidth}{llll}
+ \toprule
+ Event \# & Summary of BUC \\
+ \midrule
+ 1 & A grid system that simulates the playing board. \\
+ 2 & Built-in combat system. \\
+ 3 & A class that all playable units are modelled by. \\
+ 4 & Properties of terrain types. \\
+ 5 & A collection of sprites used for terrain types, and playable units. \\
+ 6 & A playing board with all sprites added. \\
+ 7 & Sound effects and background music. \\
+ 8 & To make Blaze Brigade playable on all operating systems. \\
+ \bottomrule
+\end{tabularx}
+
+\subsubsection{Individual Product Use Cases}
+
+\begin{tabularx}{\textwidth}{lX}
+ \toprule
+ Product Use Case & Description of Use Case \\
+ \midrule
+ Playing the Game & The user plays the game and has a sense of enjoyment. \\
+ Stimulating the Brain & The user thinks about the game at a deeper level. This causes the player to exercise and train their brain. \\
+ \bottomrule
+\end{tabularx}
+
+\subsection{Functional Requirements}
+
+The following contains the functional requirements of the project:
+
+\begin{itemize}
+ \item The game will contain a main menu, with options to select New Game, Load Game, How-To-Play, and Exit Game.
+ \item The game shall be turn-based.
+ \item A player's turn should end once all their units have performed available actions.
+ \item A unit shall only act once per turn.
+ \item Units will be able to move within their move range and shall not be able to pass through obstacles.
+ \item Obstacles on terrain will block units from moving through them.
+ \item All units shall have a corresponding class.
+ \item Classes shall include:
+ \begin{itemize}
+ \item Warriors which will be physical oriented units, with a focus on Strength and Defense.
+ \item Archers which will be a ranged physical oriented unit, with a focus on Strength, Skill, and Speed.
+ \item Mages which will be a magical oriented unit, with a focus on Magic and Resistance.
+ \end{itemize}
+ \item All units will have stat values corresponding to their class.
+ \item The stats of the game shall include:
+ \begin{itemize}
+ \item Strength stat will be used to calculate physical damage.
+ \item Intelligence stat will be used to calculate magical damage.
+ \item Defense stat will be used to calculate physical defense.
+ \item Resistance stat will be used to calculate magical defense.
+ \item Skill stat will be used to calculate hit, miss, and critical rates.
+ \item Speed stat will be used to calculate if a unit can attack twice (if the unit's speed stat is 5 higher than target's speed stat).
+ \end{itemize}
+ \item All units will have a unique corresponding HP bar.
+ \item All units shall be able to attack enemy units.
+ \item Units will lose HP if hit by a successful attack, where the hp change is equal to (Strength - Defense) if physical or (Intelligence - Resistance) if magical.
+ \item Units that fall below 1 HP will be deceased and no longer be able to be used in the current battle.
+ \item One side will be victorious, when the other side has no playable units left.
+ \item Player shall be able to select which weapon each unit uses to perform an attack.
+
+\end{itemize}
+
+\newpage
+
+\section{Non-functional Requirements}
+
+\subsection{Look and Feel Requirements}
+
+\subsubsection{Appearance Requirements}
+The product will display the '007' logo upon start up for a reasonable amount of time, then will display the menu page afterwards. The menu page will consist of a “nature-like†background (such as trees), with clouds floating across the top. The actual game will consist of maps pertaining to varying locations and themes, such as a volcano or a tundra. The characters to be controlled will be drawn and coloured in such a way that they do not blend into the background. The resolution of the game will be preset and unchangeable from a 640x480 resolution.
+
+\subsubsection{Style Requirements}
+The style of the game will be a pixelated tactical RPG, similar to classics like Fire Emblem, and will have a nostalgic appeal to those who are familiar with this genre of old school RPGs.
+
+\subsection{Usability and Humanity Requirements}
+
+\subsubsection{Ease of Use Requirements}
+The game shall be playable by persons who are capable of thought and are able to operate a pointing device (ie. mouse or touchpad).
+
+\subsubsection{Learning Requirements}
+The user shall be able to operate a computer or pointing device.
+
+\subsubsection{Understandability and Politeness Requirements}
+The user shall be able to operate a computer or pointing device.
+
+\subsubsection{Accessibility}
+The game shall be playable on Windows, Mac, and Linux OS.
+
+\subsection{Performance Requirements}
+
+\subsubsection{Speed and Latency Requirements}
+The response between the game and user input should be near instant.
+
+\subsubsection{Safety-Critical Requirements}
+The game must meet standard video game regulations.
+
+\subsubsection{Precision Critical Requirements}
+The gameplay combat statistics shall accurately reflect what is displayed on the screen. Changes in these statistics shall also be accurately reflected upon proper user input.
+
+\subsubsection{Reliability and Availability Requirements}
+The game shall be available for as long as the user has access to a Windows, Mac, or Linux machine.
+
+\subsubsection{Robustness or Fault-Tolerance Requirements}
+The game shall run for as long as the machine is on, or until the user exits the game.
+
+\subsubsection{Capacity Requirements}
+The game shall be able to support gameplay for up to 2 players.
+
+\subsubsection{Longevity Requirements}
+The game shall be playable for as long as Windows, Mac, or Linux OS supports the game file type.
+
+\subsection{Operational and Environmental Requirements}
+
+\subsubsection{Expected Technological Environment}
+The user shall be accessing and navigating the game from a computer running Windows, Mac, or Linux OS.
+
+\subsubsection{Productization Requirements}
+Before the product is playable, it must be deployed through Unreal Engine 4.
+
+\subsection{Maintainability and Support Requirements}
+
+\subsubsection{Maintainability}
+The game should be ready for launch without need for further maintenance.
+
+\subsubsection{Portability and Adaptability}
+The game shall be playable on Windows, Mac, and Linux OS.
+
+\subsection{Security Requirements}
+
+\subsubsection{Access Requirements}
+The game shall be made available to the general public through a free online download link hosted by a remote hosting site. The public shall be able to access the game given that they have previously acquired internet access and access to a machine capable of running the game.
+
+\subsubsection{Integrity Requirements}
+The game shall not accept invalid user input, nor have the source code modified by any persons or apparatus who are not permitted to do so.
+
+\subsection{Cultural Requirements}
+
+The game shall not contain any form of content that may be found offensive to any religious or ethnic group. The game shall state that any resemblance in game to real people or events is purely coincidental.
+
+\subsection{Legal Requirements}
+
+The game shall comply with the law.
+
+\newpage
+
+\section{Project Issues}
+
+\subsection{Open Issues}
+The developers of Blaze Brigade must become familiarized with the C++ programming language and investigate how to efficiently adapt to the specific coding standard and testing methodologies. With the use of new technologies, such as a Unreal Engine 4, additional time would need to be allocated to learn this tool in depth. In addition, a feasibility study is yet to be completed to indicate whether a mouse-only control would be a feasible for all the possible scenerios present throughout the game play.
+
+\subsection{Off-the-Shelf Solutions}
+Blaze Brigade makes use of Tactics Heroes, an open source program that motivates the creation of a tactical simulation role-playing game. The engine streamlines the process of implementing the framework, and the developers of Blaze Brigade would simply need to implement maps, units, characters and the storyline. Rather than re-inventing the framework, we can use the pre-existing model of Tactics Heroes, and simply polish it in order to fulfil the enhancement requirement of the project. In addition, the open-source program presents a software license agreement and encourages developers to contribute to the program by getting involved within the forums.
+
+\subsection{New Problems}
+No new problems are tracked at this stage of the project.
+
+\subsection{Tasks}
+\subsubsection{Project Planning}
+The game shall be completed using the prospective timeline:
+
+\noindent
+\begin{tabularx}{\textwidth}{llX}
+ \toprule
+ Task & Resource & Start Date \\
+ \midrule
+ Problem Statement & Developers & Sept 20 \\
+ Development Plan & Developers & Sept 23 \\
+ Requirements Document - Revision 0 & Developers & Oct 3 \\
+ Test Plan - Revision 0 & Developers & Oct 21 \\
+ Design Document - Revision 0 & Developers & Sept 23 \\
+ Development of Blaze Brigade & Developers & Oct 31\\
+ Testing of Game & Developers & Dec 1\\
+ Debugging of Game & Developers & Dec 1 \\
+ Survey Round 1 & Client & Dec 12\\
+ Implement changes from survey feedback & Developers & Dec 13 \\
+ Survey Round 2 & Client & Dec 20 \\
+ Implement final changes from survey feedback & Developers & Dec 21 \\
+ \bottomrule
+\end{tabularx}
+
+\subsubsection{Planning of the Development Phases}
+
+The tasks listed in the table above will serve as the main guide for the developers to ensure that deliverables are completed in correct succession. In that regard, the output will serve the purpose to ensure that all of the requirements have been met before starting the next iteration of development in the next phase. In addition to the development phases, documents such as Problem Statement, Development Plan, Software Requirements Specification, Design Document, and Test Plan would need to be created and updated for the stakeholders as the project proceeds.
+
+\subsection{Migration to the New Product}
+Not applicable at this stage of the project.
+
+\subsection{Risks}
+The risk associated with the project comes with the nature of developing a game. For instance, accommodating testing into the game play would be a time-consuming and trivial task. Hence, the investigation on how to proceed with a specific testing standard and whether to introduce an automated testing framework is still underway at this stage of the project. In relation to the design aspect, a feasibility study is yet to be completed to indicate whether a mouse-only control would be feasible throughout all the scene of the game play. In addition, research will have to be conducted to ensure that the product is compatible on multiple operating systems. In addition, extra time would need to be allocated in the process of learning and adapting to new technologies to ensure all of the objectives are met in the constrained time frame.
+
+\subsection{Costs}
+There is no cost associated in the development of the product. The developers of Blaze Brigade will make best use of their personal computers for the main development environment, with the addition of already-owned tools such as Unreal Engine 4 and Adobe Photoshop.
+
+\subsection{User Documentation and Training}
+
+\subsubsection{Training Requirements}
+Ideally, an on-screen tutorial will be shown to first time users, and will guide them on how to interact with the game to meet its objectives. As the tutorial completes, the user will be directed to the story of the game. If time does not allow for this implementation, readable instructions will be added as a menu feature presented to the user upon game launch. In addition, instructions can be referenced later at any point of the game.
+
+\subsection{Waiting Room}
+No backlogged requirements are indicated at this stage of the project. This section will be updated as we proceed through the project planning phases.
+
+\subsection{Ideas for Solutions}
+No ideas for solution are indicated at this stage of the project. This section will be updated as we proceed through project planning phases.
+
+\end{document}
\ No newline at end of file