\documentclass[a4paper,10pt]{article}
\usepackage[utf8]{inputenc}


\newcommand{\cc}{comparison~complexity}
\newcommand{\ft}{\ensuremath{4\!\!\rightarrow\!\!20mA} }
\newcommand{\tenfifty}{\ensuremath{10\!\!\rightarrow\!\!50mA} }
\usepackage{graphicx}
\usepackage{fancyhdr}
\usepackage{tikz}
\usepackage{amsfonts,amsmath,amsthm}
\usetikzlibrary{shapes.gates.logic.US,trees,positioning,arrows}
\def\layersep{1.8cm}
%\input{../style}\def\layersep{1.8cm}
\usepackage{ifthen}
\usepackage{lastpage}
\usetikzlibrary{shapes,snakes}
\newcommand{\tickYES}{\checkmark}
%%   \newcommand{\fc}{fault~scenario}
\newcommand{\fc}{failure~cause}
%%   \newcommand{\fcs}{fault~scenarios}
\newcommand{\fcs}{failure~causes}
% Page layout definitions to suit A4 paper
\setcounter{secnumdepth}{3}        \setcounter{tocdepth}{4}
\setlength{\topmargin}{0mm}
\setlength{\textwidth}{160mm}      \setlength{\textheight}{220mm}
\setlength{\oddsidemargin}{0mm}    \setlength{\evensidemargin}{0mm}
%
\newcommand{\permil}{\ensuremath{0/{\!}_{00}}}

\newcommand{\emp}{} %% was italics
\newcommand{\sd}{\ensuremath{\Sigma \Delta ADC}} 
%\newcommand{\sd}{\ensuremath{Sigma\;Delta\;ADC}} 
\newcommand{\derivec}{{D}}
%\newcommand{\hh}{\ensuremath{{\stackrel{o}{H}}}}
\newcommand{\hh}{\ensuremath{{\hbar}}}
\newcommand{\abslev}{\ensuremath{\alpha}}
\newcommand{\oc}{\ensuremath{^{o}{C}}}
\newcommand{\adctw}{{${\mathcal{ADC}}_{12}$}}
\newcommand{\adcten}{{${\mathcal{ADC}}_{10}$}}
\newcommand{\ohms}[1]{\ensuremath{#1\Omega}}
\newcommand{\fm}{\emp failure~mode}
\newcommand{\fms}{\emp failure~modes}
\newcommand{\FG}{\ensuremath{{FG}}}
\newcommand{\DC}{\ensuremath{{DC}}}
\newcommand{\fg}{\emp functional~grouping}
\newcommand{\fgs}{\emp functional~groupings}
\newcommand{\Fgs}{\emp Functional~groupings}
\newcommand{\dc}{\emp derived~component}
\newcommand{\dcs}{\emp derived~components}
\newcommand{\bc}{\emp base~component}
\newcommand{\Bc}{\emp Base~component}
\newcommand{\bcs}{\emp base~components}
\newcommand{\irl}{in~real~life}
\newcommand{\enc}{\ensuremath{\stackrel{enc}{\longrightarrow}}}
\newcommand{\pin}{\ensuremath{\stackrel{pi}{\longleftrightarrow}}}
\newcommand{\half}{\ensuremath{\frac{1}{2}}}
\newcommand{\cf}[1]{\textbf{#1()}}
\newcommand{\etc}{Energy~Technology~Control~Ltd}
%
% OK after about 3 years its not rigorous FMEA (RFMEA) anymore, oh no, its Exhaustive FMEA
% but since the fuckers might change it yet again, I am making this a macro.
\newcommand{\XFMEA}{XFMEA}
%

%\newcommand{\pic}{\em pure~intersection~chain}
\newcommand{\pic}{\emp pair-wise~intersection~chain}
\newcommand{\wrt}{\emp with~respect~to}
\newcommand{\swf}{software~function}
% DO NOT USE THIS ONE USE \abslev \newcommand{\abslevel}{\ensuremath{\Psi}}
\renewcommand{\baselinestretch}{1.5}

%opening
\title{Abstract for Phd Thesis: Failure Mode Modular De-Composition}
\author{R. P. Clark}

\begin{document}

\maketitle

\begin{abstract}


%
% This should be a three hundred word summary of the work and findings
% Supervisors did not warn me this was required.
% I found out by reading the OU ``how to get a PhD'' book in the bath, and then wading through the Brighton University
% regulations where it is stated on page 14 of a 30+ page document filled with mostly n/a regulations to me.
%
%

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% BEGINING --- Introduce the field
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
The certification process of safety critical products for European and other international 
standards typically demand environmental stress, endurance and electro magnetic compatibility testing. 
%
Theoretical, or `static~testing' also a requirement. 
%
Failure Mode Effects Analysis (FMEA) is a tool used for static testing.
FMEA is a bottom-up technique that aims to assess the effects 
of all component failure modes in a system.
%
Its use is traditionally limited to hardware systems. % only. 
%
With the growing complexity of modern electronics traditional FMEA
is suffering from state explosion and re-use of analysis problems.
%
Also with the now ubiquitous use of micro-controllers in smart~instruments and control systems, 
software is increasingly being seen as a `missing~factor' for FMEA. % analysis.


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Middle work and findings
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
This thesis presents a new modular variant of FMEA, Failure Mode Modular Decomposition (FMMD).
%
FMMD has been designed to integrate mechanical/electronic and software 
failure models, by treating them all as components  in terms of their failure modes. 
%
For instance, software functions, 
electronic and mechanical components
can all be assigned sets of failure modes.
%
FMMD builds failure mode models from the bottom-up by incrementally analysing
{\fgs} of components, using the results of analysis to create higher level {\dcs},
which in turn can be used to build {\fgs}.
%
In this way a hierarchical failure mode model 
is built. 
%
Software functions are treated as components by FMMD and can thus be incorporated seamlessly into
the failure mode hierarchical model.
%
A selection of examples, electronic circuits and hardware/software hybrids are analysed using 
this new methodology.
%
The results of these analyses are then discussed from the perspective of safety critical application.
%
Performance in terms of test efficiency is greatly improved by FMMD and 
the examples analysed and theoretical models are used to demonstrate this.
%

%Because FMMD is modular and hierarchical, and deals with all its objects in 
%terms of their failure mode behaviour, it is ideally suited to creating integrated software and hardware models.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% End what has been achieved ---- all in 300ish word OK here we go.
%Conclusions are presented listing the 
%and FMMD is compared with traditional HFMEA and SFMEA.
This thesis presents a methodology that %solves 
mitigates the state explosion problems of FMEA;
provides integrated hardware and software failure mode models;
facilitates multiple failure mode analysis;
encourages re-use of analysis work
and can be used to produce traditional format FMEA reports.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\end{abstract}



\end{document}
