diff --git a/BlankProjectTemplate/Doc/Design/MG/MG.pdf b/BlankProjectTemplate/Doc/Design/MG/MG.pdf
index a0cd8861f84e1521832e3ae7f79e07a27c0ecec0..56b85d6ca5bf5750757f5e4631bc8ce3d9863aef 100644
Binary files a/BlankProjectTemplate/Doc/Design/MG/MG.pdf and b/BlankProjectTemplate/Doc/Design/MG/MG.pdf differ
diff --git a/BlankProjectTemplate/Doc/Design/MG/MG.tex b/BlankProjectTemplate/Doc/Design/MG/MG.tex
index afd5d8da62f907ad4960bb353419804141c3f693..18b631393c0801508d34bb37e5ce1f9e2fe53ee7 100644
--- a/BlankProjectTemplate/Doc/Design/MG/MG.tex
+++ b/BlankProjectTemplate/Doc/Design/MG/MG.tex
@@ -399,21 +399,12 @@ AC7 & M2\\
 
 \section{Use Hierarchy Between Modules} \label{SecUse}
 
-In this section, the uses hierarchy between modules is
-provided. \citet{Parnas1978} said of two programs A and B that A {\em uses} B if
-correct execution of B may be necessary for A to complete the task described in
-its specification. That is, A {\em uses} B if there exist situations in which
-the correct functioning of A depends upon the availability of a correct
-implementation of B.  Figure \ref{FigUH} illustrates the use relation between
-the modules. It can be seen that the graph is a directed acyclic graph
-(DAG). Each level of the hierarchy offers a testable and usable subset of the
-system, and modules in the higher level of the hierarchy are essentially simpler
-because they use modules from the lower levels.
 
 \begin{figure}[H]
 \centering
-%\includegraphics[width=0.7\textwidth]{UsesHierarchy.png}
+%\includegraphics[width=0.7\textwidth]{Use_Hierarchy.png}
 \caption{Use hierarchy among modules}
+\includegraphics{Use_Heirarchy}
 \label{FigUH}
 \end{figure}
 
diff --git a/BlankProjectTemplate/Doc/Design/MG/Use_Heirarchy.jpg b/BlankProjectTemplate/Doc/Design/MG/Use_Heirarchy.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..30cf8d1189bfea988b30364cf388c26f3fb582f9
Binary files /dev/null and b/BlankProjectTemplate/Doc/Design/MG/Use_Heirarchy.jpg differ