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

After Paper acceptance, this is the final draft

Browse Source 
with a last paragraph to address reveiewer
comments.
This commit is contained in:
Robin Clark 2011-08-05 15:17:50 +01:00
parent f45896b222
commit 84855b9f43
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
fmmd_concept/System_safety_2011/submission.tex
View File

@ -1269,6 +1269,13 @@ Furthermore the reasoning path is traceable. By being able to trace a
top level event down through derived components, to base component top level event down through derived components, to base component
failure modes, with each step annotated as {\fcs}, the model is easier to maintain. failure modes, with each step annotated as {\fcs}, the model is easier to maintain.
The example used here is deliberately small for the purpose
of being presented in a six page paper. FMMD has been applied
to larger systems encompassing mechanical, electrical and software
elements. FMMD represents a new technique in that it
can address all the criteria in table 3, whereas the other methodologies
can only cover some.
\paragraph{Future work} \paragraph{Future work}
\begin{itemize} \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 provide bounds on the size of the state space for the application of the methodology to certain classes of systems.