My bib now a link --- cannot have several

versions of this it gets confusing

Added a work so far on SFMEA...

Might change the name FMMD to MFMEA
This commit is contained in:
Your Name 2012-04-16 17:41:20 +01:00
parent aa074ee773
commit a05887fd0e
2 changed files with 26 additions and 3 deletions

View File

@ -1,3 +1,20 @@
Model-driven automated software FMEA Proceedings - Annual
Snooke, N.
Comput. Sci. Dept., Aberystwyth Univ., Aberystwyth, UK
@ARTICLE{embedsfmea,
AUTHOR = "Peter L. Goddard",
TITLE = "Validating The Safety of Embedded Real-Time Control Systems using FMEA",
JOURNAL = "Reliability and Maintainability Symposium (RAMS), 1993 Proceedings - Annual",
YEAR = "1993"
}
@ARTICLE{modelsfmea,
AUTHOR = "Snooke, N",
TITLE = "Model-driven automated software FMEA",
JOURNAL = "Reliability and Maintainability Symposium (RAMS), 2011 Proceedings - Annual",
YEAR = "2011"
}
@ARTICLE{sfmeaa, @ARTICLE{sfmeaa,

View File

@ -69,6 +69,7 @@
\newcommand{\dc}{derived~component} \newcommand{\dc}{derived~component}
\newcommand{\dcs}{derived~components} \newcommand{\dcs}{derived~components}
\newcommand{\bc}{base~component} \newcommand{\bc}{base~component}
\newcommand{\FMMD}{ModularFMEA}
\newcommand{\bcs}{base~components} \newcommand{\bcs}{base~components}
\newcommand{\irl}{in real life} \newcommand{\irl}{in real life}
\newcommand{\enc}{\ensuremath{\stackrel{enc}{\longrightarrow}}} \newcommand{\enc}{\ensuremath{\stackrel{enc}{\longrightarrow}}}
@ -209,7 +210,7 @@ failure modes to fix.
Failure Mode Effects and Diagnostics Analysis, is FMEA peformed to Failure Mode Effects and Diagnostics Analysis, is FMEA peformed to
determine a statistical level of safety. determine a statistical level of safety.
This is associated with SIL classification levels~\cite{en61508}~\cite{en61511}. This is associated with Safety Integrity Levels (SIL)~\cite{en61508}~\cite{en61511} classification.
FMMD is a modularisation of FMEA and can produce failure~mode models that can be used in FMMD is a modularisation of FMEA and can produce failure~mode models that can be used in
all the above variants of FMEA. all the above variants of FMEA.
@ -222,7 +223,11 @@ FMEA on the software in isolation~\cite{procsfmea}.
Some work has been performed using databases Some work has been performed using databases
to track the relationships between variables to track the relationships between variables
and system failure modes~\cite{procsfmeadb}, and work has been performed to and system failure modes~\cite{procsfmeadb}, and work has been performed to
introduce automation into the FMEA process~\cite{appswfmea}. introduce automation into the FMEA process~\cite{appswfmea} and code analysis
automation~\cite{modelsfmea}. Although the SFMEA and hardware FMEAs are performed separately
some schools of thought aim for FTA~\cite{nasafta}~\cite{nucfta} (top down - deductive) and FMEA (bottom-up inductive)
to be performed on the same system to provide insight into the
software hardware/interface~\cite{embedsfmea}.
\subsection{Current FMEA techniques are not suitable for software} \subsection{Current FMEA techniques are not suitable for software}
@ -957,7 +962,8 @@ of this paper.
\end{itemize} \end{itemize}
%\today %\today
% %
{ %\tiny %\footnotesize { %\tiny %
\footnotesize
\bibliographystyle{plain} \bibliographystyle{plain}
\bibliography{vmgbibliography,mybib} \bibliography{vmgbibliography,mybib}
} }