Browse Prior Art Database

Knowledge Base Editor Graphical User Interface Design

IP.com Disclosure Number: IPCOM000114642D
Original Publication Date: 1995-Jan-01
Included in the Prior Art Database: 2005-Mar-29
Document File: 2 page(s) / 68K

Publishing Venue

IBM

Related People

Huang, G: AUTHOR [+4]

Abstract

This disclosure addresses the Graphical User Interface (GUI) design of the Knowledge Base Editor for the LAN SERVER SPECIALIST system. The LAN SERVER SPECIALIST system is a problem determination tool for IBM* LAN Server 3.0 and 4.0*. It analyzes and correlates the error messages issued by LAN Servers and LAN Requesters in real-time, and reports possible causes and recommended actions.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Knowledge Base Editor Graphical User Interface Design

      This disclosure addresses the Graphical User Interface (GUI)
design of the Knowledge Base Editor for the LAN SERVER SPECIALIST
system.  The LAN SERVER SPECIALIST system is a problem determination
tool for IBM* LAN Server 3.0 and 4.0*.  It analyzes and correlates
the error messages issued by LAN Servers and LAN Requesters in
real-time, and reports possible causes and recommended actions.

      The Editor GUI design is based on causal model of LAN Server
(see another invention disclosure).  The causal model of LAN Server
describes relationship between error messages, problem causes, and
recommended actions.  The editor GUI is designed so that users can
easily edit these relationships.  The relationships include:
  1.  MESSAGE-CAUSE relationship: it is called the "cause"
       relationship.  This is a many-to-many relationship.  One
message
       may correspond to several causes, and one cause may correspond
to
       several messages.  Users might want to edit the message-cause
       relationship from both the message point of view or from the
       cause point of view;
  2.  CAUSE-ACTION relationship: this is a one-to-many relationship.
       One cause might need several alternative recommended actions;
  3.  MESSAGE-MESSAGE relationship: it is called the "trigger"
       relationship.  Again, it is a many-to-many relationship.
Users
       might want to edit from the "triggering" point of view, or
from
       the "triggered" point of view;
  4.  CAUSE-CAUSE relationship: this is called the "imply"
     ...