Knowledge Engineering Environment
This article may meet Wikipedia's criteria for speedy deletion because: because Finnusertop is a moron. For valid criteria, see CSD.
If this article does not meet the criteria for speedy deletion, or you intend to fix it, please remove this notice, but do not remove this notice from pages that you have created yourself. If you created this page and you disagree with the given reason for deletion, you can click the button below and leave a message explaining why you believe it should not be deleted. You can also visit the talk page to check if you have received a response to your message. Note that this article may be deleted at any time if it unquestionably meets the speedy deletion criteria, or if an explanation posted to the talk page is found to be insufficient.
Note to administrators: this article has content on its talk page which should be checked before deletion. Administrators: check links, talk, history (last), and logs before deletion. Consider checking Google.This page was last edited by 216.53.168.62 (contribs | logs) at 20:06, 9 May 2019 (UTC) (6 years ago) |
| Developer(s) | IntelliCorp |
|---|---|
| Initial release | 1983 |
| Written in | Common Lisp |
| Platform | Symbolics Lisp Machine, HP 9000 Series 700 and 800 workstations, the Sun SPARCstation and IBM RS6000 workstation |
| Available in | English |
| Type | Expert system development tool |
| License | Proprietary |
Knowledge Engineering Environment (KEE) is a frame-based development tool for expert systems.[1] It was developed and sold by IntelliCorp, and first released in 1983. It ran on Lisp machines, and was later ported to Lucid Common Lisp with the CLX library, an X Window System (X11) interface for Common Lisp. This version was available on several different UNIX workstations.
On KEE, several extensions were offered:
- Simkit, a frame-based simulation library[2][3]
- KEEconnection, database connection between the frame system and relational databases[4]
In KEE, frames are called units. Units are used for both individual instances and classes. Frames have slots and slots have facets. Facets can describe, for example, a slot's expected values, its working value, or its inheritance rule. Slots can have multiple values. Behavior can be implemented using a message passing model.
KEE provides an extensive graphical user interface (GUI) to create, browse, and manipulate frames.
KEE also includes a frame-based rule system. In the KEE knowledge base, rules are frames. Both forward chaining and backward chaining inference are available.
KEE supports non-monotonic reasoning through the concepts of worlds. Worlds allow providing alternative slot-values of frames. Through an assumption-based truth or reason maintenance system, inconsistencies can be detected and analyzed.[5]
ActiveImages allows graphical displays to be attached to slots of Units. Typical examples are buttons, dials, graphs, and histograms. The graphics are also implemented as Units via KEEPictures, a frame-based graphics library.
See also
- Expert system
- Frame language
- Inference engine
- IntelliCorp (software)
- Knowledge base
- Knowledge-based system
- Knowledge representation
