Expert systems
An expert system stores a specialist's know-how as if-then rules and uses a separate inference engine to apply those rules to a new case and explain its advice.
An expert system is a program built for problems that normally take a trained specialist, and it tackles them by applying stored knowledge through a reasoning procedure. It has two main parts, a knowledge base and an inference engine. The knowledge base is where the program keeps what it knows about its subject, such as medicine, mostly written as rules of the form if A and B, then C. The inference engine can chain rules together, so one rule’s conclusion feeds the next. Chaining from known data forward is called forward chaining. MYCIN mostly chained backward instead. It starts from a goal and works back through the rules to find the data that would prove it.
The person who helps an expert write down their knowledge for the program is called a knowledge engineer. Step one was talking with the expert; step two was drafting rules from those talks. Next, the draft rules were tried on sample cases; when the program got one wrong, the engineer traced the rules behind the mistake and asked the expert what to change.
Three systems made the idea famous. DENDRAL, begun at Stanford in 1965, became the early model for the whole approach. DENDRAL was built by Joshua Lederberg, Edward Feigenbaum and Carl Djerassi, and identified the structure of unknown organic compounds. MYCIN advised doctors on antibiotics and computed certainty factors for its conclusions. What it knew about infections fitted into 450 rules plus roughly 1,000 other facts. MYCIN was never tried on the hospital wards. R1, also called XCON, was used at DEC from January 1980. Given a customer’s order, R1 worked out what had to be added or swapped to make it complete and consistent. By November 1983 R1 had about 3,300 rules and 5,500 component descriptions. By 1984 its builders no longer expected it ever to be finished. According to DEC, XCON together with a sister system was worth over 40 million dollars in savings each year.
Expert systems also drew a rush of private money into AI. That boom did not last, since few buyers managed to train their own staff to build and run such systems well. In the mid-1980s enthusiasm cooled and money for AI research got scarce, a slump now known as the AI winter. A Stanford history of AI adds that the field leaned too hard on true-or-false logic and neglected uncertainty. None of these expert systems took over from the chemist or the physician; the most they did was offer a second opinion. The idea lives on in rule engines such as Drools, which can chain rules both forward and backward.
Scarce expertise lives in people's heads, where ordinary programs cannot reach it.
Follow one consultation from the expert's rules to the explained advice.
- 1 · interviewA knowledge engineer works with the expert to turn what they know into rules for the program.
- 2 · storeThe rules go into a knowledge base, kept apart from the code that uses them.
- 3 · chainFor a new case, the inference engine links rules together, so one rule's conclusion becomes another rule's premise, until it reaches a conclusion.
- 4 · explainAsked why it wants a fact, the program shows the rule that needed it, and asked how, it shows how a fact was established.
The knowledge is data, not code: change the rules and the same engine gives different advice.
| Who | What they ask | What it works with |
|---|---|---|
| Chemists | “Which molecular structure fits this mass spectrum?” | Rules about how molecules break apart, as in DENDRAL |
| Hospital doctors | “Which antibiotic should this patient with an infection get?” | Rules linking lab results and symptoms to organisms and drugs, as in MYCIN |
| Computer maker's order desk | “What parts are missing from this customer's order?” | Rules about which components fit together, as in R1, also called XCON |
| Business software team | “Does this application meet our approval policy?” | Business rules held in a rule engine such as Drools |
- It lets a program use specialised knowledge rather than only general problem-solving methods.
- The rules sit apart from the engine, so knowledge can be added or changed without rewriting the program.
- It has a part that explains its reasoning to the user.
- Certainty factors let rules carry rough strengths of evidence rather than plain true or false.
- Building the knowledge base is slow, because getting knowledge out of experts is a bottleneck.
- Each system covers only a narrow task. Ten-plus years of work still left DENDRAL unable to handle every kind of compound.
- The rules need constant upkeep. At DEC, looking after the rules and the software around them took 59 technical people by 1989.
- MYCIN's own builders said its answers could not be proved right, since rules of thumb come with no guarantee.
Sources used
This explainer is written in original language. The links below support its factual claims.
- paperRule-Based Expert Systems: The MYCIN Experiments, chapter 1: The Context of the MYCIN Experiments, Buchanan and Shortliffe (eds.), Addison-Wesley 1984 · read 27 Sept 2026
- paperRule-Based Expert Systems: The MYCIN Experiments, chapter 7: Knowledge Engineering, Buchanan and Shortliffe (eds.), Addison-Wesley 1984 · read 27 Sept 2026
- paperRule-Based Expert Systems: The MYCIN Experiments, chapter 36: Major Lessons from This Work, Buchanan and Shortliffe (eds.), Addison-Wesley 1984 · read 27 Sept 2026
- officialComputers, Artificial Intelligence, and Expert Systems in Biomedical Research (Joshua Lederberg, Profiles in Science), US National Library of Medicine · read 27 Sept 2026
- paperR1 Revisited: Four Years in the Trenches, Bachant and McDermott, AI Magazine (AAAI) 1984 · read 27 Sept 2026
- paperExpert Systems in the 1980s, Feigenbaum, 1980 (Stanford Libraries, Edward A. Feigenbaum Papers) · read 27 Sept 2026
- officialAppendix I: A Short History of AI (One Hundred Year Study on Artificial Intelligence, 2016 report), Stanford University AI100 · read 27 Sept 2026
- articleHow the AI Boom Went Bust, Communications of the ACM (Haigh, 2024) · read 27 Sept 2026
- docsDrools documentation, Introduction, Drools project (Apache KIE) · read 27 Sept 2026