diff --git a/papers/software_fmea/Makefile b/papers/software_fmea/Makefile index 1268f95..f779713 100644 --- a/papers/software_fmea/Makefile +++ b/papers/software_fmea/Makefile @@ -12,3 +12,13 @@ all: ${PNG} bib: bibtex software_fmea + + + +abs: # bib + cat abs_pre.tex > abstract.tex + cat abs.tex >> abstract.tex + cat abs_end.tex >> abstract.tex + # bib abs.tex + pdflatex abstract + acroread abstract.pdf diff --git a/papers/software_fmea/abs.tex b/papers/software_fmea/abs.tex new file mode 100644 index 0000000..52a49c7 --- /dev/null +++ b/papers/software_fmea/abs.tex @@ -0,0 +1,33 @@ +%The certification process of safety critical products for European and +%other international standards often demand environmental stress, +%endurance and Electro Magnetic Compatibility (EMC) testing. Theoretical, or 'static testing', +%is often also required. +% +Failure Mode Effects Analysis (FMEA), is a is a bottom-up technique that aims to assess the effect all +component failure modes on a system. +It is used both as a design tool (to determine weaknesses), and is a requirement of certification of safety critical products. +FMEA has been successfully applied to mechanical, electrical and hybrid electro-mechanical systems. + +Work on software FMEA (SFMEA) is beginning, but +at present no technique for SFMEA that +integrates hardware and software models known to the authors exists. +% +Software generally, sits on top of most modern safety critical control systems +and defines its most important system wide behaviour and communications. +Currently standards that demand FMEA for hardware (e.g. EN298, EN61508), +do not specify it for Software, but instead specify, good practise, +review processes and language feature constraints. + +This is a weakness; where FMEA % scientifically +traces component {\fms} +to resultant system failures, software has been left in a non-analytical +limbo of best practises and constraints. +% +If software FMEA were possible, electro-mechanical-software hybrids could +be modelled; and could thus be `complete' failure mode models. +%Failure modes in components in say a sensor, could be traced +%up through the electronics and then through the controlling software. +Presently FMEA, stops at the glass ceiling of the computer program. + +This paper presents an FMEA methodology which can be applied to software, and is compatible +and integrate-able with FMEA performed on mechanical and electronic systems. diff --git a/papers/software_fmea/abs_end.tex b/papers/software_fmea/abs_end.tex new file mode 100644 index 0000000..0f05ce4 --- /dev/null +++ b/papers/software_fmea/abs_end.tex @@ -0,0 +1,4 @@ + + + +\end{document} diff --git a/papers/software_fmea/abs_pre.tex b/papers/software_fmea/abs_pre.tex new file mode 100644 index 0000000..a34da06 --- /dev/null +++ b/papers/software_fmea/abs_pre.tex @@ -0,0 +1,63 @@ + + +\documentclass[twocolumn]{article} +%\documentclass[twocolumn,10pt]{report} +\usepackage{graphicx} +\usepackage{fancyhdr} +%\usepackage{wassysym} +\usepackage{tikz} +\usepackage{amsfonts,amsmath,amsthm} +\usetikzlibrary{shapes.gates.logic.US,trees,positioning,arrows} +%\input{../style} +\usepackage{ifthen} +\usepackage{lastpage} +\usetikzlibrary{shapes,snakes} +\newcommand{\tickYES}{\checkmark} +\newcommand{\fc}{fault~scenario} +\newcommand{\fcs}{fault~scenarios} +\date{} +%\renewcommand{\encodingdefault}{T1} +%\renewcommand{\rmdefault}{tnr} +%\newboolean{paper} +%\setboolean{paper}{true} % boolvar=true or false +\newcommand{\ft}{\ensuremath{4\!\!\rightarrow\!\!20mA} } +\newcommand{\permil}{\ensuremath{{ }^0/_{00}}} +\newcommand{\oc}{\ensuremath{^{o}{C}}} +\newcommand{\adctw}{{${\mathcal{ADC}}_{12}$}} +\newcommand{\adcten}{{${\mathcal{ADC}}_{10}$}} +\newcommand{\ohms}[1]{\ensuremath{#1\Omega}} +\newcommand{\fm}{failure~mode} +\newcommand{\fms}{failure~modes} +\newcommand{\fg}{functional~group} +\newcommand{\FG}{\mathcal{G}} +\newcommand{\DC}{\mathcal{DC}} +\newcommand{\fgs}{functional~groups} +\newcommand{\dc}{derived~component} +\newcommand{\dcs}{derived~components} +\newcommand{\bc}{base~component} +\newcommand{\FMMD}{ModularFMEA} +\newcommand{\bcs}{base~components} +\newcommand{\irl}{in real life} +\newcommand{\enc}{\ensuremath{\stackrel{enc}{\longrightarrow}}} +\newcommand{\pin}{\ensuremath{\stackrel{pi}{\longleftrightarrow}}} +%\newcommand{\pic}{\em pure~intersection~chain} +\newcommand{\pic}{\em pair-wise~intersection~chain} +\newcommand{\wrt}{\em with~respect~to} +\newcommand{\abslevel}{\ensuremath{\Psi}} +\setlength{\topmargin}{0in} +\setlength{\headheight}{0in} +\setlength{\headsep}{0in} +\setlength{\textheight}{22cm} +\setlength{\textwidth}{18cm} +\setlength{\oddsidemargin}{0in} +\setlength{\evensidemargin}{0in} +\setlength{\parindent}{0.0in} +\setlength{\parskip}{6pt} + + +\begin{document} + + +\section*{FMEA applied to a hybrid software and hardware sub-system} + + diff --git a/papers/software_fmea/software_fmea.tex b/papers/software_fmea/software_fmea.tex index d08bc90..238b64b 100644 --- a/papers/software_fmea/software_fmea.tex +++ b/papers/software_fmea/software_fmea.tex @@ -131,39 +131,7 @@ failure mode of the component or sub-system}}} %\small \abstract{ \em -%The certification process of safety critical products for European and -%other international standards often demand environmental stress, -%endurance and Electro Magnetic Compatibility (EMC) testing. Theoretical, or 'static testing', -%is often also required. -% -Failure Mode Effects Analysis (FMEA), is a is a bottom-up technique that aims to assess the effect all -component failure modes on a system. -It is used both as a design tool (to determine weaknesses), and is a requirement of certification of safety critical products. -FMEA has been successfully applied to mechanical, electrical and hybrid electro-mechanical systems. - -Work on software FMEA (SFMEA) is beginning, but -at present no technique for SFMEA that -integrates hardware and software models known to the authors exists. -% -Software generally, sits on top of most modern safety critical control systems -and defines its most important system wide behaviour and communications. -Currently standards that demand FMEA for hardware (e.g. EN298, EN61508), -do not specify it for Software, but instead specify, good practise, -review processes and language feature constraints. - -This is a weakness; where FMEA % scientifically -traces component {\fms} -to resultant system failures, software has been left in a non-analytical -limbo of best practises and constraints. -% -If software FMEA were possible, electro-mechanical-software hybrids could -be modelled; and could thus be `complete' failure mode models. -%Failure modes in components in say a sensor, could be traced -%up through the electronics and then through the controlling software. -Presently FMEA, stops at the glass ceiling of the computer program. - -This paper presents an FMEA methodology which can be applied to software, and is compatible -and integrate-able with FMEA performed on mechanical and electronic systems. +\input{abs} } \today