Knowledge Engineering Suite: A Tool to Create Ontologies for Automatic Knowledge Representation in Knowledge-Based Systems

Author(s):  
Tania Cristina D’Agostini Bueno ◽  
Hugo Cesar Hoeschl ◽  
Andre Bortolon ◽  
Eduardo Mattos ◽  
Cristina Souza Santos
1995 ◽  
Vol 10 (3) ◽  
pp. 269-300 ◽  
Author(s):  
John K. C. Kingston ◽  
Jim G. Doheny ◽  
Ian M. Filby

AbstractThe KADS methodology and its successor, CommonKADS, have gained a reputation for being useful approaches to building knowledge-based systems in a manner which is both systematic and well documented. However, these methods require considerable effort to use them completely. It has been suggested that automated support for KADS or CommonKADS users, in the form of “knowledge engineering workbenches”, could be very useful. These tools would provide computerised assistance to knowledge engineers in organising and representing knowledge, in a similar fashion to the support which CASE tools provide for software engineers. To provide support for KADS or CommonKADS, the workbenches should provide specific support for the modelling techniques recommended by these methods, which are very detailed in the representation and analysis stages of knowledge engineering. A good knowledge engineering workbench should also be easy to use, should be robust and reliable, and should generate output in a presentable format.This paper reports on an evaluation of two commercially available workbenches for supporting the KADS approach: KADS Tool from ILOG and Open KADS Tool from Bull. This evaluation was carried out by AIAI as part of the CATALYST project, funded by the European Community's ESSI programme, which aimed to introduce CommonKADS to two technology-oriented companies. Information is also presented on two other workbenches: the CommonKADS workbench (which will soon become commercially available) and the VITAL workbench. The results show various strengths and weaknesses in each tool.


Author(s):  
Ram Kumar ◽  
Shailesh Jaloree ◽  
R. S. Thakur

Knowledge-based systems have become widespread in modern years. Knowledge-base developers need to be able to share and reuse knowledge bases that they build. As a result, interoperability among different knowledge-representation systems is essential. Domain ontology seeks to reduce conceptual and terminological confusion among users who need to share various kind of information. This paper shows how these structures make it possible to bridge the gap between standard objects and Knowledge-based Systems.


1994 ◽  
Vol 9 (2) ◽  
pp. 105-146 ◽  
Author(s):  
Dieter Fensel ◽  
Frank van Harmelen

AbstractIn the field of knowledge engineering, dissatisfaction with therapid-prototypingapproach has led to a number of more principled methodologies for the contruction 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 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. 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.


Author(s):  
JONATHAN LEE ◽  
JOHN YEN

Several methodologies have been developed to enhance the software life cycle of knowledge-based systems by emphasizing on the use of both prototypes and specifications. However, these methodologies focus on the development phase of knowledge-based systems. The roles of prototypes and specifications in the maintenance phase has not been fully explored. Because a suitable problem specification for a knowledge-based system is often difficult to acquire, validating changes to non-executable solution specification during the maintenance phase can be a problem. To address this, we propose an alternative paradigm in which the prototype complements the specification throughout the life cycle. The traceability between them is facilitated by organizing both types of artifacts using a common functional decomposition structure. Based on our task-based specification methodology (TBSM), we have also developed a knowledge engineering tool (called TAME) to facilitate the acquisition and the organization of the specification and the prototype. The proposed methodology and the tool together can thus enhance the verification, validation, and the maintenance of knowledge-based systems through their life cycles.


2010 ◽  
Vol 108-111 ◽  
pp. 123-128
Author(s):  
Ting Zeng

Knowledge management and knowledge engineering is two important concepts, in recent years. Knowledge Engineering is the engineering solution of the system, emphasizing the process of the acquisition of knowledge and knowledge on behalf of knowledge-based systems in the uncertain process requirements. The purpose of this paper is to discuss how to use the basic principles of knowledge engineering in order to promote knowledge management.


Author(s):  
TIM MENZIES ◽  
KLAUS-DIETER ALTHOFF ◽  
YANNIS KALFOGLOU ◽  
ENRICO MOTTA

At the SEKE'99 conference, knowledge engineering researchers held a panel on the merits of meta-knowledge (i.e. problem solving methods and ontologies) for the development of knowledge-based systems. The original panel was framed as a debate on the merits of meta-knowledge for knowledge maintenance [21]. However, the debate quickly expanded. In the end, we were really discussing the merits of different technologies for the specification of reusable components for KBS. In this brief article we record some of the lively debate from that panel and the email exchanges it generated.


Sign in / Sign up

Export Citation Format

Share Document