From 080e043506a3d10f718b0d78edd8bd1b069b229c Mon Sep 17 00:00:00 2001
From: "Robin P. Clark" <robin48gx@gmail.com>
Date: Wed, 11 Jul 2012 18:43:38 +0100
Subject: [PATCH] forgot to commit from work

---
 mybib.bib                                     | 11 +++++++
 .../fmmd_software_hardware/software_fmmd.tex  | 30 ++++++++++++-------
 2 files changed, 30 insertions(+), 11 deletions(-)

diff --git a/mybib.bib b/mybib.bib
index 167ab3d..d04827e 100644
--- a/mybib.bib
+++ b/mybib.bib
@@ -29,6 +29,17 @@
   YEAR =         "2012"
 }
 
+@INPROCEEDINGS{sfmeainterface,
+author={Ozarin, N.W.},
+booktitle={Reliability and Maintainability Symposium, 2009. RAMS 2009. Annual}, title={Applying software failure modes and effects analysis to interfaces},
+year={2009},
+month={jan.},
+volume={},
+number={},
+pages={533 -538},
+keywords={mission-critical system;safety-critical system;software failure mode and effect analysis;software variable;system recovery;},
+doi={10.1109/RAMS.2009.4914732},
+ISSN={0149-144X},}
 
 @ARTICLE{sfmea,
   AUTHOR =       "Chris Price, Neal Snooke",
diff --git a/papers/fmmd_software_hardware/software_fmmd.tex b/papers/fmmd_software_hardware/software_fmmd.tex
index 722765c..c4e393c 100644
--- a/papers/fmmd_software_hardware/software_fmmd.tex
+++ b/papers/fmmd_software_hardware/software_fmmd.tex
@@ -121,7 +121,7 @@ failure mode of the component or sub-system}}}
 % {-\baslineskip}
 % {0.5\baselineskip}
 % {\normalfont\normalsize\itshape}}%
-\linespread{0.95}
+\linespread{0.94}
 
 \begin{document}
 %\pagestyle{fancy}
@@ -734,10 +734,24 @@ the base components in this design.
 We now apply FMMD starting with the hardware.
 
 
-\subsection{FMMD Process}
+\subsection{FMMD Process --- {\ft} programmatic value implementation.}
+
+\begin{figure}[h]
+ \centering
+ \includegraphics[width=150pt,keepaspectratio=true]{./hd.png}
+ % hd.png: 416x381 pixel, 72dpi, 14.68x13.44 cm, bb=0 0 416 381
+ \caption{FMMD Hierarchy for {\ft} input}
+ \label{fig:hd}
+\end{figure}
+
+We analyse the {\ft} to programmatic value implementation in three stages using FMMD.
+We start with the hardware,  
+add then each of the software functions. 
+This forms the fault mode hierarchy represented in figure~\ref{fig:hd}.
 
 \paragraph{Functional Group - Convert mA to Voltage - CMATV}
 
+
 This functional group contains the load resistor 
 and the physical Analogue to Digital Converter (ADC).
 %
@@ -975,13 +989,7 @@ as a hierarchical diagram, see figure~\ref{fig:hd}.
 %  \label{fig:hd}
 % \end{figure}
 
-\begin{figure}[h]
- \centering
- \includegraphics[width=150pt,keepaspectratio=true]{./hd.png}
- % hd.png: 416x381 pixel, 72dpi, 14.68x13.44 cm, bb=0 0 416 381
- \caption{FMMD Hierarchy for {\ft} input}
- \label{fig:hd}
-\end{figure}
+
 
 
 
@@ -1036,7 +1044,7 @@ as a hierarchical diagram, see figure~\ref{fig:hd}.
 %\clearpage
 \section{Conclusion}
 %
-The FMMD method has been demonstrated, using an the industry stanbdard {\ft}
+The FMMD method has been demonstrated, using an the industry standard {\ft}
 input circuit and software.
 %
 The {\dc} representing the {\ft} reader
@@ -1069,7 +1077,7 @@ re-use this analysis for each {\ft} input in the system.
 %
 %A software specification for a hardware interface will concentrate on
 %how to interpret raw readings, or what signals to apply for actuators.
-Additionally, using FMMD we can determine a failure model for the hardware/software interface. % interface as well.
+Additionally, using FMMD we can determine a failure model for the hardware/software interface~\cite{sfmeainterface}. % interface as well.
 
 %Its solved. Hoooo-ray !!!!!!!!!!!!!!!!!!!!!!!!