Presentation is loading. Please wait.

Presentation is loading. Please wait.

Week 6 Expert System. Case Scenario During ABC Enterprise management meeting to discuss whether the company should consider a merger with other business.

Similar presentations


Presentation on theme: "Week 6 Expert System. Case Scenario During ABC Enterprise management meeting to discuss whether the company should consider a merger with other business."— Presentation transcript:

1 Week 6 Expert System

2 Case Scenario During ABC Enterprise management meeting to discuss whether the company should consider a merger with other business partners, one important key person of the company, Mr. Amir, who is in charge of the company’s investment portfolios was absent due to fever. The CEO of the company, Mr. Ridzuan wishes to make his expertise in investment portfolio to be made available whenever it is needed, especially during crucial time. Thus, Mr. Ridzuan was considering whether a system can be built to provide direct expertise in the same way that Mr. Amir provides investment portfolio consultation, such as type of investment, their rules, calculations, and so on.

3 3 Expert Systems Attempt to imitate expert reasoning processes and knowledge in solving specific problems. Most popular applied AI technology Enhance Productivity Increase (value) Workforces Narrow problem-solving areas or tasks

4 4 Expert Systems Provide direct application of expertise Expert systems do not replace experts, but they Make their knowledge and experience more widely available Permit non-experts to work better

5 5 Expertise The extensive, task-specific knowledge acquired from training, reading and experience Theories about the problem area Hard-and-fast rules and procedures Rules (heuristics) Global strategies Facts Enables experts to be better and faster than non-experts.

6 6 Human Expert Behaviors Recognize and formulate the problem Solve problems quickly and properly Explain the solution Learn from experience Restructure knowledge Break rules Determine relevance Degrade gracefully

7 7 Transferring Expertise Objective of an expert system To transfer expertise from an expert to a computer system and Then on to other humans (non-experts) Activities Knowledge acquisition Knowledge representation Knowledge inferencing Knowledge transfer to the user Knowledge is stored in a knowledge base

8 8 Two Knowledge Types Facts Procedures (usually rules) Rules IF-THEN-ELSE Explanation Capability

9 Rules (Example) IF interest_rate > 10 AND loan >= 10,000 THEN review_loan = True. If premise is true, the rule is said to be triggered. A rule fires implies that the action specified by the conclusion clauses is taken. premise conclusion

10 10 Three Major ES Components Knowledge Base Inference Engine User Interface

11 11 Three Major ES Components User Interface Knowledge Base Inference Engine

12 12 Knowledge Base The knowledge base contains the knowledge necessary for understanding, formulating, and solving problems Two Basic Knowledge Base Elements Facts Special heuristics, or rules that direct the use of knowledge Knowledge is the primary raw material of ES

13 13 Inference Engine The brain of the ES The control structure (rule interpreter) Provides methodology for reasoning (inference techniques)

14 14 User Interface Language processor for friendly, problem-oriented communication NLP (natural language processing), or menus and graphics

15 15 Explanation Subsystem (Justifier) Other ES component. Traces and explains the ES behavior by interactively answering questions: -Why? -How? -What? -(Where? When? Who?)

16 16 The Knowledge Engineer Helps the expert(s) structure the problem area by interpreting and integrating human answers to questions, drawing analogies, posing counterexamples, and bringing to light conceptual difficulties Usually also the System Builder

17 Inference Techniques (1) Deductive Reasoning Combines facts (axioms) with general knowledge in the form of implications to conclude new facts. Example: Axiom: I am sleeping in class Implication: Sleeping in class => Rude shock in exams Conclusion: I will get a rude shock in the exam. Modus Ponens: IF A is true, and if A => B, then B is true.

18 Inference: Forward Chaining Data driven reasoning. Attempts to conclude a hypothesis (goal) from available information. Reasoning starts from available data and continues from that data, and when it was sufficient, conclusion will be drawn. Useful to find a hypothesis (goal) from a limited information (planning, control, interpreter etc)

19 Forward Chaining: Example R1: IF A and C THEN EGiven facts: R2: IF D and C THEN F A is true R3: IF B and E THEN F B is true R4: IF B THEN CWhat can be concluded? R5: IF F THEN G Cycle through rules, looking for rules whose premise matches the working memory. Working memory A, B R4 fires: assert new fact CA, B, C R1 fires: assert new fact EA, B, C, E R3 fires: assert new fact FA, B, C, E, F R5 fires: assert new fact GA, B, C, E, F, G

20 Inference Techniques (2) Inductive Reasoning Generalizing from specific facts: case 1: Game on 21st Sept. (Friday), It rained, We lost. case 2: Game on 5th Nov. (Friday), It rained, We lost. …..  Induce general rule: IF game is on a Friday AND it rains Then we lose.

21 Inference: Backward chaining Goal driven reasoning. Attempts to prove a hypothesis (goal) by gathering supporting information. Reasoning starts from potential goal and from there, try to find any evidence (facts) to support/reject the goal. Useful when goal was known earlier, just need to find information to support the goal (diagnostic, debugging etc)

22 Backward chaining: Example Rules R1: IF B and C THEN G R2: IF A and G THEN I R3: IF D and G THEN J R4: IF E or F THEN C R5: IF D and C THEN K Goal: I What data to support? Goal I: need to trigger R2 Need both A and G Subgoal A: need user input (ask user) Subgoal G: Need to trigger R1 Need both B and C Subgoal B: need user input (ask user) Subgoal C: Need to trigger R4 Need E or F Subgoal E: need user input (ask user)

23 23 Problem Areas Addressed by Expert Systems Prediction systems Diagnostic systems Design systems Planning systems Monitoring systems Debugging systems Repair systems Control systems

24 24 Expert Systems Benefits Increased output and productivity Decreased decision making time Increased process(es) and product quality Capture scarce expertise Accessibility to knowledge and help desks

25 25 Problems and Limitations of Expert Systems Knowledge is not always readily available Expertise can be hard to extract from humans Each expert’s approach may be different, yet correct Experts’ vocabulary often limited and highly technical

26 26 Expert Systems and the Web/Internet/Intranets Provide knowledge and advice Help desks Spread of multimedia-based expert systems (Intelimedia systems) Support ES and other AI technologies provided to the Internet/Intranet

27 27 ES Shell Includes All Generic ES Components But No Knowledge EMYCIN from MYCIN (E=Empty)

28 28 Expert Systems Shells Software Development Packages Exsys http://www.exsys.com K-Vision http://www.ginesys.com/k- vision/index.htm eXpertise2Go http://www.expertise2go.com/webesie/

29 29 An Expert System at Work Exsys Demo http://www.exsys.com/demomain.html

30 Intelligence Density Dimension Explainability Flexibility Scalability Independence from experts


Download ppt "Week 6 Expert System. Case Scenario During ABC Enterprise management meeting to discuss whether the company should consider a merger with other business."

Similar presentations


Ads by Google