1991
DOI: 10.1109/64.79706
|View full text |Cite
|
Sign up to set email alerts
|

Device understanding and modeling for diagnosis

Abstract: systems depend on the underlying model for their performance, fault coverage, cost, and brittleness. Many device models use a device's structure and behavior to simulate behavior based on local interactions between primitive components. These models are easily derived and seem to work for simple (mainly static) devices.As behavior becomes more complex, though, a more global view can provide a better insight into what a device is doing. Concepts dealing with abstractions of "raw" behavior reflect this global vi… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
8
0

Year Published

1993
1993
2001
2001

Publication Types

Select...
5
1
1

Relationship

0
7

Authors

Journals

citations
Cited by 44 publications
(8 citation statements)
references
References 5 publications
0
8
0
Order By: Relevance
“…After working with the Cover and Differentiate [8] model of problem solving for 7 man-months and following a structured prototyping approach, we realized that important behaviors and representations could not be captured by the model. Instead, for the purpose of guiding the acquisition phase and contributing to meeting the desired target system and environment characteristics, we found that the diagnosis method based on functional design models [1] was more appropriate. The whole re-design, re-adjustment, and reimplementation of the prototype occupied approximately two man-months 13 . In the Schedule project we have not yet performed a detailed evaluation of the "design by decomposition" model which is embedded in the prototype problem solving system that has been constructed so far.…”
Section: Selecting the Wrong Model May Be Costlymentioning
confidence: 98%
See 2 more Smart Citations
“…After working with the Cover and Differentiate [8] model of problem solving for 7 man-months and following a structured prototyping approach, we realized that important behaviors and representations could not be captured by the model. Instead, for the purpose of guiding the acquisition phase and contributing to meeting the desired target system and environment characteristics, we found that the diagnosis method based on functional design models [1] was more appropriate. The whole re-design, re-adjustment, and reimplementation of the prototype occupied approximately two man-months 13 . In the Schedule project we have not yet performed a detailed evaluation of the "design by decomposition" model which is embedded in the prototype problem solving system that has been constructed so far.…”
Section: Selecting the Wrong Model May Be Costlymentioning
confidence: 98%
“…According to [1] schematics about the processor boards under focus and documentations regarding the board's design and functional specification can fulfill the roles required by this method. This knowledge is available to TroTelC's domain expert.…”
Section: Multiple Generic Models May Applymentioning
confidence: 99%
See 1 more Smart Citation
“…GDE uses minimal entropy Ž as a measure to minimize the expected number of tests s additional observa-. 2 tions . FAULTY minimizes the estimated number of tests based on a variety of balanced global factors.…”
Section: Assumptions In System-environment Interactionmentioning
confidence: 98%
“…The most difficult point concerns the building of the ontology. Examples of using a model ontology construct to guide the diagnosis already exist in the domain of model-based reasoning, for example [2]. We have also succeeded in constructing ontology for developing medical diagnosis expert systems [6,10].…”
Section: Framework For Future Experimentsmentioning
confidence: 99%