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

iet_abstract.doc produced

Browse Source
This commit is contained in:
Robin P. Clark 2012-05-01 10:15:36 +01:00
parent 244b6685b0
commit 03493d6f81
2 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
papers/fmmd_software_hardware/abs.tex
View File

@ -14,14 +14,14 @@ for static testing. Its use is traditionally applied to hardware (electrical and
With the increasing use of micro-controllers in smart~instruments and control~systems, With the increasing use of micro-controllers in smart~instruments and control~systems,
software is increasingly being seen as the `missing~factor' in FMEA analysis. software is increasingly being seen as the `missing~factor' in FMEA analysis.
% %
This paper presents a new modular variant of FMEA, Failure Mode Modular De-Composition (FMMD). This paper presents a new modular variant of FMEA, Failure Mode Modular Decomposition (FMMD).
% %
Because FMMD is modular and hierarchical, and deals with all its objects in terms of their failure mode behaviour, Because FMMD is modular and hierarchical, and deals with all its objects in terms of their failure mode behaviour,
it is ideally suited to creating integrated software and hardware models. it is ideally suited to creating integrated software and hardware models.
% %
This paper takes a simple example of a hardware/software hybrid (an industry standard {\ft} input), analyses %%This paper takes a simple example of a hardware/software hybrid (an industry standard {\ft} input), analyses
the hardware and software using FMMD, and then discusses the effectiveness of the %%the hardware and software using FMMD, and then discusses the effectiveness of the
failure modelling from the perspective of the hybrid hardware/software sub-system. %%failure modelling from the perspective of the hybrid hardware/software sub-system.
@ -78,10 +78,10 @@ over traditional FMEA.
% %
This paper presents an overview of the FMMD methodology and then an FMMD analysis of a simple software/hardware hybrid sub-system. This paper presents an overview of the FMMD methodology and then an FMMD analysis of a simple software/hardware hybrid sub-system.
% %
The example sub-system chosen is a {\ft} input circuit consisting of The example system chosen is a {\ft} input circuit consisting of
a resistive element, multiplexer (MUX), Analogue to Digital Converter (ADC) and two software functions. a resistive element, multiplexer (MUX), Analogue to Digital Converter (ADC) and two software functions.
% %
The purpose of this sub-system is to convert an electrical current signal into a value for use in software. The purpose of this system is to convert an electrical current signal into a value for use in software.
% %
FMMD is applied to the hardware (resistive element, MUX and ADC) and FMMD is applied to the hardware (resistive element, MUX and ADC) and
to the software components (two `C' functions), producing one integrated to the software components (two `C' functions), producing one integrated
@ -96,7 +96,8 @@ The failure model is then discussed and compared with heuristic
knowledge of {\ft} inputs, circuitry and software. knowledge of {\ft} inputs, circuitry and software.
% %
Conclusions are then presented listing the benefits and draw-backs Conclusions are then presented listing the benefits and draw-backs
of analysing the hardware/software hybrid system using FMMD. of analysing the hardware/software hybrid system using FMMD, and FMMD
is compared with traditional HFMEA and SFMEA.
\clearpage \clearpage

BIN
papers/fmmd_software_hardware/iet_abstract.doc Normal file
View File

Binary file not shown.