Made this into a paper to
print it out easier.
This commit is contained in:
parent
ee1a2397f7
commit
30bf554f77
19
introduction/Makefile
Normal file
19
introduction/Makefile
Normal file
@ -0,0 +1,19 @@
|
|||||||
|
|
||||||
|
#
|
||||||
|
|
||||||
|
|
||||||
|
paper: paper.tex introduction_paper.tex
|
||||||
|
#latex paper.tex
|
||||||
|
#dvipdf paper pdflatex cannot use eps ffs
|
||||||
|
pdflatex paper.tex
|
||||||
|
cp paper.pdf introduction_paper.pdf
|
||||||
|
okular introduction_paper.pdf
|
||||||
|
|
||||||
|
|
||||||
|
# Remove the need for referncing graphics in subdirectories
|
||||||
|
#
|
||||||
|
introduction_paper.tex: introduction.tex paper.tex
|
||||||
|
cat introduction.tex | sed 's/introduction\///' > introduction_paper.tex
|
||||||
|
|
||||||
|
bib:
|
||||||
|
bibtex paper
|
@ -41,7 +41,15 @@ can determine an overall failure rate, in terms of probability of failure on dem
|
|||||||
The maturing of the application of the programmable electronic controller (PEC)
|
The maturing of the application of the programmable electronic controller (PEC)
|
||||||
for a wide range safety critical applications, has led to a fragmentation of subdisiplines
|
for a wide range safety critical applications, has led to a fragmentation of subdisiplines
|
||||||
which speak imperfectly to one another.
|
which speak imperfectly to one another.
|
||||||
The main three sub-disiplines are Electrical, Software and Mechanical Engineering.
|
This is because
|
||||||
|
the main three engineering disiplines, Electrical, Software and Mechanical Engineering
|
||||||
|
produced equipment that was interfaced a a later time.
|
||||||
|
Just as electronic circuitry becomes more integrated, and sub-domains
|
||||||
|
of electrical engineering (analog and digital for instance) are commonly found along-side on the same chip,
|
||||||
|
so modern PEC's are becoming more and more integrated and now typically encompass
|
||||||
|
input from the three engineering disciplines\footnote{Consider an aircraft, this involves expert knowledge from
|
||||||
|
Software, Electronic and Mechanical Engineering and requires a high degree of safety validation}.
|
||||||
|
|
||||||
Additional disiplines are defined by application area of the PEC. All of these sub-displines
|
Additional disiplines are defined by application area of the PEC. All of these sub-displines
|
||||||
are in turn split into even finer units.
|
are in turn split into even finer units.
|
||||||
The practicioners of these fields tend to view a PEC in different ways.
|
The practicioners of these fields tend to view a PEC in different ways.
|
||||||
@ -56,10 +64,22 @@ tool.
|
|||||||
For a anyone responsible for ensuring or proving the safety of a PEC must be able
|
For a anyone responsible for ensuring or proving the safety of a PEC must be able
|
||||||
to understand the process being controlled, the mechanical and electrical
|
to understand the process being controlled, the mechanical and electrical
|
||||||
sensors and actuators and the software. Not only must the
|
sensors and actuators and the software. Not only must the
|
||||||
safety engineer understand more than four potential disiplines, he/she
|
safety engineer understand more than four potential disciplines, he/she
|
||||||
must be able to trace failure modes of components to SYSTEM levels failure modes,
|
must be able to trace failure modes of components to SYSTEM levels failure modes,
|
||||||
and classify these according to their criticallity.
|
and classify these according to their criticallity.
|
||||||
|
|
||||||
|
\paragraph{Desire to introduce formal methods to static failure mode analysis}
|
||||||
|
There has been much work introducing formal methods into
|
||||||
|
the requirements and validation phases of electromechanical systems.
|
||||||
|
Apart from the ability to check, precisely, that what ha been
|
||||||
|
build behaves correctly and as requested, the process
|
||||||
|
of formal specification ensures that all important details are analysed
|
||||||
|
and looked at in detail.
|
||||||
|
It is an aim of this project to bring formal methods to
|
||||||
|
static failure mode analysis. This means being able to account for every base
|
||||||
|
component failure mode in a model, and to be able to represent
|
||||||
|
mechanical, electrical and software components in a single failure mode model.
|
||||||
|
|
||||||
\paragraph{Desirability of a common failure mode notation}
|
\paragraph{Desirability of a common failure mode notation}
|
||||||
Having a common failure mode notation accross all disciplines in a project
|
Having a common failure mode notation accross all disciplines in a project
|
||||||
would allow all the specialists to prepare failure mode
|
would allow all the specialists to prepare failure mode
|
||||||
|
36
introduction/paper.tex
Normal file
36
introduction/paper.tex
Normal file
@ -0,0 +1,36 @@
|
|||||||
|
|
||||||
|
\documentclass[a4paper,10pt]{article}
|
||||||
|
\usepackage{graphicx}
|
||||||
|
\usepackage{fancyhdr}
|
||||||
|
\usepackage{tikz}
|
||||||
|
\usetikzlibrary{shapes,snakes}
|
||||||
|
\usepackage{amsfonts,amsmath,amsthm}
|
||||||
|
\input{../style}
|
||||||
|
\usepackage{ifthen}
|
||||||
|
\usepackage{lastpage}
|
||||||
|
|
||||||
|
\newboolean{paper}
|
||||||
|
\setboolean{paper}{true} % boolvar=true or false
|
||||||
|
|
||||||
|
\begin{document}
|
||||||
|
\pagestyle{fancy}
|
||||||
|
\fancyhf{}
|
||||||
|
%\renewcommand{\chaptermark}[1]{\markboth{ \emph{#1}}{}}
|
||||||
|
\fancyhead[LO]{}
|
||||||
|
\fancyhead[RE]{\leftmark}
|
||||||
|
%\fancyfoot[LE,RO]{\thepage}
|
||||||
|
\cfoot{Page \thepage\ of \pageref{LastPage}}
|
||||||
|
\rfoot{\today}
|
||||||
|
\lhead{FMMD Introduction}
|
||||||
|
% numbers at outer edges
|
||||||
|
\pagenumbering{arabic} % Arabic page numbers hereafter
|
||||||
|
\author{R.P.Clark}
|
||||||
|
\title{FMMD Introduction}
|
||||||
|
\maketitle
|
||||||
|
\input{introduction_paper}
|
||||||
|
|
||||||
|
\bibliographystyle{plain}
|
||||||
|
\bibliography{../vmgbibliography,../mybib}
|
||||||
|
|
||||||
|
\today
|
||||||
|
\end{document}
|
Loading…
Reference in New Issue
Block a user