|4.15 Elementary Method "Expertise Model" (EXPM)|
An Expertise Model describes the required problem solution behavior of a knowledge-based system and the task-oriented knowledge structure. The problem solution behavior of the human expert is input for the expertise model. It is to model the solving of a problem on domain and task related knowledge levels without referring to knowledge presentation and implementation details.
Means of Representation
The Expertise Model can be specified in three different ways: verbally, conceptually or formally. The most common form is the conceptual way by using diagrams and a conceptual modeling language (CML)-see also /Gustafsson, 1994/ chapter 11.1 and /Wielinga, 1994/ Annex A, whereby the diagrams only represent overviews and the complete modeling is realized in CML. The diagrams are concept relation diagrams and inference structures.
The generation of an expertise is done in increments where more detailed structures are created in every design increment. A design direction (top-down, bottom-up, etc.) is not specified. The Expertise Model is generated in an overall system for all those tasks that are identified as knowledge-intensive. In this connection, the following aspects and model parts have to be analysed and specified:
The generation of an Expertise Model requires the application of a tool in all cases that are not trivial, in order to collect the various knowledge components and their connections. This is the only way to collect, assess and document the Expertise Model without too much time or effort.
|4.1||SD1.5 - User-Level System Structure||
Based on the application system described in activity SD1.2 - Description of Application System an Expertise Modell has to be generated for any task characterized as knowledge -intensive. From a professional point of view, the required problem solution knowledge and the problem solution process must be so minutely described that all relevant concepts, reactions, inferences, tasks (in the sense of the expertise model) as well as their relationship to each other are covered. The problem solution knowledge and the problem solution process are updated and completed by means of an incremental development so further inquiries regarding the knowledge about the problem field and the solution process are not required in the subsequent technical system design.
The method covers subproduct User Requirements.Description of the Functionality.
|No.||Interface||Observation||Information in Annex 1|
|5.1||EXPM-FCTD||The results of a preliminary functional decomposition from a professional point of view-within the scope of activity SD1.2 - Description of Application System-are initial information for the expertise model. For any of the functions there described it must be decided if they are knowledge-intensive. If this is the case, an expertise model has to be generated.|
|5.2||EXPM-ODT||The Expertise Model is the basis of the technical design for the modeled system portion. Method ODT - Object Design Technique can be one possibility to design the representation of the required knowledge and the sequences in the problem solution process.|
|5.3||EXPM-STRD||The Expertise Model is the basis of the technical design for the modeled system portion. Method STRD - Structured Design may present a possibility to design the representation of the required knowledge and the sequences in the problem solution process.|
|GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster|