Started on the paper.

Copied the bib files so that this
is easy to copy as a directory in
case they compile it in Latex, not pdf.
This commit is contained in:
Your Name 2012-03-22 13:45:19 +00:00
parent 5af377a61b
commit 8a9b9dbb23
3 changed files with 2537 additions and 29 deletions

View File

@ -0,0 +1,603 @@
% my bib file.
@ARTICLE{fmd91,
AUTHOR = "Reliability Analysis Center",
TITLE = "Failure Mode/Mechanisms Distributions 1991",
JOURNAL = "United States Department of Commerce",
YEAR = "1991"
}
% $Id: mybib.bib,v 1.3 2009/11/28 20:05:52 robin Exp $
@article{Clark200519,
title = "Failure Mode Modular De-Composition Using Spider Diagrams",
journal = "Electronic Notes in Theoretical Computer Science",
volume = "134",
number = "",
pages = "19 - 31",
year = "2005",
note = "Proceedings of the First International Workshop on Euler Diagrams (Euler 2004)",
issn = "1571-0661",
doi = "DOI: 10.1016/j.entcs.2005.02.018",
url = "http://www.sciencedirect.com/science/article/B75H1-4G6XT71-3/2/0e3a47df2ec15bfba9f85feae81786e3",
author = "R.P. Clark",
keywords = "Failsafe",
keywords = "EN298",
keywords = "gas-safety",
keywords = "burner",
keywords = "control",
keywords = "fault",
keywords = "double-fault",
keywords = "single-fault",
keywords = "fault-tolerance"
}
@ARTICLE{ftahistory,
AUTHOR = "Clifton Ericsson",
TITLE = "Fault Tree Analysis a History",
JOURNAL = "Proceedings of the 17th international safety conference",
YEAR = "1999"
}
@ARTICLE{fafmea,
AUTHOR = "Zigmund Bluvband, Pavel Grabov",
TITLE = "Failure Analysis of FMEA",
JOURNAL = "IEEE 1-4244-2509-9/09/",
YEAR = "2009"
}
@ARTICLE{fmeda,
AUTHOR = "John C. Grebe Dr. William M. Goble",
TITLE = "FMEDA Accurate Product Failure Metrics",
JOURNAL = "EXIDA publication. www.exida.com/articles/FMEDA\%20Development.pdf",
YEAR = "2007"
}
@ARTICLE{canspec,
AUTHOR = "Bosch.",
TITLE = "CAN Specification 2.0",
JOURNAL = "Bosch Technical Standard",
YEAR = "1991"
}
@ARTICLE{caninauto,
AUTHOR = "H. Zeltwanger",
TITLE = "Single Processor implementation of the CANopen Safety Protocol",
JOURNAL = "CAN in Automation (CiA)",
YEAR = "2008"
}
@ARTICLE{valueoflife,
AUTHOR = "W.K. Viscusi",
TITLE = "The value of life: Estimates with risks by occupation and industry",
JOURNAL = "Harvard John M. Olin Canter for Law ISSN 1045-6333",
YEAR = "2003"
}
@ARTICLE{crcembedd,
AUTHOR = "Philip Koopman, Tridib Chakravarty",
TITLE = "Cyclic Redundancy Code (CRC) Polynomial Selection for Embedded Networks",
JOURNAL = "The International Conference on dependable systems and networks DSN-2004",
YEAR = "2004"
}
@ARTICLE{nucfta,
AUTHOR = "US Nuclear reg commission",
TITLE = "Fault Tree Handbook",
JOURNAL = "Nuclear Safety Analysis Handbook",
YEAR = "1981"
}
@ARTICLE{nasafta,
AUTHOR = "NASA",
TITLE = "Fault Tree Handbook with Aerospace Applications",
JOURNAL = "NASA Handbook",
YEAR = "2002"
}
@BOOK{embupsys,
TITLE = "Embedded Microprocessor Systems 3rd Edition ISBN 0-7506-75434-9",
AUTHOR = "Stuart R Ball",
PUBLISHER = "Newnes",
YEAR = "2002"
}
@BOOK{alggraph,
AUTHOR = "Alan Gibbons",
TITLE = "Algorithmic Graph Theory ISBN:978-0521288811 ",
PUBLISHER = "Cambridge University PressCambridge University Press",
YEAR = "1985"
}
@BOOK{git,
AUTHOR = "Jon Loeliger",
TITLE = "Version Control with Git ISBN:978-0-596-52012-0",
PUBLISHER = "O'Reilly Media",
YEAR = "2009"
}
@BOOK{ince,
AUTHOR = "D. C. Ince",
TITLE = "In Introduction to discrete Mathematics, Formal System specification and Z",
PUBLISHER = "Oxford University Press",
YEAR = "1992"
}
@BOOK{safeware,
AUTHOR = "Nancy Leveson",
TITLE = "Safeware: System safety and Computers ISBN: 0-201-11972-2",
PUBLISHER = "Addison-Wesley",
YEAR = "2005"
}
@BOOK{bfmea,
AUTHOR = "Robin E McDermot et all",
TITLE = "The Basics of FMEA ISBN: 0-527-76320-9",
PUBLISHER = "Productivity",
YEAR = "1996"
}
@BOOK{mil1991,
AUTHOR = "United~States~DOD",
TITLE = "Reliability Prediction of Electronic Equipment",
PUBLISHER = "DOD",
YEAR = "1991"
}
@BOOK{faa,
AUTHOR = "Federal Aviation Administration",
TITLE = "System Safety Handbook",
PUBLISHER = "http://www.faa.gov/library/ manuals/aviation /risk\_management/ss\_handbook/",
YEAR = "2008"
}
@BOOK{sccs,
AUTHOR = "Neil~Storey",
TITLE = "Safety-Critical Computer Systems ISBN 0-201-42787-7",
PUBLISHER = "Prentice Hall",
YEAR = "1996"
}
@PHDTHESIS{maikowski,
AUTHOR = "Leo M Maikowski",
TITLE = "Toleranced Multiple Fault Diagnosis of Analog Circuits",
SCHOOL = " Brighton University, School of Electrical Engineering",
YEAR = "1995"
}
@BOOK{sem,
AUTHOR = "J.~Woodcock,~Martin~Loomes",
TITLE = "Software Engineering Mathematics ISBN 0-273-02673-9",
PUBLISHER = "Pitman",
YEAR = "1988"
}
@BOOK{allfour,
AUTHOR = "Betty Tootell",
TITLE = "All Four Engines Have Failed ISBN 0-233-97758-9",
PUBLISHER = "Andre deutsch",
YEAR = "1985"
}
@BOOK{f77,
AUTHOR = "A.~Balfour D.H.~Marwick",
TITLE = "Programming in Standard Fortran 77 ISBN 0-435-77486-7",
PUBLISHER = "Heinemann Educational Books",
YEAR = "1979"
}
@BOOK{ctw,
AUTHOR = "Gregory~J.E.~Rawlins",
TITLE = "Compared to What ? An introduction to the analysis of algorithms ISBN 0-7167-8243-x",
PUBLISHER = "Computer Science Press",
YEAR = "1991"
}
@BOOK{alg,
AUTHOR = "Alan~Gibbons",
TITLE = "Algorithmic Graph Theory ISBN 0-521-28881-9",
PUBLISHER = "Cambridge University Press",
YEAR = "1985"
}
@BOOK{found,
AUTHOR = "Ian~Stewart, David~Tall",
TITLE = "The Foundations of Mathematics : ISBN 0-19-853165-6",
PUBLISHER = "Oxford University Press",
YEAR = "1977"
}
@BOOK{shin,
AUTHOR = "Sun-Joo~Shin",
TITLE = "The Iconic Logic of Peirces Graphs",
PUBLISHER = "Bradford",
YEAR = "2002"
}
@BOOK{probstat,
AUTHOR = " M~R~Spiegel",
TITLE = "Probability and Statistics Second edition : SHCAUM'S : ISBN 0-07-135004-7",
PUBLISHER = "Oxford University Press",
YEAR = "1988"
}
@BOOK{idmfssz,
AUTHOR = " D~C~Ince",
TITLE = " An Introduction to Discrete Mathematics, Formal System Specification and Z : Oxford : ISBN 0-19-853836-7",
PUBLISHER = "Oxford University Press",
YEAR = "1988"
}
@BOOK{wdycwopt,
AUTHOR = " Richard~P~Feynman",
TITLE = " What do you care what other people think: Harper Collins : ISBN 0-586-21855-6",
PUBLISHER = " harpercollins",
YEAR = "1988"
}
@BOOK{joyofsets,
AUTHOR = " Keith~devlin",
TITLE = " The Joy of Sets: 2nd edition: ISBN 978-0-387-94094-6",
PUBLISHER = " Springer",
YEAR = "1993"
}
@MISC{microchip,
author = "Microchip",
title = "Microchip technology Inc. Home Page",
howpublished = "Available from http://www.microchip.com/",
year = "2009"
}
@MISC{gnuplot,
author = "Various Open~source~Project",
title = "",
howpublished = "Available from http://www.gnuplot.info/",
year = "2005"
}
@MISC{eulerviz,
author = "Peter~Rodgers, John~Howse, Andrew~Fish",
title = "Visualization of Euler Diagrams",
howpublished = "http://www.cmis.bton.ac.uk/research/vmg/papers/EulerViz.pdf",
year = "2005"
}
@MISC{eulerprop,
author = "Peter~Rodgers, John~Howse, Gem~Stapleton",
title = "Properties of Euler Diagrams",
howpublished = "http://www.cmis.bton.ac.uk/research/vmg/papers/",
year = "2007"
}
@MISC{en161,
author = "E N Standard",
title = "EN161:2007 Automatic shutoff valves for gas burners and gas appliances",
howpublished = "British standards Institution http://www.bsigroup.com/",
year = "2003"
}
@MISC{en298,
author = "E N Standard",
title = "EN298:2003 Gas Burner Controllers with forced draft",
howpublished = "British standards Institution http://www.bsigroup.com/",
year = "2003"
}
@MISC{en60730,
author = "E N Standard",
title = "EN60730: Automatic Electrical controls for household and similar use",
howpublished = "British standards Institution http://www.bsigroup.com/",
year = "1994"
}
@MISC{challenger,
author = "U.S. Presidential Commission",
title = "Report of the SpaceShuttle Challanger Accident",
howpublished = "Available from http://science.ksc.nasa.gov/shuttle/missions/51-l/docs/rogers-commission/table-of-contents.html",
year = "1986"
}
@MISC{en61508,
author = "E N Standard",
title = "EN61508:2002 Functional safety of electrical/electronic/programmable electronic safety related systems",
howpublished = "British standards Institution http://www.bsigroup.com/",
year = "2002"
}
@MISC{javaarea,
author = "Sun~Micro~Systems",
title = "Java Area Operations",
howpublished = "Available from http://java.sun.com/j2se/1.3/docs/api/java/awt/geom/Area.html",
year = "2000"
}
@Manual{tlp181,
title = {TLP 181 Datasheet},
key = {TOSHIBA Photocoupler GaAs Ired and PhotoTransistor},
author = {Toshiba inc.},
OPTorganization = {},
address = {http://www.toshiba.com/taec/ components2/Datasheet\_Sync//206/4191.pdf},
OPTedition = {},
OPTmonth = {},
year = {2009},
OPTnote = {},
OPTannote = {},
OPTurl = {},
OPTdoi = {},
OPTissn = {},
OPTlocalfile = {},
OPTabstract = {},
}
@Manual{pic18f2523,
title = {PIC18F2523 Datasheet},
OPTkey = {},
author = {Microchip inc},
OPTorganization = {},
address = {http://ww1.microchip.com/downloads/en/DeviceDoc/39755c.pdf},
OPTedition = {},
OPTmonth = {},
year = {2009},
OPTnote = {},
OPTannote = {},
OPTurl = {},
OPTdoi = {},
OPTissn = {},
OPTlocalfile = {},
OPTabstract = {},
}
@Book{wt,
title = {Water Treatment Essentials for Boiler Plant Operation},
publisher = {Mc Graw Hill ISBN 0-07-048291-5},
year = {1997},
author = {Robert G Nunn},
ALTALTeditor = {},
OPTkey = {},
OPTvolume = {},
OPTnumber = {},
OPTseries = {},
OPTaddress = {},
OPTedition = {},
OPTmonth = {},
OPTnote = {},
OPTannote = {},
OPTurl = {},
OPTdoi = {},
OPTissn = {ISBN 0-07-048291-5},
OPTlocalfile = {},
OPTabstracts = {},
}
@TechReport{spiraxsarco,
author = {Spirax Sarco},
title = {http://www.spiraxsarco.com/resources/steam-engineering-tutorials.asp},
institution = {Spirax Sarco},
year = {2010},
OPTkey = {},
OPTtype = {},
OPTnumber = {},
OPTaddress = {},
OPTmonth = {},
OPTnote = {},
OPTannote = {},
OPTurl = {},
OPTdoi = {},
OPTissn = {},
OPTlocalfile = {},
OPTabstract = {},
}
@Book{aoe,
title = {The Art of Electronics},
publisher = {Cambridge},
year = {1989},
author = {Paul Horowitz, Winfield Hill},
OPTkey = {},
OPTvolume = {},
OPTnumber = {},
OPTseries = {},
OPTaddress = {},
OPTedition = {2nd},
OPTmonth = {},
OPTnote = {},
OPTannote = {},
OPTurl = {},
OPTdoi = {},
OPTissn = {ISBN 0-521-37095-7},
OPTlocalfile = {},
OPTabstracts = {},
}
@TechReport{eurothermtables,
author = {Eurotherm Ltd.},
title = {Thermocouple Emf TABLES and PLATINUM 100 RESISTANCE THERMOMETER TABLES},
institution = {Eurotherm, UK},
year = {1973},
OPTkey = {},
OPTtype = {},
OPTnumber = {},
OPTaddress = {},
OPTmonth = {June},
OPTnote = {Bulletin TT-1},
OPTannote = {},
OPTurl = {},
OPTdoi = {},
OPTissn = {},
OPTlocalfile = {},
OPTabstract = {},
}
@Book{ldd,
author = {Jonathon Corbet},
ALTeditor = {Alessandro Rubini},
ALTeditor = {Greg Kroah-Hartman},
title = {Linux Device Drivers},
publisher = {O'Reilly ISBN 0-596-00590-3},
year = {1998},
OPTkey = {ISBN 0-596-00590-3},
OPTvolume = {},
OPTnumber = {},
OPTseries = {linux},
OPTaddress = {},
OPTedition = {3rd},
OPTmonth = {},
OPTnote = {},
OPTannote = {},
OPTurl = {www.oreilly.com},
OPTdoi = {},
OPTissn = {},
OPTlocalfile = {},
OPTabstract = {}
};
@Book{bash,
author = {Carl Albing},
title = {Bash Cookbook},
publisher = {O'Reilly ISBN 0-596-52678-4},
year = {2007},
OPTkey = {ISBN 0-596-52678-4},
OPTvolume = {},
OPTnumber = {},
OPTseries = {unix/linux},
OPTaddress = {},
OPTedition = {},
OPTmonth = {},
OPTnote = {},
OPTannote = {},
OPTurl = {www.oreilly.com},
OPTdoi = {},
OPTissn = {},
OPTlocalfile = {},
OPTabstract = {}
};
@Book{sedawk,
author = {Dale Dougherty, Arnold Robbins},
title = {Sed and Awk},
publisher = {O'Reilly ISBN 1-56592-225-5},
year = {1997},
OPTkey = {ISBN 1-56592-225-5},
OPTvolume = {},
OPTnumber = {},
OPTseries = {unix/linux},
OPTaddress = {},
OPTedition = {},
OPTmonth = {},
OPTnote = {},
OPTannote = {},
OPTurl = {www.oreilly.com},
OPTdoi = {},
OPTissn = {},
OPTlocalfile = {},
OPTabstract = {}
};
@Book{bels,
author = {Karim Yaghmour},
title = {Building Embedded LINUX systems},
publisher = {O'Reilly ISBN ISBN 0-596-00222-X},
year = {2003},
OPTkey = {ISBN 0-596-00222-X},
OPTvolume = {},
OPTnumber = {},
OPTseries = {linux},
OPTaddress = {},
OPTedition = {3rd},
OPTmonth = {},
OPTnote = {},
OPTannote = {},
OPTurl = {www.oreilly.com},
OPTdoi = {},
OPTissn = {},
OPTlocalfile = {},
OPTabstract = {}
};
@Book{can,
author = {Olaf Pfeiffer},
ALTeditor = {Andrew Ayre},
ALTeditor = {Christian Keydel},
title = {Embedded networking with CAN and CANopen},
publisher = {RTC ISBN 0-929392-78-7},
year = {2003},
OPTkey = { },
OPTvolume = {},
OPTnumber = {},
OPTseries = {Embedded Systems},
OPTaddress = {},
OPTedition = {1st},
OPTmonth = {},
OPTnote = {},
OPTannote = {},
OPTurl = {www.rtcbooks.com},
OPTdoi = {},
OPTissn = {},
OPTlocalfile = {},
OPTabstract = {}
};
@Article{article,
author = {dd},
title = {dd},
journal = {dd},
year = {2008},
OPTkey = {},
OPTvolume = {},
OPTnumber = {},
OPTpages = {1,2},
OPTmonth = {JAN},
OPTnote = {},
OPTannote = {},
OPTurl = {},
OPTdoi = {},
OPTissn = {},
OPTlocalfile = {},
OPTabstract = {}
};
@Book{sqlite,
author = {Micheal Owens},
title = {The definitive guide to SQLite},
publisher = {Apres ISBN 1-59059-673-0},
year = {2006},
OPTkey = {},
OPTvolume = {},
OPTnumber = {},
OPTseries = {Databases/SQLite},
OPTaddress = {},
OPTedition = {},
OPTmonth = {},
OPTnote = {},
OPTannote = {},
OPTurl = {},
OPTdoi = {},
OPTissn = {},
OPTlocalfile = {},
OPTabstract = {}
};

View File

@ -1,35 +1,184 @@
%%% OUTLINE
% Software FMEA
%
%
% Glaring hole in approvals FMEA is performed on hardware
% and electronics, but with software we only get guidlines ( which mostly consist of constraints!)
%
% No known method of software failure mode effects analysis--- some work has been done on
% Sofware FTA a top down approach---
% Bottom up approach means all known failure modes must be modelled.
% SIL does not have metric or tools to analyse software for safety,
% it instead applies best practises and constraints on computer language features (i.e.
% in C limited use of pointers no recursion etc).
%
%
% Introduce concept of FMEA
% * bottom up
% * all failure modes for all componnts
%
% Concept of FMMD
%
% Look at the structure of software
% * a natural hierarchy
%
% Software written for a controlled
% Contract programming
% * describe concept
% * describe how this fits in with failure modes and failure symptoms concepts
%
% Describe how contract programming represents the failure modes of software
%
% Now describe how this fits in with the structure of FMMD
\documentclass[twocolumn]{article}
%\documentclass[twocolumn,10pt]{report}
\usepackage{graphicx}
\usepackage{fancyhdr}
\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
Software FMEA \newcommand{\oc}{\ensuremath{^{o}{C}}}
\newcommand{\adctw}{{${\mathcal{ADC}}_{12}$}}
\newcommand{\adcten}{{${\mathcal{ADC}}_{10}$}}
\newcommand{\ohms}[1]{\ensuremath{#1\Omega}}
\newcommand{\fg}{functional~group}
\newcommand{\fgs}{functional~groups}
\newcommand{\dc}{derived~component}
\newcommand{\dcs}{derived~components}
\newcommand{\bc}{base~component}
\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}}
\newcommand{\fmmdgloss}{\glossary{name={FMMD},description={Failure Mode Modular De-Composition, a bottom-up methodolgy for incrementally building failure mode models, using a procedure taking functional groups of components and creating derived components representing them, and in turn using the derived components to create higher level functional groups, and so on, that are used to build a failure mode model of a system}}}
\newcommand{\fmodegloss}{\glossary{name={failure mode},description={The way in which a failure occurs. A component or sub-system may fail in a number of ways, and each of these is a
failure mode of the component or sub-system}}}
\newcommand{\fmeagloss}{\glossary{name={FMEA}, description={Failure Mode and Effects analysis (FMEA) is a process where each potential failure mode within a system, is analysed to determine system level failure modes, and to then classify them {\wrt} perceived severity}}}
\newcommand{\frategloss}{\glossary{name={failure rate}, description={The number of failure within a population (of size N), divided by N over a given time interval}}}
\newcommand{\pecgloss}{\glossary{name={PEC},description={A Programmable Electronic controller, will typically consist of sensors and actuators interfaced electronically, with some firmware/software component in overall control}}}
\newcommand{\bcfm}{base~component~failure~mode}
\def\layersep{1.8cm}
\newboolean{pld}
\setboolean{pld}{false} % boolvar=true or false : draw analysis using propositional logic diagrams
\newboolean{dag}
\setboolean{dag}{true} % boolvar=true or false : draw analysis using directed acylic graphs
\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}
%\pagestyle{fancy}
%\fancyhf{}
%\fancyhead[LO]{}
%\fancyhead[RE]{\leftmark}
%\cfoot{Page \thepage\ of \pageref{LastPage}}
%\rfoot{\today}
%\lhead{Developing a rigorous bottom-up modular static failure mode modelling methodology}
%\lhead{Developing a rigorous bottom-up modular static failure modelling methodology}
% numbers at outer edges
\pagenumbering{arabic} % Arabic page numbers hereafter
\author{R.Clark$^\star$ \\ % , A.~Fish$^\dagger$ , C.~Garrett$^\dagger$, J.~Howse$^\dagger$ \\
$^\star${\em Energy Technology Control, UK. r.clark@energytechnologycontrol.com} \and $^\dagger${\em University of Brighton, UK}
}
%\title{Developing a rigorous bottom-up modular static failure mode modelling methodology}
\title{Applying FMEA to Software}
%\nodate
\maketitle
\paragraph{Keywords:} static failure mode modelling safety-critical
%\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 weakness), and is a requirement of certification of safety critical products.
FMEA has been successfully applied to mechanical, electrical and hybrid electro-mechanical systems.
At present no known technique for Software FMEA exists.
Standards~\cite{en298}~\cite{en61508} that use FMEA
do not specify it for Software, but do specify, good practise,
review processes and language feature constraints.
Software gnerally, sits on top of most safety critical control systems
and
This is a weakness; if software FMEA were possible electro-mechanical-software hybrids could
be modelled.
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.
}
\section{Introduction}
{
This paper describes and appraises four current failure modelling methodologies.
Their advantages and deficiencies are discussed and a desirable criteria list
for an `ideal' static failure mode methodology is developed.
A proposed
methodology is then described. % and discussed.
A worked example is then presented, using the new methodology, which models the failure mode
behaviour of a non-inverting op-amp circuit.
Using the worked example the new methodology is evaluated.
Finally the desirable criteria list is presented as a check box table alongside
four current methodologies.
}
\subsection{Evaluation of FMMD}
%\clearpage
\section{Conclusion}
No known method of software failure mode effects analysis--- some work has been done on \paragraph{Future work}
Sofware FTA a top down approach--- \begin{itemize}
Bottom up approach means all known failure modes must be modelled. \item To provide bounds on the size of the state space for the application of the methodology to certain classes of systems.
SIL does not have metric or tools to analyse software for saefty, \item To build a {\dcs} library of common electrical, mechanical and software models (i.e. a collection of worked example {\dcs}).
it instead applies best practises and constraints on computer language features (i.e. \item To provide formal generic translations from the constructed model of any given system to the other models.
in C limited use of pointers no recursion etc). \end{itemize}
%\today
%
Introduce concept of FMEA { %\tiny %\footnotesize
* bottom up \bibliographystyle{plain}
* all failure modes for all componnts \bibliography{vmgbibliography,mybib}
}
Concept of FMMD
Look at the structure of software
* a natural hierarchy
Software written for a controlled
Contract programming
* describe concept
* describe how this fits in with failure modes and failure symptoms concepts
Describe how contract programming represents the failure modes of software
Now describe how this fis in with the structure of FMMD
%\today
\end{document}

File diff suppressed because it is too large Load Diff