robin/Robin_PHD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

forgot to commit from work

Browse Source
This commit is contained in:
Robin P. Clark 2012-07-11 18:43:38 +01:00
parent db0ff368e8
commit 080e043506
2 changed files with 30 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
mybib.bib
View File

@ -29,6 +29,17 @@
YEAR = "2012" 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, @ARTICLE{sfmea,
AUTHOR = "Chris Price, Neal Snooke", AUTHOR = "Chris Price, Neal Snooke",

30
papers/fmmd_software_hardware/software_fmmd.tex
View File

@ -121,7 +121,7 @@ failure mode of the component or sub-system}}}
% {-\baslineskip} % {-\baslineskip}
% {0.5\baselineskip} % {0.5\baselineskip}
% {\normalfont\normalsize\itshape}}% % {\normalfont\normalsize\itshape}}%
\linespread{0.95} \linespread{0.94}
\begin{document} \begin{document}
%\pagestyle{fancy} %\pagestyle{fancy}
@ -734,10 +734,24 @@ the base components in this design.
We now apply FMMD starting with the hardware. 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} \paragraph{Functional Group - Convert mA to Voltage - CMATV}
This functional group contains the load resistor This functional group contains the load resistor
and the physical Analogue to Digital Converter (ADC). and the physical Analogue to Digital Converter (ADC).
% %
@ -975,13 +989,7 @@ as a hierarchical diagram, see figure~\ref{fig:hd}.
% \label{fig:hd} % \label{fig:hd}
% \end{figure} % \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 %\clearpage
\section{Conclusion} \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. input circuit and software.
% %
The {\dc} representing the {\ft} reader 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 %A software specification for a hardware interface will concentrate on
%how to interpret raw readings, or what signals to apply for actuators. %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 !!!!!!!!!!!!!!!!!!!!!!!! %Its solved. Hoooo-ray !!!!!!!!!!!!!!!!!!!!!!!!