Results 1 -
3 of
3
Assumptions of Problem-Solving Methods
- LECTURE NOTES IN ARTIFICIAL INTELLIGENCE, 1076, 9TH EUROPEAN KNOWLEDGE ACQUISITION WORKSHOP, EKAW-96
, 1996
"... Assumptions of problem-solving methods refer to necessary applicability conditions of problem-solving methods, indicating that a problem-solving method is only applicable to realize a task, if the assumptions are met. In principle, such assumptions may refer to any kind of condition involved in a ..."
Abstract
-
Cited by 40 (14 self)
- Add to MetaCart
Assumptions of problem-solving methods refer to necessary applicability conditions of problem-solving methods, indicating that a problem-solving method is only applicable to realize a task, if the assumptions are met. In principle, such assumptions may refer to any kind of condition involved in a problem-solving method's applicability, including its required domain knowledge. In this paper, we propose a conceptual organization for assumptions of problem-solving methods and suggest a formal language to describe them. For illustration we take examples from the Propose & Revise problem-solving method and from diagnosis.
Domain and Task Modeling in MIKE
- In Proceedings of the IFIP WG8.1/13.2 Joint Working Conference on Domain Knowledge for Interactive System Design
, 1996
"... The paper describes the MIKE (Model-based and Incremental Knowledge Engineering) approach for the development of knowledge-based systems (kbs). It integrates semiformal specification techniques, formal specification techniques, and prototyping into a coherent framework. This allows the domain and ta ..."
Abstract
-
Cited by 14 (5 self)
- Add to MetaCart
The paper describes the MIKE (Model-based and Incremental Knowledge Engineering) approach for the development of knowledge-based systems (kbs). It integrates semiformal specification techniques, formal specification techniques, and prototyping into a coherent framework. This allows the domain and task model of a kbs to be described on different formalization levels. All activities in the building process are embedded in a cyclic life cycle model. For the semiformal representation we use a hypermedia-based formalism which serves as a communication basis between expert and knowledge engineer during knowledge acquisition. The semiformal knowledge representation is also the basis for formalization, resulting in a formal and executable model of expertise specified in the Knowledge Acquisition and Representation Language (KARL). Since KARL is executable the model of expertise can be developed and validated by prototyping. A smooth transition from a semiformal to a formal specification and fu...
Requirements Specification and Model-based Knowledge Engineering
, 1997
"... Knowledge Engineering (KE) and Software Engineering (SE) have similar goals: developing methods, techniques, and tools for the building process of either knowledge based systems (kbs) or (complex) traditional software. Due to this kinship it seems obvious to analyse to which extent both areas, KE an ..."
Abstract
- Add to MetaCart
Knowledge Engineering (KE) and Software Engineering (SE) have similar goals: developing methods, techniques, and tools for the building process of either knowledge based systems (kbs) or (complex) traditional software. Due to this kinship it seems obvious to analyse to which extent both areas, KE and SE, can benefit from each other. In this paper we want to argue from the KE point of view. The main paradigm in KE has switched from a transfer point of view to a modeling point of view. So a lot of emphasis has been put on the development of notions and methods for building and structuring models, which capture different results of the development process. Much effort has been investigated into the analysis and development of reusable components: problem solving methods describing the dynamic behaviour of kbs and ontologies defining the vocabulary and structure of (domain) models. We describe specific approaches in KE in some detail which exploit these ideas in different ways: Role-Limiting Methods, KADS and MIKE. Finally Life Cycle Models, Non Functional Requirements and Transformational Development are discussed as areas where we think KE might profit from research and experiences made in SE.

