Morning work...

mybib.bib

@@ -223,6 +223,19 @@ ISSN={0149-144X}}
 %%#%%
 
 
+
+@INPROCEEDINGS{incrementalfmea,
+author={Price, C.J.},
+booktitle={Reliability and Maintainability Symposium, 1996 Proceedings. International Symposium on Product Quality and Integrity., Annual}, title={Effortless incremental design FMEA},
+year={1996},
+month={jan},
+volume={},
+number={},
+pages={43 -47},
+keywords={Automotive engineering;Circuits;Costs;Design engineering;Failure analysis;Filling;Fires;Performance analysis;Power engineering and energy;Software tools;circuit analysis computing;circuit reliability;design engineering;failure analysis;Flame system;computer simulation;electrical engineering;electrical systems;failure mode and effects analysis;incremental design FMEA;reliability;software;},
+doi={10.1109/RAMS.1996.500640},
+ISSN={0149-144X},}
+
 @ARTICLE{sfmea,
   AUTHOR =       "Chris Price, Neal Snooke",
   TITLE =        "An Automated Software FMEA",
@@ -231,9 +244,56 @@ ISSN={0149-144X}}
 }
 
 % my bib file.
+@INPROCEEDINGS{automatingFMEA1281774,
+author={Papadopoulos, Y. and Parker, D. and Grante, C.},
+booktitle={High Assurance Systems Engineering, 2004. Proceedings. Eighth IEEE International Symposium on}, title={Automating the failure modes and effects analysis of safety critical systems},
+year={2004},
+month={march},
+volume={},
+number={},
+pages={ 310 - 311},
+keywords={Aerospace engineering;Aerospace industry;Aerospace safety;Automotive engineering;Cause effect analysis;Computer architecture;Data engineering;Failure analysis;Performance analysis;Software performance; data flow analysis; fault trees; safety-critical software; software architecture; software fault tolerance; FMEA; component failure modes; data flow; data transactions; failure effect analysis; failure mode analysis; fault simulation; fault tree analysis; safety critical systems; software design; software development; system models; system safety analysis; system topology;},
+doi={10.1109/HASE.2004.1281774},
+ISSN={1530-2059},}
 
+
+@INPROCEEDINGS{1372150,
+author={Hartkopf, S.},
+booktitle={Software Technology and Engineering Practice, 2003. Eleventh Annual International Workshop on}, 
+title={From a single discipline risk management approach to an interdisciplinary one: adaptation of FMEA to software needs},
+year={2003},
+month={sept.},
+volume={},
+number={},
+pages={ 204 - 213},
+keywords={Automotive engineering;Computer industry;Electrical engineering;Engineering management;Failure analysis;Organizations;Production engineering;Project management;Risk management;Software engineering; failure analysis; project management; risk management; software development management; FMEA adaptation; STEP2003; Workshop of Interdisciplinary Software Engineering; failure modes-and-effects analysis; interdisciplinary projects; interdisciplinary risk management; nonsoftware products; project management task; single discipline risk management; software needs; software products;},
+doi={10.1109/STEP.2003.12},
+ISSN={},}
+
+
+@INPROCEEDINGS{5754453,
+author={Snooke, N. and Price, C.},
+booktitle={Reliability and Maintainability Symposium (RAMS), 2011 Proceedings - Annual}, title={Model-driven automated software FMEA},
+year={2011},
+month={jan.},
+volume={},
+number={},
+pages={1 -6},
+keywords={Analytical models;Fault diagnosis;Hardware;Programming;Software;Testing;Unified modeling language;safety-critical software;MISRA C;component diagrams;low-level languages;low-level programming;model-driven automated software FMEA;model-driven software developments;safety critical embedded systems;sequence diagrams;software development philosophy;software effects analysis;software failure mode;source code embedded testing;state charts;use case diagram;Failure modes and effects analysis;model-driven software development;software FMEA;},
+doi={10.1109/RAMS.2011.5754453},
+ISSN={0149-144X},}
 Baiqiao HUANG
-
+@INPROCEEDINGS{FMECAresearch,
+author={Ying Chen and Cui Ye and Bingdong Liu and Rui Kang},
+booktitle={Prognostics and System Health Management (PHM), 2012 IEEE Conference on}, title={Status of FMECA research and engineering application},
+year={2012},
+month={may},
+volume={},
+number={},
+pages={1 -9},
+keywords={automobile industry;electronics industry;failure analysis;military standards;product quality;reliability;research and development;risk analysis;China;FMECA automotive industries standards;FMECA electronic industries standards;FMECA engineering application status;FMECA military standards;FMECA research status;FMECA technology;NEC;Philips;QS9000;RPN;computer aided analysis;data accumulation;failure mode analysis methods;failure mode effect and criticality analysis;inter-department cooperation;international companies;product reliability;reliability analysis method;risk analysis;risk assessment;simulation tools;timed FMECA;FMECA;application status;current research;failure mechanism;standard;},
+doi={10.1109/PHM.2012.6228914},
+ISSN={2166-563X},}
 
 Software FMEA Approach Based on Failure Modes
 Database

submission_thesis/CH1_introduction/copy.tex

@@ -75,8 +75,8 @@ use.
 It then reveals common flaws 
 which make them unsuitable for the higher safety requirements of the 21st century.
 %
-Problems with state explosion in failure mode reasoning and the impossibility
-of integrating software and hardware failure mode models are the most obvious of these. %flaws.
+Problems with state explosion in failure mode reasoning and the current impossibility
+of integrating software and hardware failure mode models~\cite{1372150} are the most obvious of these. %flaws.
 %
 The four current methodologies are described in chapter~\ref{sec:chap2} and %the advantages and drawbacks
 %of each FMEA variant are examined 

submission_thesis/CH2_FMEA/copy.tex

@@ -33,6 +33,9 @@ how failures could affect some equipment in %an initial
 a brain-storming session
 %in product design, 
 to formal submission as part of safety critical certification.
+When performed as part of a safety critical certification process FMEA
+is a time consuming business. To reduce amount of work to perform,
+software packages and analysis strategies have been developed~\cite{incrementalfmea, automatingFMEA1281774}.
 %
 FMEA is always performed in context. That is, the equipment is always analysed for a particular purpose
 and in a given environment. An `O' ring for instance can fail by leaking
@@ -725,9 +728,10 @@ will return most cost benefit.
 %  \caption{A10 Thunderbolt}
 %  \label{fig:f16missile}
 % \end{figure}
-Emphasis on determining criticality of failure.
-Applies some Bayesian statistics (probabilities of component failures and those thereby causing given system level failures).
-~\cite{bayesfrequentist}
+Emphasis on determining criticality rather than the cost of system failures.
+Applies some Bayesian statistics (probabilities of component failures and those 
+thereby causing given system level failures)~\cite{bayesfrequentist}.
+A history of the usage and development of FMECA may be found in~\cite{FMECAresearch}.