Beruflich Dokumente
Kultur Dokumente
knowledge base,
. The knowledge base contains the rules and associations of compiled data which
most often take the form of IF-THEN rules. If this was a system for determining drug
interactions, then a rule might be that IF drug X is taken AND drug Y is taken THEN
alert user. Using another interface, an advanced user could edit the knowledge base
to keep it up to date with new drugs
The knowledge base is the heart of the system and contains the knowledge needed
for solving a specific problem. The knowledge may be in the form of facts, heuristics
(e.g. experiences, opinions, judgments, predictions, algorithms) and relationships
usually gleaned from the mind of experts through specific knowledge acquisition
methods (e.g. interview) in the relevant domain. Knowledge can be represented
using a variety of representation techniques (e.g. semantic nets, frames, predicate
logic) (Ignizio, 1991; Mital and Anand, 1994), but the most commonly used technique
is if-then rules, also known as production rules.
inference engine
The inference engine combines the rules from the knowledge base with the patients
data.
The inference engine is employed during a consultation session, examines the status
of the knowledge base, handles the content of the knowledge base and determines
the order in which inferences are made. It may use various inference methods. Many
inference engines have the capability for reasoning in the presence of uncertainty
The communication mechanism will allow the system to show the results to the user
as well as have input into the system
The user interface part enables interaction of the system with the user. It mainly
includes screen displays, a consultation/advice dialogue and an explanation
component. In addition, expert systems provide interfaces for communication with
external programs including databases and spreadsheets.
Knowledge-Acquisition Interface
The knowledge-acquisition interface controls how the expert and knowledge engineer
interact with the program to incorporate knowledge into the knowledge base. It
includes features to assist experts in expressing their knowledge in a form suitable for
reasoning by the computer
Debugging faulty knowlege bases is facilitated by traces (lists of rules in the order
they were fired), probes (commands to find and edit specific rules, facts, and so on),
and bookkeeping functions and indexes (which keep track of various features of the
knowledge base such as variables and rules). Some rule-based expert system shells
for personal computers monitor data entry, checking the syntactic validity of rules.
Expert systems are typically validated by testing their preditions for several cases
against those of human experts. Case facilities--permitting a file of such cases to be
stored and automatically evaluated after the program is revised--can greatly speed
the vaidation process. Many features that are useful for the user interface, such as
on-screen help and explanations, are also of benefit to the developer of expert
systems and are also part of knowledge-acquisition interfaces
genetic algorithms
Artificial neural networks use nodes and weighted connections between them to analyze the
patterns found in the patient data to derive the associations between the symptoms and a
diagnosis. This eliminates the need for writing rules and for expert input. However since the
system cannot explain the reason it uses the data the way it does, most clinicians dont use
them for reliability and accountability reasons.
Genetic Algorithms are based on simplified evolutionary processes using directed selection to
achieve optimal CDSS results. The selection algorithms evaluate components of random sets
of solutions to a problem. The solutions that come out on top are then recombined and
mutated and run through the process again. This happens over and over till the proper
solution is discovered. They are the same as neural networks in that they derive their
knowledge from patient data.
Non-knowledge-based networks often focus on a narrow list of symptoms like ones for a single
disease as opposed to the knowledge based approach which cover many different diseases to
diagnosis.
1.
http://www.google.lk/imgres?
q=expert+system+architecture&um=1&hl=en&biw=1366&bih=643&tbm=isc
h&tbnid=rwG2wmfWQ6Y8sM:&imgrefurl=http://www.generation5.org/conte
nt/2005/MobES.asp&docid=DAj1xDNyVFyf4M&imgurl=http://www.generat
ion5.org/content/2005/images/mobes_image002.gif&w=374&h=216&ei=UJI3
T_-aFYHRrQfPuYDWBQ&zoom=1
The basic architecture of an expert system is the inference engine and the
knowledge base containing the domain knowledge usually stored in the form of
rules.' Another component, called the user interface, which provides a means of
communicating with an expert system is also part of the basic architecture.
2.
http://www.emeraldinsight.com/journals.htm?articleid=850140&show=html&
3.
search for hybrid expert system architecture. Real time forward chaining
architecture and backward chaining architectures
http://www.generation5.org/content/2005/Expert_System.asp
4.
http://onlinemca.com/mca_course/kurukshetra_university/semester5/artificiali
ntelligence/architecture_of_expert_system.php
5.
http://www.muxtronics.com/an-expert-system-for-power-plants/
6.
http://www.grin.com/en/doc/247144/dynamic-interaction-a-measurementdevelopment-and-empirical-evaluation
7.
http://www.conveylive.com/a/Expert_Systems
8.
http://pages.cpsc.ucalgary.ca/~gaines/reports/KBS/HFES/
9.
http://train-srv.manipalu.com/wpress/?p=81124
10.
http://www.jmir.org/article/viewFile/906/1/2707
http://www.jmir.org/2004/1/e4/
11.
http://www.google.lk/imgres?
q=inference+engine+architecture&um=1&hl=en&sa=N&biw=1366&bih=643
&tbm=isch&tbnid=eIkN2UReWO1o4M:&imgrefurl=http://www.ibm.com/de
veloperworks/cloud/library/cl-devcloudmodule/index.html%3Fca%3Ddrs&docid=tNoE4KGA5YH1OM&imgurl=http://www.ibm.com/developerworks
/cloud/library/cldevcloudmodule/figure3.gif&w=375&h=174&ei=zZE3T7zYCsXMrQei5JXW
BQ&zoom=1
12.
http://myweb.nutn.edu.tw/~leecs/htm/eng/eng_research_projects.html
13.
http://www.cs.purdue.edu/homes/acc/pythiaPaper.html
14.
http://www.google.lk/imgres?
q=inference+engine+architecture&um=1&hl=en&sa=N&biw=1366&bih=643
&tbm=isch&tbnid=HMKBNbDaWU51YM:&imgrefurl=http://www.cs.waikat
o.ac.nz/oldcontent/cbeardon/papers/9509.html&docid=d9yOTyriqI96_M&img
url=http://www.cs.waikato.ac.nz/oldcontent/cbeardon/papers/paper95091.gif&
w=414&h=252&ei=C5A3T5vvF4r3rQec_fnVBQ&zoom=1
http://www.cs.waikato.ac.nz/oldcontent/cbeardon/papers/9509.html
The rules are of the standard "if ... then ..." format. In an ideal version of the
system users would be able to express their rules in natural language:
The domain expert sets up a particular world by modelling the different types
of object, specifying attributes they should have and their default values, and
writing the main behavioural rules they follow. The domain expert may also
specify some lower-level domain-specific predicates and operators.
15.
http://www.ucm.es/info/VerbaLogica/bi_afca1.htm
16.
http://www.ucgis.org/summer2002/choi/choi.htm
17.
http://geniferology.blogspot.com/2011/06/distributive-architecture-forinference.html
18.
http://www.eecs.berkeley.edu/~alspaugh/dmp/rule_engines/index.html
When a rule engine is run under the forward-chaining method, it goes through three
main stages:
1. Match the rules with the facts by testing the conditional part of every rule with
all subsets of facts. As a rule can match with more than one set of facts, pairs
of rules and fact subsets are denoted instantiations. In Drools, they are referred
to as Activations. The set of instantiations is sometimes called the conflict set.
2. Select and order the instantiations or Activations for execution. In Drools, the
Activations selected are placed on an Agenda for execution.
3. Execute the rules in the order specified. Rule execution may trigger other
programs, or may also update the facts, requiring rules to be re-matched.
19.
http://www.codeproject.com/Articles/153914/Machine-Reasoning-in-CADApplictions
20.
http://www.google.lk/imgres?
q=inference+engine+architecture&um=1&hl=en&sa=N&biw=1366&bih=643
&tbm=isch&tbnid=gMEFGpGfTU1YCM:&imgrefurl=http://ewh.ieee.org/soc
/es/Nov1998/03/BEGIN.HTM&docid=T4gTJgmXFJ5ApM&imgurl=http://ew
h.ieee.org/soc/es/Nov1998/03/IMAGE32.GIF&w=452&h=403&ei=C5A3T5v
vF4r3rQec_fnVBQ&zoom=1
21.
http://ewh.ieee.org/soc/es/Nov1998/03/BEGIN.HTM
22.
http://www.w3.org/TandS/QL/QL98/pp/queryservice.html
23.
http://train-srv.manipalu.com/wpress/?p=81124
24.
http://en.wikipedia.org/wiki/Inference_engine
25.
http://vikon.myweb.hinet.net/thesisa.htm
26.
http://amine-platform.sourceforge.net/intro.htm
27.
http://ise.canberra.edu.au/html/DDavies/pages/twm-intro.html
28.
http://www.grin.com/en/doc/247144/dynamic-interaction-a-measurementdevelopment-and-empirical-evaluation
29.
http://www.eee.metu.edu.tr/~vision/books/alife/ch3.html
30.
http://www.agentwaresystems.com/publications/agents.html
31.
http://onlinemca.com/mca_course/kurukshetra_university/semester5/artificiali
ntelligence/architecture_of_expert_system.php
32.
http://parlab.eecs.berkeley.edu/wiki/patterns/task_parallelism
33.
http://www.amzi.com/ExpertSystemsInProlog/02usingprolog.htm