Information Technology Reference
In-Depth Information
TABLE 16.2
(Continued)
Year
Reference
Contribution
Noted that current design controls can
include design reviews, walk throughs,
inspections, complexity analysis, and
coding standards.
Argued that because reliable empirical
numbers for occurrence values are difficult
or impossible to establish, FMEA teams
can set all occurrences to a value of 5 or 10.
Noted that detection numbers are highly
subjective and heavily dependent on the
experience of the FMEA team.
Bouti, A., Kadi, D.A. &
Lefran¸ois, P., An Integrative
Functional Approach for
Automated Manufacturing
systems modeling. Integrated
Computer-Aided
Engineering, 5(4), pp.
333-348, 1998.
Bouti, Kadi, and Lefran¸ois:
Described the use of FMEA in an automated
manufacturing cell.
Noted that a good functional description of the
system is necessary for FMEA.
Recommended the use of an overall model that
clearly specifies the system functions.
Suggested the use of system modeling
techniques that facilitate communication and
teamwork.
Argued that it is impossible to perform a
failure analysis when functions are not well
defined and understood.
Pointed out that failure analysis is possible
during the design phase because the functions
are well established by then.
Noted that when several functions are
performed by the same component, possible
failures for all functions should be considered.
Stalhane, T. & Wedde, K.J.,
Modification of Safety
Critical Systems: An
Assessment of three
Approached,
Microprocessors and
Microsystems, 21(10), pp.
611-619, 1998.
Stalhane and Wedde:
Used FMEA with a traffic control system in
Norway.
Used FMEA to analyze changes to the system.
Noted that potentially any change involving an
assignment or a procedure call can change
system parameters in a way that could
compromise the system's safety. The FMEA
pointed out code segments or procedures
requiring further investigation.
 
Search WWH ::




Custom Search