diff --git a/pub/dissertation/chapters/conclusion.tex b/pub/dissertation/chapters/conclusion.tex
index 9c9896e..930be58 100644
--- a/pub/dissertation/chapters/conclusion.tex
+++ b/pub/dissertation/chapters/conclusion.tex
@@ -45,6 +45,8 @@
   \end{itemize}
   \item Objective 2.a. was met to an extent
   \begin{itemize}
+    \item Currently, the states of the aircraft monitored are only
+      the actions specified in the test, in the checklist tester
     \item There could be more variables that could be monitored. Such
       as engine fire, could monitor the engine temperature or thrust
       produced by engine
@@ -52,8 +54,10 @@
       as checklists does have a bit of logic like if statements,
       for example \enquote{If APU is available, then do \ldots else do \ldots}
   \end{itemize}
-  \item Objective 2.b was also met to an extent
+  \item Objective 2.b. was also met to an extent
   \begin{itemize}
+    \item Currently, this can be met by re-running the test multiple
+      times manually
     \item However, it is manual at this stage due to limitations of XPC
       and setting up the aircraft
     \item The test data is stored on the database, hence test results
@@ -67,6 +71,47 @@
 
 
 \section{What Next}
+The most important next steps to implement would be
+linking the formal mode, adding options of what parts of the aircraft
+to monitor
+
+\begin{itemize}
+  \item Formal Model
+  \begin{itemize}
+    \item Implemented either by creating an automatic wrapper.
+      Done by either potentially linking the VDMJ LSP, or creating a
+      plugin for VDMJ
+    \item Or doing string manipulation on the VDM results for each of the
+      functions as a lot of it is copy and paste - can be bad practice as
+      it requires a lot of hard-coded code
+  \end{itemize}
+  \item Monitoring more of the aircraft
+  \begin{itemize}
+    \item Done by adding options in the Checklist Tester for extra
+      Datarefs to monitor
+    \item Modifying the \lstinline|Aircraft| record type to include a
+      states type that checks multiple times throughout the procedure
+      if this state has violated a constraint or if the goal of the
+      state has been achieved (e.g. Engine is no longer on fire)
+  \end{itemize}
+  \item Expanding out of the scope of the objectives,
+    adding logic, such as the if statements to the checklist
+    would be the next logical step
+  \begin{itemize}
+    \item VDM-SL would be really helpful for this, as can be used to
+      design logic to be used outside of Kotlin
+    \item This would allow for further automation of checklists,
+      rather than only testing linearly, which at this current state
+      would require writing the test multiple times
+  \end{itemize}
+  \item Adding more detailed test results
+  \begin{itemize}
+    \item Use analysis of previous test results to gain an understanding
+      of the reproducibility of the procedure
+    \item Keep track of aircraft state, such as speed or altitude
+      aiding in understanding if the procedure may impose a safety risk 
+  \end{itemize}
+\end{itemize}
 
 
 \end{document}
diff --git a/pub/dissertation/dissertation.pdf b/pub/dissertation/dissertation.pdf
index 80f11bd..cfec228 100644
Binary files a/pub/dissertation/dissertation.pdf and b/pub/dissertation/dissertation.pdf differ
diff --git a/pub/dissertation/dissertation.sum b/pub/dissertation/dissertation.sum
index 928819e..e2f5cf7 100644
--- a/pub/dissertation/dissertation.sum
+++ b/pub/dissertation/dissertation.sum
@@ -1 +1 @@
-4345
+4626