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

Sending this one to supervisors now.

Browse Source
This commit is contained in:
Robin P. Clark 2012-06-25 09:55:44 +01:00
parent 41db5db6c9
commit 01b2dd7c86
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
papers/fmmd_software_hardware/software_fmmd.tex
View File

@ -230,7 +230,7 @@ and determining what system level failure modes could be caused.
FMEA dates from the 1940s where simple electro-mechanical systems were the norm. FMEA dates from the 1940s where simple electro-mechanical systems were the norm.
Modern control systems nearly always have a significant software/firmware element, Modern control systems nearly always have a significant software/firmware element,
and not being able to model software with current FMEA methodologies and not being able to model software with current FMEA methodologies
is a cause for criticism~\cite{safeware}. is a cause for criticism~\cite{safeware}[Ch.12].
%Several variants of FMEA exist, %Several variants of FMEA exist,
% traditional FMEA being associated with the manufacturing industry, with the aims of prioritising % traditional FMEA being associated with the manufacturing industry, with the aims of prioritising
@ -270,7 +270,7 @@ software hardware/interface~\cite{embedsfmea}.
Although this Although this
would give a better picture of the failure mode behaviour, it would give a better picture of the failure mode behaviour, it
is by no means a rigorous approach to tracing errors that may occur in hardware is by no means a rigorous approach to tracing errors that may occur in hardware
through the top (and therefore ultimately controlling) layer of software. through to the top (and therefore ultimately controlling) layer of software.
\subsection{Current FMEA techniques are not suitable for software} \subsection{Current FMEA techniques are not suitable for software}