During the development of new and complex electronic products, the developer identifies high-risk components by listing those components that could generate project risk based on past experience, also adding those new components with limited history. These critical items are key to product performance and, therefore, are an area of major concern during product development. Critical items are issues not totally understood by the program's development staff, even though these individuals will be specifying and designing these items into the end product. The applications for which critical items are used can have major effects on the reliability of the critical items as well as on the products that incorporate them. Critical items are normally purchased from specialty suppliers, who design and manufacture them to a procurement specification. Critical items are classified as program risks and constitute a subset of a program's total risk area that must be managed. Critical items are considered to be risk items because they are unique to the program (custom-designed), can embody new technologies or processes, can be state of the art (pushing the envelope of knowledge and understanding), can have higher failure rates than other components, can be life-limited, and can jeopardize safety. Critical items have enough technical and programmatic uncertainties within themselves that must be mitigated and managed by the program development staff, without adding critical item design application issues resulting from product design decisions. This paper describes a current effort that focuses on solutions for these issues.
[1]
John H. Boose,et al.
Selecting Knowledge Acquisition Tools and Strategies Based on Application Characteristics
,
1989,
Int. J. Man Mach. Stud..
[2]
Jack V. Michaels,et al.
Technical Risk Management
,
1996
.
[3]
Nancy J. Cooke,et al.
Varieties of knowledge elicitation techniques
,
1994,
Int. J. Hum. Comput. Stud..
[4]
John P. Cushman.
Managing Concurrent Engineering: Buying Time to Market, Jon Turino. Van Nostrand Reinhold, New York (1992), 154+xvi pages. $39.95
,
1992
.
[5]
R T Anderson.
Reliability Design Handbook
,
1976
.
[6]
J. P. Pennell,et al.
Concurrent engineering: practices and prospects
,
1989,
IEEE Global Telecommunications Conference, 1989, and Exhibition. 'Communications Technology for the 1990s and Beyond.
[7]
John H. Boose,et al.
Choosing knowledge acquisition strategies for application tasks
,
1991
.
[8]
Anna Hart,et al.
Knowledge acquisition for expert systems
,
1988
.
[9]
John Millar Carroll,et al.
Managing Risk: A Computer Aided Strategy
,
1984
.
[10]
Kevin Magee,et al.
The elicitation of knowledge from designers
,
1987
.