From 40f485af1bdcc04477a2cfcb71c899d397d7c6e6 Mon Sep 17 00:00:00 2001
From: Jaro <jarorutjes07@gmail.com>
Date: Wed, 18 Sep 2024 19:03:53 +0200
Subject: removed TODO and change some small typos

---
 plan.tex | 70 +++++++++++++++++++++-------------------------------------------
 1 file changed, 23 insertions(+), 47 deletions(-)

(limited to 'plan.tex')

diff --git a/plan.tex b/plan.tex
index 076ce11..2f9cc94 100644
--- a/plan.tex
+++ b/plan.tex
@@ -20,7 +20,7 @@
 This project is part of the fourth-year minor `Systems Programming in C++'. The minor
 consists of several courses troughout 20 weeks, which create the basis for this
 project. The project is focussed on building a game engine using the programming
-language C++. This document describes our plan of attack for the project.
+language C++. This document describes the plan of attack for the project.
 
 \section{Problem Definition}
 
@@ -34,7 +34,7 @@ language C++. This document describes our plan of attack for the project.
 \subsection{Problem Analysis}
 
 CodedFun Games is a small, single-person game company looking to scale up. The owner,
-who is also a game programmer, and graphical artist, has received government funding,
+who is a game programmer, and graphical artist, has received government funding,
 which he wants to invest in a custom-built game engine. The owner has no interest in
 developing or maintaining a game engine himself, so he has hired a part-time engine
 programmer. This programmer does not have time to create an entire engine but is
@@ -49,29 +49,19 @@ Therefore, he wants the new engine to adhere to a similar structure. A simple
 requirements document is defined to specify how strictly this structure should be
 followed.
 
-Finally, because the client does not want to dive deeply into the engine himself, he
-wants a secondary application (preferably a game) that can be used to test the
-engine's features. This is referred to as the \emph{validation application}.
+Finally, because the client does not want to dive deeply into the engine himself, he wants a secondary application (preferably a game) that can be used to test the engine's features. This is referred to as the \emph{validation application}.
 
 \subsection{Goal}
 
-The goal is to develop a custom game engine that meets the client's requirements for
-maintainability, extensibility, user-friendliness, and adherence to a Unity-like
-structure. In addition, a validation application should be created to show and test
-the engine's features.
+The goal is to develop a custom game engine that meets the client's requirements for maintainability, extensibility, user-friendliness, and adherence to a Unity-like structure. In addition, a validation application is created to show and test the engine's features.
 
 \subsection{Result}
 
-The expected result is a well-documented, custom game engine that follows a structure
-similar to Unity. Additionally, a validation application should be provided to test
-and showcase the engine's capabilities.
+The expected result is a well-documented, custom game engine that follows a structure similar to Unity. Additionally, a validation application should be provided to test and showcase the engine's capabilities.
 
 \section{Planning}
 
-The customer specified multiple deliverables troughout the 20 weeks of this project.
-Despite the fact that 20 weeks have been reserved for this project, the intention is
-that the game will be delivered in week 17. Any delay/resit will take place between
-weeks 17 and 20. A rough planning can be found in \cref{tab:planning}.
+The customer specified multiple deliverables throughout the 20 weeks of this project. Despite the fact that 20 weeks have been reserved for this project, the game will be delivered in week 17. Any delay/resit will take place between weeks 17 and 20. A rough planning can be found in \cref{tab:planning}.
 
 \begin{table}
 	\begin{tabularx}{\linewidth}{lX}
@@ -106,21 +96,20 @@ weeks 17 and 20. A rough planning can be found in \cref{tab:planning}.
 	\item[Scope Expansion] There is a risk of creating a scope that is bigger than the
 		requirements. Lack of Team Collaboration: Insufficient collaboration among team
 		members may hinder progress.
+	\item[Lack of Team Collaboration] Within the team a lack of collaboration can result in miscommunication or delay in work.
 \end{description}
 
 \subsection{Measures}
 
 \begin{description}
 	\item[Multiplatform] The team can switch any time to a single platform, so this
-		risk is metigated. 
+		risk is metigated.
 	\item[Integration] By following standards and having an integrator, which checks
 		every pull request, this risk is minimilised.
 	\item[Scope Expansion] By writing detailed requirements and having weekly team
 		meetings, to check if the progress is within the scope, should be sufficient to
 		decrease the risk.
-	\item[Lack of Team Collaboration] Weekly team meetings will result in collaboration
-		among team members and discussing what each other tasks is, will decease this
-		risk.
+	\item[Lack of Team Collaboration] Weekly team meetings will result in collaboration among team members and discussing what each other tasks is, will decease this risk.
 \end{description}
 
 \section{Documentation}
@@ -177,8 +166,8 @@ Each project member will keep track of their own working hours and add them to t
 
 \subsection{Absence or delay}
 
-If a project member is going to be absent or delayed, they are required to 
-notify the team through either WhatsApp or Outlook. Additionally, the teacher 
+If a project member is going to be absent or delayed, they are required to
+notify the team through either WhatsApp or Outlook. Additionally, the teacher
 should be informed of the absence as well.
 
 \subsection{Inconsistent participation}
@@ -200,9 +189,9 @@ will be necessary in such cases. However, if the inconsistency is due to other
 factors, potential repercussions may include additional assignments or actions as
 determined by the project supervisor.
 
-A team member is considered to have inconsistent participation if their hours 
-are significantly behind the team’s average or if tasks are not completed 
-without valid reasons. It is essential that any concerns regarding a team 
+A team member is considered to have inconsistent participation if their hours
+are significantly behind the team’s average or if tasks are not completed
+without valid reasons. It is essential that any concerns regarding a team
 member's performance, should be resolved through unanimous agreement within the team.
 
 \subsection{Weekly Update}
@@ -212,9 +201,9 @@ before 12:00 on Friday. Personal updates may also be included and will be
 confidential between the team member, the Team Leader, and/or the teacher, if
 requested.
 
-Jaro Rutjes will compile and send a team update to the project supervisor, Bob 
-van der Putten, also by Friday. This update will include technical information 
-on what has been accomplished, plans for upcoming work, and an overview of the 
+Jaro Rutjes will compile and send a team update to the project supervisor, Bob
+van der Putten, also by Friday. This update will include technical information
+on what has been accomplished, plans for upcoming work, and an overview of the
 team's overall progress.
 
 \subsection{Weekly Meetings}
@@ -230,8 +219,7 @@ project needs.
 % Information about how and when Scrum will be used in this project (using Miro).
 \section{Scrum (Miro)}
 
-The team will start using scrum after the initial phase, of structering the project,
-is finished. This phase is over when proof of concepts are being made.
+The team starts using scrum after the initial phase, of structering the project, is finished. This phase is finished after a initial design of the product is made.
 
 \subsection{Scrum Board}
 
@@ -257,26 +245,22 @@ To manage tasks effectively:
 
 \begin{itemize}
 	\item A task from the \emph{Current Sprint} tab should be selected and moved to the
-		\emph{In Progress} tab when work begins. 
+		\emph{In Progress} tab when work begins.
 	\item The status of the task should be updated to \emph{In Progress} as soon as
 		work starts.
 	\item Once the task is completed and reviewed, it should be moved to the
 		\emph{Done} tab, and its status should be updated to \emph{Done}.
 \end{itemize}
 
-Each task or user story will be assigned user points, which indicate the relative
-size or complexity of the task compared to these examples.
-% TODO: add examples
+Each task or user story will be assigned user points, which indicate the relative size or complexity of the task. Examples of certain tasks will be available in the scrumboard.
 
 \subsection{Burn Down Chart}
 
 The Burn Down Chart will be generated using Excel from the Scrum board data every
 week. Each user story or task marked as done, will burn the chart downwards. This
-Burn Down Chart is shared in the weekly updates with the team and the project
-supervisor.
+Burn Down Chart is shared in the weekly updates with the team.
 
 % Information regarding the git workflow of this project.
-% TODO: Diagram explaining the workflow
 \section{Git Workflow}
 
 GitHub is used for version management of both code \autocite{crepe:code-repo} and
@@ -284,16 +268,8 @@ documentation \autocite{crepe:docs-repo}, each in its own respective repository.
 keeps the documentation and code seperate, resulting in ordened and manageable
 repositories.
 
-\subsection{Git New Branch}
+\subsection{Code Standard and git workflow}
 
-% TODO: add here details from contributing.md?
-
-\subsection{Git Merge To Master}
-
-% TODO: add here diagram on what actions are taken before merge.
-
-\subsection{Code Standard}
-
-The code standard can be found in the contributing.md \autocite{crepe:code-standard}.
+The code standard and the git workflow can be found in the contributing.md \autocite{crepe:code-standard}.
 
 \end{document}
-- 
cgit v1.2.3


From 28d0733146aa3a8ba720bda20ff66ffa4cf4e64d Mon Sep 17 00:00:00 2001
From: Jaro <jarorutjes07@gmail.com>
Date: Wed, 18 Sep 2024 19:30:48 +0200
Subject: added feedback to project plan

---
 plan.tex    | 5 ++++-
 sources.bib | 7 +++++++
 2 files changed, 11 insertions(+), 1 deletion(-)

(limited to 'plan.tex')

diff --git a/plan.tex b/plan.tex
index 2f9cc94..147e49c 100644
--- a/plan.tex
+++ b/plan.tex
@@ -53,7 +53,10 @@ Finally, because the client does not want to dive deeply into the engine himself
 
 \subsection{Goal}
 
-The goal is to develop a custom game engine that meets the client's requirements for maintainability, extensibility, user-friendliness, and adherence to a Unity-like structure. In addition, a validation application is created to show and test the engine's features.
+The goal is to develop a custom game engine that meets the client's requirements for maintainability, extensibility, user-friendliness, and adherence to a Unity-like structure. The engine may integrate third-party software (as agreed with the client) to support specific features, such as audio, physics, and rendering. In addition, a validation application is created to show and test the engine's features.
+
+\subsection{Scope}
+The requirements document \autocite{crepe:requirements} has several requirements with a MoSCoW `must', `should', `could' or `won't' priority to indicate the project's scope.
 
 \subsection{Result}
 
diff --git a/sources.bib b/sources.bib
index 50f5ead..8d96ce1 100644
--- a/sources.bib
+++ b/sources.bib
@@ -47,4 +47,11 @@
   date = {2024-09-10},
 }
 
+@misc{crepe:requirements,
+  author = {Loek Le Blansch and Wouter Boerenkamps and Jaro Rutjes and Max Smits and Niels Stunnebrink},
+  title = {Requirements},
+  url = {https://github.com/lonkaars/crepe/blob/master/requirements.pdf},
+  date = {2024-09-10},
+}
+
 
-- 
cgit v1.2.3


From be63aadea11619a08878c25a26b7ccafc6174b53 Mon Sep 17 00:00:00 2001
From: Jaro <jarorutjes07@gmail.com>
Date: Thu, 19 Sep 2024 18:10:43 +0200
Subject: added some feedback

---
 plan.tex    | 32 +++++++++++---------------------
 sources.bib |  7 +++++++
 2 files changed, 18 insertions(+), 21 deletions(-)

(limited to 'plan.tex')

diff --git a/plan.tex b/plan.tex
index 147e49c..13c487d 100644
--- a/plan.tex
+++ b/plan.tex
@@ -1,13 +1,6 @@
 \documentclass{projdoc}
 \input{meta.tex}
 
-% @Jaro: Zie hieronder
-% Version 0.0 seems not right
-% I'm also missing a 'version table'
-% Shall we use this version system?:
-% Version numbers after the comma indicate an interim version and version numbers
-% before the comma indicate versions ready for publication
-
 \title{Project Plan}
 \version{0.1}
 
@@ -18,19 +11,12 @@
 \section{Background}
 
 This project is part of the fourth-year minor `Systems Programming in C++'. The minor
-consists of several courses troughout 20 weeks, which create the basis for this
-project. The project is focussed on building a game engine using the programming
+consists of several courses throughout 20 weeks, which create the basis for this
+project. The project focus is on building a game engine using the programming
 language C++. This document describes the plan of attack for the project.
 
 \section{Problem Definition}
 
-% The assignments will be discussed with the project supervisor on specifics for this
-% project. This will give the team the ability to direct the project.
-
-% @Jaro: Ik snap niet wat je met deze zinnen wil zeggen. Het lijkt een soort van
-% background information, maar toch niet helemaal ofzo. Hoe dan ook heb ik het er nu
-% even uit gehaald en een nieuw kopje background toegevoegd.
-
 \subsection{Problem Analysis}
 
 CodedFun Games is a small, single-person game company looking to scale up. The owner,
@@ -45,7 +31,7 @@ user-friendly. Additionally, the engine should be well-documented, which is
 considered an essential aspect of being user-friendly.
 
 So far, the client has made all his games in Unity and is very fond of the structure.
-Therefore, he wants the new engine to adhere to a similar structure. A simple
+Therefore, the client wants the new engine to adhere to a similar structure. A simple
 requirements document is defined to specify how strictly this structure should be
 followed.
 
@@ -62,6 +48,10 @@ The requirements document \autocite{crepe:requirements} has several requirements
 
 The expected result is a well-documented, custom game engine that follows a structure similar to Unity. Additionally, a validation application should be provided to test and showcase the engine's capabilities.
 
+\subsection{validation application}
+
+The validation application \autocite{crepe:validation-application} is explained in a document where the features of the validation application are linked to the user stories.
+
 \section{Planning}
 
 The customer specified multiple deliverables throughout the 20 weeks of this project. Despite the fact that 20 weeks have been reserved for this project, the game will be delivered in week 17. Any delay/resit will take place between weeks 17 and 20. A rough planning can be found in \cref{tab:planning}.
@@ -72,10 +62,9 @@ The customer specified multiple deliverables throughout the 20 weeks of this pro
 		\textbf{Week\#} & \textbf{Deliverable}\\
 		\midrule
 		4 & Project Plan\\
-		7 & Requirements document\\
+		7 & POCs\\
 		10 & POCs and Design document\\
-		17 & Game engine, Validation application, Research document, and Qualification
-		document\\
+		17 & Game engine, Validation application\\
 		\bottomrule
 	\end{tabularx}
 	\caption{Planning}
@@ -100,6 +89,7 @@ The customer specified multiple deliverables throughout the 20 weeks of this pro
 		requirements. Lack of Team Collaboration: Insufficient collaboration among team
 		members may hinder progress.
 	\item[Lack of Team Collaboration] Within the team a lack of collaboration can result in miscommunication or delay in work.
+	\item[Falling out of specific team member] Within the team the scrum master and integrator have additional roles. If one or both members can not continue it can hinder progress of the project.
 \end{description}
 
 \subsection{Measures}
@@ -113,6 +103,7 @@ The customer specified multiple deliverables throughout the 20 weeks of this pro
 		meetings, to check if the progress is within the scope, should be sufficient to
 		decrease the risk.
 	\item[Lack of Team Collaboration] Weekly team meetings will result in collaboration among team members and discussing what each other tasks is, will decease this risk.
+	\item[Falling out of specific team member] The scrum master can be taken over by any other team member. All tools (e.g. scrum board) are open to all members. The tasks of the integrator can be taken over by the team. Within GitHub the team as a whole has the same rights as the integrator.
 \end{description}
 
 \section{Documentation}
@@ -128,7 +119,6 @@ This project consists of seven main documents:\noparbreak
 		project, including timelines, milestones, roles, and responsibilities.
 	\item[Requirements] Details the requirements and user stories, including both
 		functional and non-functional requirements.
-	\item[Research] Consists of all research related to this project.
 	\item[Design] Describes the design choices, including architecture, user interface,
 		and system components.
 	\item[Qualification] Includes test cases, test plans, and quality measures to
diff --git a/sources.bib b/sources.bib
index 8d96ce1..31262fb 100644
--- a/sources.bib
+++ b/sources.bib
@@ -54,4 +54,11 @@
   date = {2024-09-10},
 }
 
+@misc{crepe:validation-application,
+  author = {Loek Le Blansch and Wouter Boerenkamps and Jaro Rutjes and Max Smits and Niels Stunnebrink},
+  title = {Validation Application},
+  url = {https://github.com/lonkaars/crepe/blob/master/Validation-Application.pdf},
+  date = {2024-09-10},
+}
+
 
-- 
cgit v1.2.3


From 3c6a635c6a8d38aae2284cbe744c060e765968a6 Mon Sep 17 00:00:00 2001
From: Jaro <jarorutjes07@gmail.com>
Date: Thu, 19 Sep 2024 18:13:16 +0200
Subject: removed qualification

---
 plan.tex | 2 --
 1 file changed, 2 deletions(-)

(limited to 'plan.tex')

diff --git a/plan.tex b/plan.tex
index 74f6a2b..54cc9d6 100644
--- a/plan.tex
+++ b/plan.tex
@@ -120,8 +120,6 @@ This project consists of seven main documents:\noparbreak
 		functional and non-functional requirements.
 	\item[Design] Describes the design choices, including architecture, user interface,
 		and system components.
-	\item[Qualification] Includes test cases, test plans, and quality measures to
-		ensure the project meets its requirements and standards.
 	\item[Working hours] A table which includes all working hours of each team member.
 	\item[API Reference] Details the available endpoints, request and response formats,
 		authentication methods, error codes, and examples for interacting with the
-- 
cgit v1.2.3


From 23ceaf0edc1db82240740dbcc6d305d1e10726c8 Mon Sep 17 00:00:00 2001
From: Jaro <jarorutjes07@gmail.com>
Date: Thu, 19 Sep 2024 18:37:07 +0200
Subject: changed role max

---
 plan.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'plan.tex')

diff --git a/plan.tex b/plan.tex
index 54cc9d6..a1cbb15 100644
--- a/plan.tex
+++ b/plan.tex
@@ -145,7 +145,7 @@ reviewed and agreed to these terms.
 	\item[Loek Le Blansch] Integrator
 	\item[Wouter Boerenkamps] Project Member
 	\item[Jaro Rutjes] Team Leader / Scrum Master
-	\item[Max Smits] Project Member
+	\item[Max Smits] Project Member / Product owner
 	\item[Niels Stunnebrink] Project Member
 \end{description}
 
-- 
cgit v1.2.3


From 77c9588359df6a72097e46074b1ff14f80350285 Mon Sep 17 00:00:00 2001
From: heavydemon21 <nielsstunnebrink1@gmail.com>
Date: Thu, 19 Sep 2024 20:02:17 +0200
Subject: Read through the plan.tex and fixed some issues

---
 plan.tex | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

(limited to 'plan.tex')

diff --git a/plan.tex b/plan.tex
index a1cbb15..11d8d41 100644
--- a/plan.tex
+++ b/plan.tex
@@ -72,10 +72,10 @@ The customer specified multiple deliverables throughout the 20 weeks of this pro
 
 \section{Risks}
 
-\subsection{Techincal Risks}
+\subsection{Technical Risks}
 
 \begin{description}
-	\item[Multiplatform] The team works in both linux and windows, which poses a risk
+	\item[Multiplatform] The team works in both Linux and windows, which poses a risk
 		for the development if there is a platform dependency.
 	\item[Integration] Users can make a wrong integration causing for delay or risk of
 		losing code.
@@ -95,9 +95,9 @@ The customer specified multiple deliverables throughout the 20 weeks of this pro
 
 \begin{description}
 	\item[Multiplatform] The team can switch any time to a single platform, so this
-		risk is metigated.
+		risk is mitigated.
 	\item[Integration] By following standards and having an integrator, which checks
-		every pull request, this risk is minimilised.
+		every pull request, this risk is minimized.
 	\item[Scope Expansion] By writing detailed requirements and having weekly team
 		meetings, to check if the progress is within the scope, should be sufficient to
 		decrease the risk.
@@ -209,7 +209,7 @@ project needs.
 % Information about how and when Scrum will be used in this project (using Miro).
 \section{Scrum (Miro)}
 
-The team starts using scrum after the initial phase, of structering the project, is finished. This phase is finished after a initial design of the product is made.
+The team starts using scrum after the initial phase, of structuring the project, is finished. This phase is finished after a initial design of the product is made.
 
 \subsection{Scrum Board}
 
@@ -255,7 +255,7 @@ Burn Down Chart is shared in the weekly updates with the team.
 
 GitHub is used for version management of both code \autocite{crepe:code-repo} and
 documentation \autocite{crepe:docs-repo}, each in its own respective repository. This
-keeps the documentation and code seperate, resulting in ordened and manageable
+keeps the documentation and code separate, resulting in ordered and manageable
 repositories.
 
 \subsection{Code Standard and git workflow}
-- 
cgit v1.2.3


From dcd17e39494010e3696f8e6b935e2da1d63ea37a Mon Sep 17 00:00:00 2001
From: Max-001 <80035972+Max-001@users.noreply.github.com>
Date: Fri, 20 Sep 2024 10:22:07 +0200
Subject: Corrected cappital letters

---
 plan.tex | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

(limited to 'plan.tex')

diff --git a/plan.tex b/plan.tex
index 11d8d41..55707ce 100644
--- a/plan.tex
+++ b/plan.tex
@@ -47,7 +47,7 @@ The requirements document \autocite{crepe:requirements} has several requirements
 
 The expected result is a well-documented, custom game engine that follows a structure similar to Unity. Additionally, a validation application should be provided to test and showcase the engine's capabilities.
 
-\subsection{validation application}
+\subsection{Validation Application}
 
 The validation application \autocite{crepe:validation-application} is explained in a document where the features of the validation application are linked to the user stories.
 
@@ -61,7 +61,7 @@ The customer specified multiple deliverables throughout the 20 weeks of this pro
 		\textbf{Week\#} & \textbf{Deliverable}\\
 		\midrule
 		4 & Project Plan\\
-		7 & POCs\\
+		7 & Some POCs\\
 		10 & POCs and Design document\\
 		17 & Game engine, Validation application\\
 		\bottomrule
@@ -139,7 +139,7 @@ protocols for handling absences or delays, guidelines for addressing inconsisten
 participation, and procedures for weekly updates and meetings. All team members
 reviewed and agreed to these terms.
 
-\subsection{Project roles}
+\subsection{Project Roles}
 
 \begin{description}
 	\item[Loek Le Blansch] Integrator
@@ -149,18 +149,18 @@ reviewed and agreed to these terms.
 	\item[Niels Stunnebrink] Project Member
 \end{description}
 
-\subsection{Work hours}
+\subsection{Work Hours}
 
 Each project member will keep track of their own working hours and add them to the
 `file'.
 
-\subsection{Absence or delay}
+\subsection{Absence or Delay}
 
 If a project member is going to be absent or delayed, they are required to
 notify the team through either WhatsApp or Outlook. Additionally, the teacher
 should be informed of the absence as well.
 
-\subsection{Inconsistent participation}
+\subsection{Inconsistent Participation}
 
 Inconsistent participation will be addressed in a structured manner:
 
@@ -258,7 +258,7 @@ documentation \autocite{crepe:docs-repo}, each in its own respective repository.
 keeps the documentation and code separate, resulting in ordered and manageable
 repositories.
 
-\subsection{Code Standard and git workflow}
+\subsection{Code Standard and Git Workflow}
 
 The code standard and the git workflow can be found in the contributing.md \autocite{crepe:code-standard}.
 
-- 
cgit v1.2.3


From f55937c99dfdd08d89d3d7db24780d42b9f4ea75 Mon Sep 17 00:00:00 2001
From: Max-001 <80035972+Max-001@users.noreply.github.com>
Date: Fri, 20 Sep 2024 12:03:16 +0200
Subject: Last minor changes

---
 plan.tex | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

(limited to 'plan.tex')

diff --git a/plan.tex b/plan.tex
index 55707ce..c439aa7 100644
--- a/plan.tex
+++ b/plan.tex
@@ -38,18 +38,18 @@ Finally, because the client does not want to dive deeply into the engine himself
 
 \subsection{Goal}
 
-The goal is to develop a custom game engine that meets the client's requirements for maintainability, extensibility, user-friendliness, and adherence to a Unity-like structure. The engine may integrate third-party software (as agreed with the client) to support specific features, such as audio, physics, and rendering. In addition, a validation application is created to show and test the engine's features.
+The goal is to develop a custom game engine that meets the client's requirements for maintainability, extensibility, user-friendliness, and adherence to a Unity-like structure. The engine may integrate third-party software (as agreed with the client) to support specific features, such as audio, physics, and rendering. In addition, a \emph{validation application} is created to show and test the engine's features.
 
 \subsection{Scope}
 The requirements document \autocite{crepe:requirements} has several requirements with a MoSCoW `must', `should', `could' or `won't' priority to indicate the project's scope.
 
 \subsection{Result}
 
-The expected result is a well-documented, custom game engine that follows a structure similar to Unity. Additionally, a validation application should be provided to test and showcase the engine's capabilities.
+The expected result is a well-documented, custom game engine that follows a structure similar to Unity. Additionally, a \emph{validation application} should be provided to test and showcase the engine's capabilities.
 
 \subsection{Validation Application}
 
-The validation application \autocite{crepe:validation-application} is explained in a document where the features of the validation application are linked to the user stories.
+The \emph{validation application} \autocite{crepe:validation-application} is explained in a document where the features of the \emph{validation application} are linked to the user stories.
 
 \section{Planning}
 
@@ -63,7 +63,7 @@ The customer specified multiple deliverables throughout the 20 weeks of this pro
 		4 & Project Plan\\
 		7 & Some POCs\\
 		10 & POCs and Design document\\
-		17 & Game engine, Validation application\\
+		17 & Game engine, \emph{validation application}\\
 		\bottomrule
 	\end{tabularx}
 	\caption{Planning}
@@ -145,7 +145,7 @@ reviewed and agreed to these terms.
 	\item[Loek Le Blansch] Integrator
 	\item[Wouter Boerenkamps] Project Member
 	\item[Jaro Rutjes] Team Leader / Scrum Master
-	\item[Max Smits] Project Member / Product owner
+	\item[Max Smits] Project Member / Product Owner
 	\item[Niels Stunnebrink] Project Member
 \end{description}
 
-- 
cgit v1.2.3


From 6329755a372d90985bda1cd164fae8d91d4a60c6 Mon Sep 17 00:00:00 2001
From: Loek Le Blansch <loek@pipeframe.xyz>
Date: Thu, 26 Sep 2024 15:50:58 +0200
Subject: remove meta.tex and just set defaults directly in projdoc.cls

---
 example.tex      |  1 -
 meta.tex         |  9 ---------
 plan.tex         |  1 -
 projdoc.cls      | 15 +++++++++++++--
 requirements.tex |  1 -
 research.tex     |  1 -
 timerep.tex      |  1 -
 7 files changed, 13 insertions(+), 16 deletions(-)
 delete mode 100644 meta.tex

(limited to 'plan.tex')

diff --git a/example.tex b/example.tex
index 24c525b..9f36f59 100644
--- a/example.tex
+++ b/example.tex
@@ -1,7 +1,6 @@
 \documentclass{projdoc}
 % if the document compiles too slow (likely due to many/large images), try compiling
 % with the [draft] option. this replaces all images with placeholders.
-\input{meta.tex}
 
 \title{Example Document}
 
diff --git a/meta.tex b/meta.tex
deleted file mode 100644
index db7c7b1..0000000
--- a/meta.tex
+++ /dev/null
@@ -1,9 +0,0 @@
-\organization{Avans University of Applied Sciences}
-\project{Project cr\^epe}
-\author{%
-	Loek Le Blansch\and%
-	Wouter Boerenkamps\and%
-	Jaro Rutjes\and%
-	Max Smits\and%
-	Niels Stunnebrink%
-}
diff --git a/plan.tex b/plan.tex
index c439aa7..a67598e 100644
--- a/plan.tex
+++ b/plan.tex
@@ -1,5 +1,4 @@
 \documentclass{projdoc}
-\input{meta.tex}
 
 \title{Project Plan}
 
diff --git a/projdoc.cls b/projdoc.cls
index 16b1790..8a2c05d 100644
--- a/projdoc.cls
+++ b/projdoc.cls
@@ -1,6 +1,19 @@
 \NeedsTeXFormat{LaTeX2e}
 \ProvidesClass{projdoc}[2024-09-03 class projdoc]
 
+% project defaults
+\makeatletter
+\def\@project{Project cr\^epe}
+\def\@organization{Avans University of Applied Sciences}
+\def\@author{%
+	Loek Le Blansch\and%
+	Wouter Boerenkamps\and%
+	Jaro Rutjes\and%
+	Max Smits\and%
+	Niels Stunnebrink%
+}
+\makeatother
+
 % based on article
 \LoadClass{article}
 
@@ -160,9 +173,7 @@
 
 % \maketitle format
 \makeatletter
-\let\@project\relax
 \def\project#1{\def\@project{#1}}
-\let\@organization\relax
 \def\organization#1{\def\@organization{#1}}
 \def\@maketitle{%
 	\centering%
diff --git a/requirements.tex b/requirements.tex
index be0e103..6b4a87a 100644
--- a/requirements.tex
+++ b/requirements.tex
@@ -1,5 +1,4 @@
 \documentclass{projdoc}
-\input{meta.tex}
 
 \makeatletter
 \projdoc@description@leftmargin=2ex
diff --git a/research.tex b/research.tex
index 228f3ac..5aa7c4f 100644
--- a/research.tex
+++ b/research.tex
@@ -1,5 +1,4 @@
 \documentclass{projdoc}
-\input{meta.tex}
 
 \title{Research document}
 
diff --git a/timerep.tex b/timerep.tex
index 7590217..34a30ea 100644
--- a/timerep.tex
+++ b/timerep.tex
@@ -1,5 +1,4 @@
 \documentclass{projdoc}
-\input{meta.tex}
 
 \title{Time Report}
 
-- 
cgit v1.2.3

