A comparison of languages which operationalise and formalise {KADS} models of expertise

In the field of Knowledge Engineering, dissatisfaction with the rapid-prototyping approach has led to a number of more principled methodologies for the construction of knowledge-based systems. Instead of immediately implementing the gathered and interpreted knowledge in a given implementation formalism according to the rapid-prototyping approach, many such methodologies centre around the notion of a conceptual model: an abstract, implementation independent description of the relevant problem solving expertise. A conceptual model should describe the task which is solved by the system and the knowledge which is required by it. Although such conceptual models have often been formulated in an informal way, recent years have seen the advent of formal and operational languages to describe such conceptual models more precisely, and operationally as a means for model evaluation. In this paper, we study a number of such formal and operational languages for specifying conceptual models. In order to enable a meaningful comparison of such languages, we focus on languages which are all aimed at the same underlying conceptual model, namely that from the KADS method for building KBS. We describe eight formal languages for KADS models of expertise, and compare these languages with respect to their modelling primitives, their semantics, their implementations and their applications. Future research issues in the area of formal and operational specification languages for KBS are identified as the result of studying these languages. The paper also contains an extensive bibliography of research in this area

The SEC-system : reuse support for scheduling system development

Recently, in a joint cooperation of Stichting VNA, SAL Apotheken, the Faculty of Management and Organization, and the University Centre for Pharmacy, University of Groningen in the Netherlands, a Ph.D-study started regarding Apot(he)ek, Organization and Management (APOM). The APOM-project deals with the structuring and steering of pharmacy organization. The manageability of the internal pharmacy organization, and the manageability of the direct environment of pharmacy organization is the subject matter. The theoretical background of the APOM-project is described. A literature study was made to find mixes of objectives. Three mixes of objectives in pharmacy organization are postulated; the product mix, the process mix, and the customer mix. The typology will be used as a basic starting point for the empirical study in the next phase of the APOM-project.

Multi-perspective modelling for knowledge management and knowledge engineering

ii It seems almost self-evident that “knowledge management ” and “knowledge engineering” should be related disciplines that may share techniques and methods between them. However, attempts by knowledge engineers to apply their techniques to knowledge management have been praised by some and derided by others, who claim that knowledge engineers have a fundamentally wrong concept of what “knowledge management” is. The critics also point to specific weaknesses of knowledge engineering, notably the lack of a broad context for the knowledge. Knowledge engineering has suffered some criticism from within its own ranks, too, particularly of the “rapid prototyping ” approach, in which acquired knowledge was encoded directly into an iteratively developed computer system. This approach was indeed rapid, but when used to deliver a final system, it became nearly impossible to verify and validate the system or to maintain it. A solution to this has come in the form of knowledge engineering methodology, and particularly in the CommonKAD

Knowledge-Level Reflection

This paper presents an overview of the REFLECT project. It defines the notion of knowledge level reflection that has been central to the project, it compares this notion with existing approaches to reflection in related fields, and investigates some of the consequences of the concept of knowledge level reflection: what is a general architecture for knowledge level reflection, how to model the object component in such an architecture, what is the nature of reflective theories, how can we design such architectures, and what are the results of our actual experiments with such systems

Reusable Knowledge-based Components for Building Software Applications: A Knowledge Modelling Approach

In computer science, different types of reusable components for building software applications were proposed as a direct consequence of the emergence of new software programming paradigms. The success of these components for building applications depends on factors such as the flexibility in their combination or the facility for their selection in centralised or distributed environments such as internet. In this article, we propose a general type of reusable component, called primitive of representation, inspired by a knowledge-based approach that can promote reusability. The proposal can be understood as a generalisation of existing partial solutions that is applicable to both software and knowledge engineering for the development of hybrid applications that integrate conventional and knowledge based techniques. The article presents the structure and use of the component and describes our recent experience in the development of real-world applications based on this approach

Knowledge based system development as an engineering process

This thesis was submitted for the degree of Doctor of Philosophy and awarded by Brunel University.Knowledge Based System (KBS) development is a difficult and challenging task, in particular in knowledge intensive domains. The traditional view of knowledge engineering is one of mining experts' knowledge and somehow transforming it into a machine usable form. This process, in general, suffers from insufficient or misconstrued representation of experts' problem solving behaviour. It is also unstructured and unduly biased at an early stage by design and implementation issues - normally in the form of incremental prototyping. We believe that both knowledge acquisition and KBS development for real life applications will require a 'structured' approach. This approach should harness a KBS developer's ability in extracting knowledge and developing systems. The structure should also be sufficiently flexible to allow the knowledge engineer to use his sense of creativity in developing a KBS. This thesis puts forward such a structured approach, in which KBS development is carried out in an engineering fashion. A process in which the worker is provided with an environment for developing knowledge based systems as an engineering process, as opposed to that of an artform or crafting. The main emphasis of this work is that part of the process which deals with the analysis and design phases in developing KBS. The analysis is performed at an 'epistemological' level, not coloured by design or implementation issues. The output of this phase captures both an expert's problem solving capability, and the business constraints placed upon the intended system. This is then used by the design process in order to create an optimal, workable, and elegant design architecture for the ultimate system.Commission for the European Communities' ESPRIT programme (Project Number 1098

Making diagnosis explicit

What is good diagnostic practice? The answer is elusive for many medical students and equally puzzling for those trying to build effective medical decision support systems. Much of the problem lies in the difficult of 'getting at' diagnosis. Expert diagnosticians find it difficult to introspect on their own strategies, thus making it difficult to pass on their expertise.Traditional knowledge acquisition methods are designed for gathering static domain knowledge and are inappropriate for the acquisition of knowledge about the diagnos¬ tic 'task'. More advanced knowledge acquisition methodologies, particularly those which focus on the modelling of problem-solving knowledge seem to hold more promise, but are not sufficiently practicable to allow anyone other than a knowledge engineer to operate directly. Given the difficulty experts have in accessing their own diagnostic strategies what is needed is a tool which would enable diagnosticians themselves to directly formu¬ late and experiment with their own methods of diagnosis.This research describes the development of a knowledge acquisition methodology geared specifically towards the exposition of medical diagnosis. The methodology is implemented as a toolkit enabling exploration and construction of medical diagnostic models and production of model-based medical diagnostic support systems. The toolkit allows someone skilled in diagnosis to articulate their diagnostic strategy so that it can be used by those with less experience

DEKAS - An evolutionary case-based reasoning system to support protection scheme design

This paper describes a decision support system being developed in conjunction with two UK utility companies to aid the design of electrical power transmission protection systems. A brief overview of the application domain is provided, followed by a description of the work carried out to date concerning the development and deployment of the Design Engineering Knowledge Application System (DEKAS). The paper then discusses the provision of intelligent decision support to the design engineer through the application of case-based reasoning (CBR). The key benefits from this will be outlined in conjunction with a relevant case study