robin/Robin_PHD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

FINAL because I am going down the pub

Browse Source
This commit is contained in:
Robin Clark 2011-06-28 18:12:23 +01:00
parent 1b4aecc211
commit f45896b222
1 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
fmmd_concept/System_safety_2011/submission.tex
View File

@ -73,7 +73,7 @@ failure mode of the component or sub-system}}}
% 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, 25 North Street, Lewes, BN7 2PE, UK} \and $^\dagger${\em University of Brighton, UK}
$^\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}
@ -203,7 +203,7 @@ If $E$ is the number of environmental conditions to consider
in a system, and $A$ the number of applied/operational states (or modes of the system),
the bottom-up analyst is presented with two
additional %cross product
factors,
factors, yielding approximately
$(N-1) \times N \times K \times E \times A$.
%
If we put some typical very small embedded system numbers\footnote{These figures would
@ -364,12 +364,12 @@ that interact to provide
a function or task within a system.
%
In the proposed methodology components are collected into functional groups
and each component failure (and optionally combinations) are considered in the
and each component failure (and possibly multiple simultaneous component failures) are considered in the
context of the {\fg}.
%% GARK
%
The component failures (and optional combinations) are termed {\em{\fcs}}. %`test~cases'.
The component failures are termed {\em{\fcs}}. %`test~cases'.
For each {\fc}
there will be a corresponding resultant failure, or `symptom', from the perspective of the {\fg}.
%
@ -1269,7 +1269,12 @@ Furthermore the reasoning path is traceable. By being able to trace a
top level event down through derived components, to base component
failure modes, with each step annotated as {\fcs}, the model is easier to maintain.
\paragraph{Future work}
\begin{itemize}
\item To provide bounds on the size of the state space for the application of the methodology to certain classes of systems.
\item To build a {\dcs} library of common electrical, mechanical and software models (i.e. a collection of worked example {\dcs}).
\item To provide formal generic translations from the constructed model of any given system to the other models.
\end{itemize}
%\today
%
{ %\tiny %\footnotesize