Sending this one to supervisors now.
This commit is contained in:
parent
41db5db6c9
commit
01b2dd7c86
@ -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.
|
||||
Modern control systems nearly always have a significant software/firmware element,
|
||||
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,
|
||||
% traditional FMEA being associated with the manufacturing industry, with the aims of prioritising
|
||||
@ -270,7 +270,7 @@ software hardware/interface~\cite{embedsfmea}.
|
||||
Although this
|
||||
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
|
||||
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}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user