Update development plan

Doc/DevelopmentPlan/DevelopmentPlan.tex

@@ -62,38 +62,86 @@ Saif Fadhel\\
 }
 \date{\submissionDate{}}
 
+
+
 \begin{document}
+\vspace*{\fill}
+\begin{table}[hp]
+\centering
+\caption{Revision History} \label{TblRevisionHistory}
+\begin{tabularx}{\textwidth}{llX}
+\toprule
+\textbf{Date} & \textbf{Developer(s)} & \textbf{Change}\\
+\midrule
+Feb. 04 & All Team Members & Create and review document\\
+\bottomrule
+\end{tabularx}
+\end{table}
+\vspace*{\fill}
+
+
+\newpage
+
 \maketitle
 \thispagestyle{empty}
 \pagebreak
 
-Put your introductory blurb here.
+\noindent Today's virtual currencies, such as cryptocurrencies or other digital currencies, have significantly changed the way we view the concept of money. There is a growing interest in crypto worldwide, but without any knowledge of the projected trends, it is easy to make uneducated investments and lose hard earned money. Our proposed project, CryptoMetrics, will help users make more educated investments by providing a dashboard that displays historical and real-time cryptocurrency prices.
 
 \section{Team Meeting Plan}
-\noindent The team will be meeting virtually two times a week for two hours during the 3XA3 lab times, using either Discord or Microsoft Teams. If more time is needed to discuss specific issues, Discord will be used to schedule additional meetings amongst the team members.
+\noindent The team will be meeting virtually two times a week for two hours during the 3XA3 lab times, either virtually using Discord or Microsoft Teams, or in-person in ITB 236. If more time is needed to discuss specific issues, Discord will be used to schedule additional meetings amongst the team members. The meeting roles for roles each team member are described as follows: \\
+
+\begin{table}[h!]
+    \centering
+    \begin{tabular}{|c|c|}
+    \hline
+    \multicolumn{1}{|c|}{Name}              & \multicolumn{1}{c|}{Role}                \\ \hline
+    \multicolumn{1}{|c|}{Himanshu Aggarwal} & \multicolumn{1}{c|}{Meeting Chairperson} \\ \hline
+    Saif Fadhel                             & Meeting Facilitator                      \\ \hline
+    Vanshaj Verma                           & Meeting Minute-Taker                     \\ \hline
+    \end{tabular}
+    \caption{Meeting Roles}
+\end{table}
 
 \section{Team Communication Plan}
 \noindent The team has decided to use a Discord server for all communication related to this project. This allows for creation of multiple channels within the server to discuss different tasks that need to be completed. If needed, the group will be using Microsoft Teams and Emails to communicate to the TAs and the professor. The group will also use git issues to track and assign any issues within the project. 
-
+\newpage 
 \section{Team Member Roles}
-
+\noindent The following table lists the roles of the members of the group:
+
+\begin{table}[hbt!]
+    \centering
+    \begin{tabular}{|c|c|c|}
+    \hline
+    Name              & Role                                                                                           & Expertise                                                            \\ \hline
+    Himanshu Aggarwal & \begin{tabular}[c]{@{}c@{}}Software Developer\\ Meeting Chairperson\end{tabular}               & \begin{tabular}[c]{@{}c@{}}Gantt\\ JavaScript\\ ReactJS\end{tabular} \\ \hline
+    Saif Fadhel       & \begin{tabular}[c]{@{}c@{}}Software Developer\\ Meeting Facilitator\\ Team Leader\end{tabular} & \begin{tabular}[c]{@{}c@{}}LaTeX \\ JavaScript\end{tabular}          \\ \hline
+    Vanshaj Verma     & \begin{tabular}[c]{@{}c@{}}Software Developer\\ Meeting Minute-Taker / Scribe\end{tabular}     & \begin{tabular}[c]{@{}c@{}}Git\\ JavaScript\end{tabular}             \\ \hline
+    \end{tabular}
+    \caption{Team Member Roles}
+\end{table}
 
 \section{Git Workflow Plan}
+\noindent The team will use GitLab as a version control platform, and each individual team member will commit their initial changes to separate branches. The code will be tested and verified before merging into the \texttt{main} development branch to be approved by a merge request. Upon completion of the assigned deliverable, the final commit will be tagged in order to specify the version of the deliverable to be marked by TAs.
 
 \section{Proof of Concept Demonstration Plan}
+\noindent Implementing the data visualization charts for the historical time series data might be a challenge but we plan on researching how to properly implement them using \texttt{Echarts}. Testing will not be difficult because \texttt{Jest}, \texttt{React Testing Library} and \texttt{Cypress} provide easy ways to create and run tests. The required libraries can be easily installed via a Node Package Manager like \texttt{npm} and \texttt{yarn}. Portability is also not a concern as React supports all major browsers including Chrome, Safari, Firefox, etc.\\
+\newline
+\noindent We plan to demonstrate a working prototype of some of the tools we intend to implement. Our demonstration will include charts for data visualization and comparison, and tables for real-time aggregate data related to cryptocurrencies.
+
 
 \section{Technology}
-\noindent The project will use JavaScript as the primary programming language, along with HTML and CSS for the design. A JavaScript framework called 'NextJS' will be used as the frontend framework. (...add details about testing and documentation tools)
+\noindent The project will use JavaScript as the primary programming language, along with HTML and CSS for the design. A React framework called \href{https://nextjs.org/}{NextJS} will be used as the frontend framework, along with JavaScript libraries like \href{https://react-query.tanstack.com/}{React Query} and \href{https://axios-http.com/docs/intro}{Axios} for fetching data and managing state. Libraries like \href{https://echarts.apache.org/en/index.html}{Echarts} and \href{https://apexcharts.com/}{ApexCharts} will be used to create data visualizations. Popular text editors like \href{https://atom.io/}{Atom} and \href{https://code.visualstudio.com/}{Visual Studio Code} will be used to add and modify code. \href{https://jestjs.io/}{Jest} and \href{https://github.com/testing-library/react-testing-library}{React Testing Library} will be used for Unit Testing, and \href{https://www.cypress.io/}{Cypress} will be used for End-to-End (E2E) and Integration Testing. The project will use {\href{https://github.com/reactjs/react-docgen}{reactjs/react-docgen}} for document generation.
 
 \section{Coding Style}
+\noindent The project will adhere to \href{https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide}{Mozilla's JavaScript Guide} as the coding standard to ensure consistency.
 
 \section{Project Schedule}
-
-Provide a pointer to your Gantt Chart.
+\noindent The project schedule can be found \href{https://gitlab.cas.mcmaster.ca/webapp/webapp_l02_grp15/-/tree/main/ProjectSchedule}{here}.
 
 \section{Project Review}
 
 
- \end{document}
+\end{document}