RuleWorks

A Framework for Model-Based Adaptive Training

Model Ontology

An essential aspect for any model is its ontology. This dimension concerns the fundamental source of knowledge that is used to establish the model. The ontology can be established from theoretical or empirical sources. Empirical knowledge is sometimes used in expert systems by encoding properties directly into rules as they are gained from knowledge acquisition. So called ‘second generation’ expert systems attempt to employ both theoretical and empirical knowledge sources. A theoretical source is generally structured in libraries which define subject specific properties, attributes, relations and expressions. These libraries can be represented as object-oriented data structures. The representation of different model ontologies in libraries opens up almost endless possibilities. Structures to carry multiple ontologies can be activated (as needed) in Workmanship-MOBAT problem spaces. However, research in multiple libraries for the ontology dimension is beyond the scope of this work.

Figure 6-4 Workmanship-MOBAT Object Oriented Structures

Figure 6-4 Workmanship-MOBAT Object Oriented Structures

Model ontology is considered constant in the Workmanship-MOBAT domain. That is, the training system does not switch from one model ontology to another in the workmanship domain. The use of standard terminology in the Workmanship-MOBAT domain is important, in order to promote the use of company defined terms to describe quality aspects of printed circuit boards. In Workmanship-MOBAT, the theoretical source defining the domain model is expressed in object-oriented views for components, definitions, topics, defects, causes, fixes, preventions, conclusions, dispositions, checksand repairs. Each view contains detailed properties, attributes, relations, expressions and links to other objects. For example, a ‘defect’ object inherits links to appropriate supporting expertise objects (e.g., text, figures, pictures), but has its own attributes for defect code, type, reporting-category and disposition-default. Similarly, a “component” object inherits attributes from the domain and has links to other objects. A partial structure for these objects in Workmanship-MOBAT with sample values is shown in Figure 6-4.

*
Flower Show
  *  
© RuleWorks.co.uk | | Sitemap