All compile as papers and thesis now.

This commit is contained in:
Robin Clark 2010-12-05 13:17:04 +00:00
parent 001b77c49f
commit ad0c94d3d0
2 changed files with 13 additions and 4 deletions

View File

@ -868,7 +868,7 @@ This is represented in UML in figure \ref{fig:componentconcept}.
\begin{figure}[h] \begin{figure}[h]
\centering \centering
\includegraphics[width=200pt,keepaspectratio=true]{./component.jpg} \includegraphics[width=200pt,keepaspectratio=true]{./fmmd_concept/component.jpg}
% component.jpg: 467x76 pixel, 72dpi, 16.47x2.68 cm, bb=0 0 467 76 % component.jpg: 467x76 pixel, 72dpi, 16.47x2.68 cm, bb=0 0 467 76
\caption{Component with failure modes UML diagram} \caption{Component with failure modes UML diagram}
\label{fig:componentconcept} \label{fig:componentconcept}
@ -1052,13 +1052,13 @@ of A multiplied by the probability of Q).
If we wish to dynamically model the conditional failure If we wish to dynamically model the conditional failure
an attribute to the failure~modes must be added an attribute to the failure~modes must be added
that can reference other failure~modes and environmental conditions. that can reference other failure~modes and environmental conditions.
An UML diagram with inhibit conditions added is shown in figure \ref{fig:uml2concept}. An UML diagram with inhibit conditions added is shown in figure \ref{fig:umlconcept2}.
% UML DIAGRAM % UML DIAGRAM
\begin{figure}[h] \begin{figure}[h]
\centering \centering
\includegraphics[width=400pt,keepaspectratio=true]{./fmmd_env_op_uml2.jpg} \includegraphics[width=400pt,keepaspectratio=true]{./fmmd_concept/fmmd_env_op_uml2.jpg}
% fmmd_env_op_uml2.jpg: 866x313 pixel, 72dpi, 30.55x11.04 cm, bb=0 0 866 313 % fmmd_env_op_uml2.jpg: 866x313 pixel, 72dpi, 30.55x11.04 cm, bb=0 0 866 313
\caption{UML diagram with Inhibit conditions} \caption{UML diagram with Inhibit conditions}
\label{fig:umlconcept2} \label{fig:umlconcept2}
@ -1087,7 +1087,15 @@ chosing {\fg}s and working bottom-up this hierarchical trait will occur as a nat
\section{Conclusion} \section{Conclusion}
This paper provides the background for the need for a new methodology for This
\ifthenelse {\boolean{paper}}
{
paper
}
{
chapter
}
provides the background for the need for a new methodology for
static analysis that can span the mechanical electrical and software domains static analysis that can span the mechanical electrical and software domains
using a common notation. using a common notation.
The author believes it addresses many short comings in current static failure mode analysis methodologies. The author believes it addresses many short comings in current static failure mode analysis methodologies.

View File

@ -4,6 +4,7 @@
\usepackage{fancyhdr} \usepackage{fancyhdr}
\usepackage{tikz} \usepackage{tikz}
\usetikzlibrary{shapes,snakes} \usetikzlibrary{shapes,snakes}
\usetikzlibrary{shapes.gates.logic.US,trees,positioning,arrows}
\usepackage{subfigure} \usepackage{subfigure}
\usepackage{amsfonts,amsmath,amsthm} \usepackage{amsfonts,amsmath,amsthm}
\usepackage{algorithm} \usepackage{algorithm}