Quality Assurance Of An Expert System.

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

Modelling with expert systems. Expert systems Modelling with expert systems Coaching modelling with expert systems Advantages and limitations of modelling.
ARCHITECTURES FOR ARTIFICIAL INTELLIGENCE SYSTEMS
Chapter 11 user support. Issues –different types of support at different times –implementation and presentation both important –all need careful design.
Software Development Languages and Environments. Programming languages High level languages are problem orientated contain many English words are easier.
CHAPTER 13 Inference Techniques. Reasoning in Artificial Intelligence n Knowledge must be processed (reasoned with) n Computer program accesses knowledge.
Supporting Business Decisions Expert Systems. Expert system definition Possible working definition of an expert system: –“A computer system with a knowledge.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Inferences The Reasoning Power of Expert Systems.
Rule Based Systems Michael J. Watts
Chapter 12: Expert Systems Design Examples
Expert System Human expert level performance Limited application area Large component of task specific knowledge Knowledge based system Task specific knowledge.
Chapter 11 Artificial Intelligence and Expert Systems.
Help and Documentation zUser support issues ydifferent types of support at different times yimplementation and presentation both important yall need careful.
Artificial Intelligence
Chapter 9 Describing Process Specifications and Structured Decisions
Designing Help… Mark Johnson Providing Support Issues –different types of support at different times –implementation and presentation both important.
Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall Chapter Chapter 1: Introduction to Decision Support Systems Decision Support.
Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall Chapter Chapter 7: Expert Systems and Artificial Intelligence Decision Support.
EXPERT SYSTEMS Part I.
Chapter 12: Intelligent Systems in Business
Lead Black Slide. © 2001 Business & Information Systems 2/e2 Chapter 11 Management Decision Making.
Building Knowledge-Driven DSS and Mining Data
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
Artificial Intelligence CSC 361
Software Life Cycle Model
Sepandar Sepehr McMaster University November 2008
Expert Systems.
Expert Systems Infsy 540 Dr. Ocker. Expert Systems n computer systems which try to mimic human expertise n produce a decision that does not require judgment.
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
Introduction to Systems Analysis and Design Trisha Cummings.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Katanosh Morovat.   This concept is a formal approach for identifying the rules that encapsulate the structure, constraint, and control of the operation.
Artificial Intelligence Lecture No. 15 Dr. Asad Ali Safi ​ Assistant Professor, Department of Computer Science, COMSATS Institute of Information Technology.
Knowledge Acquisition. Concepts of Knowledge Engineering Knowledge engineering The engineering discipline in which knowledge is integrated into computer.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Software System Engineering: A tutorial
Chapter 6 Supplement Knowledge Engineering and Acquisition Chapter 6 Supplement.
11 C H A P T E R Artificial Intelligence and Expert Systems.
School of Computer Science and Technology, Tianjin University
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
 Architecture and Description Of Module Architecture and Description Of Module  KNOWLEDGE BASE KNOWLEDGE BASE  PRODUCTION RULES PRODUCTION RULES 
Knowledge Representation
Problem Solving Techniques. Compiler n Is a computer program whose purpose is to take a description of a desired program coded in a programming language.
SYSTEM TESTING AND DEPLOYMENT CHAPTER 8. Chapter 8: System Testing and Deployment 2 KNOWLEDGE CAPTURE (Creation) KNOWLEDGE TRANSFER KNOWLEDGE SHARING.
Chap#11 What is User Support?
The Software Development Process
Chapter 4 Decision Support System & Artificial Intelligence.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
Software Requirements Specification (SRS)
Finite State Machines (FSM) OR Finite State Automation (FSA) - are models of the behaviors of a system or a complex object, with a limited number of defined.
Of An Expert System.  Introduction  What is AI?  Intelligent in Human & Machine? What is Expert System? How are Expert System used? Elements of ES.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
Artificial Intelligence
ITEC 1010 Information and Organizations Chapter V Expert Systems.
Knowledge Engineering. Sources of Knowledge - Books - Journals - Manuals - Reports - Films - Databases - Pictures - Audio and Video Tapes - Flow Diagram.
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
Introduction to Computer Programming Concepts M. Uyguroğlu R. Uyguroğlu.
 System Requirement Specification and System Planning.
Knowledge Representation Techniques
Software Testing.
Definition CASE tools are software systems that are intended to provide automated support for routine activities in the software process such as editing.
Advanced AI Session 2 Rule Based Expert System
CHAPTER 1 Introduction BIC 3337 EXPERT SYSTEM.
Architecture Components
Intro to Expert Systems Paula Matuszek CSC 8750, Fall, 2004
Test Case Test case Describes an input Description and an expected output Description. Test case ID Section 1: Before execution Section 2: After execution.
Chapter 11 user support.
Chapter 11 Describing Process Specifications and Structured Decisions
Presentation transcript:

Quality Assurance Of An Expert System

Index Introduction Comparison of expert systems with What is AI? Intelligent in Human & Machine? What is Expert System? How are Expert System used? Elements of ES Who are people involved in an Expert System project ? Comparison of expert systems with (( conventional systems and human experts )) Knowledge Definition of Knowledge Knowledge acquisition Knowledge representation

What is AI (Artificial intelligent )? "Artificial intelligence is the study of how to make computers do things at which, at moment, people are better“ Elaine Rich (1983) Artificial intelligence is the branch of computer science that focuses on the development of computer systems. Artificial is also called machine intelligence

Natural vs. Artificial Intelligence Fundamentals of Information Systems, Second Edition

Branches of Artificial Intelligence Computer Science Fundamentals of Information Systems, Second Edition

What is an Expert System ? Expert systems are artificial intelligence (AI) tools that capture the expertise of knowledge workers “Experts” and provide advice to (usually) non-experts in a given domain. Expert systems are implemented with artificial intelligence technology, often called expert system shells. Expert System Shell : is an expert system but without knowledge “with empty knowledge” Expert system shells capture and simulate the reasoning of the experts. Expert systems require data and information like any other information system, but they are unique in their requirement of rules that simulate the reasoning of the experts who use the data and information.

The elements of ES

How are Expert Systems used? Many expert systems are built using a generic ‘shell’. An expert system shell consists of the programming components of an expert system but without a KB. Using a shell, a knowledge engineer can quickly enter a new KB and, without the need for any programming, create a complete working expert system. The expert system can be used many times with the same knowledge using that knowledge to solve different problems (just like a doctor uses their knowledge many times to diagnose and cure lots of patients).

The elements of ES The elements of an expert system are as follows: Expert—human expert to provide the knowledge for the expert system. Database—some knowledge acquisition methods use data in databases to automatically generate new rules, e.g. weather data can be used to generate rules that will enable prediction of tomorrow’s weather. Acquisition module— obtains appropriate knowledge from the human expert and the database ready for input to the KB of the expert system. Knowledge base— retains the knowledge and rules used by the expert system in making decisions. Inference engine— system that reasons to provide answers to problems placed into the expert system. The inference engine uses knowledge from the KB to arrive at a decision. Explanatory interface— to provide the user with an explanation on how the expert system reached its conclusion. User—the human being using the expert system!

Who are people involved in an Expert system project ?

Comparison of expert systems with conventional systems

Comparison of expert systems with conventional systems

Knowledge

What is Knowledge ? Knowledge is a theoretical or practical understanding of a subject or a domain. Who owns knowledge are called experts. Domain expert is anyone has deep knowledge and strong practical experience in a particular domain. An expert is a skilful person who can do things other people cannot.

Knowledge Engineering ‘Knowledge engineering is the process of developing knowledge based systems in any field, whether it be in the public or private sector, in commerce or in industry’ (Debenham, 1988). Knowledge engineering normally involves five distinct steps (listed below) in transferring human knowledge into some form of knowledge based system(KBS). 1. Knowledge acquisition 2. Knowledge validation 3. Knowledge representation 4. Inferencing 5. Explanation “Interface” An Introduction to knowledge engineering

Knowledge acquisition Fundamentals of Information Systems, Second Edition

What is Knowledge Acquisition ? Knowledge acquisition  is the process of acquiring the knowledge from human experts or other sources (e.g. books, manuals) to solve the problem. the knowledge acquisition process primarily involves a discussion between the knowledge engineer and the human expert. A knowledge engineer can also use interviews as method of obtaining knowledge from human experts however they must also consider other sources of knowledge. (( records of past case studies , standards documentation ,knowledge from other humans who are less knowledgeable but more available then experts. )) Adaptive fuzzy petri nets for dynamic knowledge representation and inference X. Li, F. Lara-Rosano* Centre for Instrumentation Research, National University of Mexico (UNAM), Apartado Postal 70-418, Mexico City, D.F. 04510, Mexico

Knowledge acquisition techniques Interview (1) An Interview is the easiest technique for Knowledge Acquisition. To conduct a successful interview the knowledge engineer will need to: plan use appropriate stage management techniques consider and use appropriate social skills maintain appropriate self-control during the interview.

Knowledge acquisition techniques Interview (2) The interview normally consists of three parts :

Knowledge acquisition techniques Interview (3) Questions useful to begin the interview process include: Can you give me an overview of the subject? Can you describe the last case you dealt with? What facts or hypotheses do you try to establish when thinking about a problem? What kinds of things do you like to know about when you begin to think about a problem? Leading on to find a little more detail; tell me more about how this is achieved? What do you do next? How does that relate to . . . ? How, why, when, do you do that? Can you describe what you mean by that? Closing an interview by reviewing the information obtained, and perhaps by alerting the expert to the need for further interviews, is also important.

Other Knowledge Acquisition Techniques By knowledge engineer Tutorial interviews “presentation” Twenty question interviews “Yes or No” Teach back interviews “past interviews” Observation studies Observation of an expert doing his task The cooperation with the expert can be difficult The time consuming for the knowledge engineer No knowledge engineer necessary Machine induction “ automated Knowledge Acquisition “ Rules are automatically induced from given examples Database is instable & Rules are complex Adaptive fuzzy petri nets for dynamic knowledge representation and inference X. Li, F. Lara-Rosano* Centre for Instrumentation Research, National University of Mexico (UNAM), Apartado Postal 70-418, Mexico City, D.F. 04510, Mexico

Knowledge acquisition techniques Interview (4) Dealing with Multiple Experts

Knowledge representation

Knowledge Representation Knowledge representation (KR) is an area of artificial intelligence whose fundamental goal is to represent knowledge in a manner that facilitates inferencing (i.e. drawing conclusions) from knowledge. Different knowledge representation schemes: Rules Semantic Networks Frames http://en.wikipedia.org/wiki/Knowledge_representation_and_reasoning An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

Production Rules Rules is the most commonly used type of knowledge representation in AI. Format: IF .. THEN Any rule consists of two parts: IF part, called the premise (or condition) and THEN part, called the conclusion (or action). Basic syntax of a rule is: IF <condition> THEN <action> An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

THEN many factories will close for the whole of Christmas week. Production Rules Other clauses such as OR, And and ELSE can also be used within this construct to show alternative conditions or different courses of action. For example, a simple rule could be: IF raining THEN you-should-carry-an-umbrella IF Christmas day falls on a Monday, OR Christmas day falls on a Tuesday THEN many factories will close for the whole of Christmas week. An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

Production Rules Advantages: Easy to understand Explanations and inference are easy to get. Rules are independent of all others. Modification and maintenance are relatively easy. Uncertainty is easily combined with rules.

Production Rules Disadvantages: Hard to follow hierarchies Inefficient for large systems. Not all knowledge can be expressed as rules. Decision Support Systems and Intelligent Systems, 7th edition, Turban, Aronson, and Liang

Semantic Networks One of the oldest and easiest to understand knowledge representation schemes. It is a graphical representation of knowledge that shows objects and their relationships. They are often used as a communication tool between the knowledge engineer and the expert during the knowledge acquisition phase of a project. In these networks, objects are shown by nodes, and links between the nodes describe the hierarchical relationships between objects. An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

Semantic Networks For example: Mary is an instance of trainer, and trainer is a type of consultant. A trainer trains a programmer and a programmer is an employee. Joe is an instance of programmer. From this we can clearly see the relationship that may exist between Mary and Joe. An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

Semantic Networks An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

Semantic Networks Inheritance is concerned with how one object inherits the properties of another object. An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

Semantic Networks An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

Semantic Networks Advantages: Flexible to add new nodes and links The network is graphical and easy to understand. They tend to be a powerful and adaptable method of representing knowledge because many different types of object can be included in the network. Can be used as a common communication tool between the knowledge engineer and the human expert during the knowledge acquisition phase of designing an ES. An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

Semantic Networks Disadvantages: Meaning attached to nodes may be ambiguous. Difficult to program. Decision Support Systems and Intelligent Systems, 7th edition, Turban, Aronson, and Liang

Frames Frames are a simplified version of a semantic network where only ‘is a’ relationships apply. Frames provide a method of storing knowledge, collecting specific information about one object in an ES. In essence they allow both data and procedures to be included within one structure. An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

Frames Each frame has its own name and a set of attributes, or slots, associated with it.

Frames An example frame for a coffee mug object can be drawn as follows: An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

Frames Three different types of slots are used: Named slots having a standard filler value of certain data items. For example, the slot for number of wheels in a car frame will have a default value of four. This can be overwritten where the specific type of car being described (such as a three-wheel car) does not meet this default value. Range values can also be specified, e.g. the size must be small, medium or large. An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

Frames 2. Slots showing relationships using the term IS A. For example, a car is a motor vehicle. The IS A motor vehicle slot will therefore link the frame for car with a frame describing the basic features of a motor vehicle. 3. Slots contain procedural code. For example, the number of miles that a car can travel, i.e., its range, is determined by the current petrol stored in its tank and by the engine size. The slot for range can therefore store procedural code to calculate the range (if needed) based on the slots for current petrol and engine size. An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

Frames An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

Frames Inheritance: One of the main advantages of using frames is the principle of inheritance. This means that frames can inherit the attributes of other frames, in a hierarchical structure. For example, a frame for a cup can provide some basic attributes in a number of slots about that object. These attributes can be given to other objects that share those attributes. An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

Frames An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

Frames Advantages: be represented in the form of a table, making the information easy to read. be structured hierarchically and thus allow easy classification of knowledge. reduce complexity by allowing a hierarchy of frames to be built up. clearly document information using common formats and syntax. combine procedural and declarative knowledge using one knowledge representation scheme. constrain allowed values, or allow values to be entered within a specific range. An Introduction to Knowledge Engineering, Simon Kendal, Malcolm Creen

Frames Disadvantages: Difficult to program. Difficult for inference. Lack of inexpensive software Decision Support Systems and Intelligent Systems, 7th edition, Turban, Aronson, and Liang

Inference Engine

Inference Engine Use information and relations to derive new facts to solve problems or predict possible outcomes. Main reasoning component Find the right facts, apply the right relations, etc. Ex: Facts: male(Ali), female(Mona) Relations: father(X, Y) => male(X) The engine can conclude that Mona cannot be a father. ArtificialArtificial A Guide to Intelligent Systems, Second Edition. By MICHAEL NEGNEVITSKY. 47

Inference Engine Inference engine compares each rule stored in the knowledge base with facts contained in the database. When the IF (condition) part of the rule matches a fact: The rule is fired and its THEN (action) part is executed. Fired rule may change the set of facts by adding a new fact. Artificial Artificial A Guide to Intelligent Systems, Second Edition. By MICHAEL NEGNEVITSKY.

Inference Engine General problem-solving knowledge or methods. Interpreter analyzes and processes the rules. Scheduler determines which rule to look at next. The search portion of a rule-based system. Artificial Intelligence and Expert Systems for Engineers. By C.S. Krishnamoorthy; S. Ra.

Chaining Inference Techniques In a rule-based expert system: Domain knowledge is represented by a set of IF-THEN production rules. Data is represented by a set of facts about the current situation. Artificial Artificial A Guide to Intelligent Systems, Second Edition. By MICHAEL NEGNEVITSKY.

Matching of the rule IF parts to the facts produces inference chains Artificial Artificial A Guide to Intelligent Systems, Second Edition. By MICHAEL NEGNEVITSKY. The inference engine cycles via a match-fire procedure

Chaining Inference Techniques 1- Forward Chaining Forward chaining is a data-driven inference process. Is a technique for gathering information and then inferring from it whatever can be inferred. You start with facts and try to reach conclusions. The user of the system has to give all the available data before the start of the inference. The inference mechanism tries to establish the facts as they appear in the knowledge base until the goal is established. Artificial Intelligence and Expert Systems for Engineers. By C.S. Krishnamoorthy; S. Ra. 52

Chaining Inference Techniques 1- Forward Chaining Advantage 1-The forward chaining process is suitable only when there are very few initial states and many goal states. 2-If the data are sufficient the goal may be reached. 3-Forward chaining is going to be adopted for reasoning. Artificial Intelligence and Expert Systems for Engineers. By C.S. Krishnamoorthy; S. Ra. 53

Chaining Inference Techniques 1- Forward Chaining Disadvantage 1-If the data are sufficient the goal may be reached; otherwise it may exit stating that the goal is unreachable with the available data. 2-Many initial and goal states can exist. Also the User may not be able to give all the necessary data a priori, as he/she may not be able to visualize the flow of the inference process.   3-Not efficient if our goal is to infer only one particular fact. Many rules may be executed that have nothing to do with the established goal. 4-Many rules may be executed that have nothing to do with the established goal. 5-More expensive since it can generate many conclusions. Chaining Inference Techniques 1- Forward Chaining Artificial Intelligence and Expert Systems for Engineers. By C.S. Krishnamoorthy; S. Ra. 54

Chaining Inference Techniques 2- Backward Chaining You start with conclusions. You want to find out if you can get to the conclusion from your facts. Is a goal-driven process and the most frequently used inference mechanism. It tries to establish goals in the order in which they appear in the knowledge base. The goal variable defined in the rule base for selection of a structural. Artificial Intelligence and Expert Systems for Engineers. By C.S. Krishnamoorthy; S. Ra. 55

Chaining Inference Techniques 2- Backward Chaining Advantage System is ‘floor system’, The inference process will stop once this variable gets a value. It tries to establish goals in the order in which they appear in the knowledge base. The inference process will stop once this variable gets a value. 56

Chaining Inference Techniques 2- Backward Chaining Disadvantage It will continue to follow a given line of reasoning even if it should drop it and switch to a different one. Artificial Intelligence and Expert Systems for Engineers. By C.S. Krishnamoorthy; S. Ra. 57

Comparative Summary of Backward and Forward Chaining Attribute Backward Chaining Forward Chaining Also known as Goal-driven Data-driven Starts from Possible conclusion New data Processing Efficient Somewhat wasteful Aims for Necessary data Any conclusion (s) Approach Conservative/cautious Opportunistic Practical if Number of possible final answers is reasonable or a set of known alternatives is available Combinatorial explosion creates an infinite number of possible right answers Appropriate for Diagnostic, prescription and debugging application Planning, monitoring, control and interpretation application Example of application Selecting a specific type of investment Making changes to corporate pension fund

Chaining Inference Techniques 3- Hybrid inference mechanism It is a combination of the backward and forward chaining process. The sequence in which the data are requested depends on the flow of the inference process. Backward chaining is suitable, if there are few goal states and many initial states. In forward chaining all the data that the user knows have to be given a priori and the system does not prompt for any data. It starts in the forward chaining mode with an empty context by trying to establish the facts as they appear in the rule base and then backward chains to prove or disprove them. Artificial Intelligence and Expert Systems for Engineers. By C.S. Krishnamoorthy; S. Ra. 59

Other Components Explanation Facility Knowledge Acquisition Facility Enables the expert system to explain its reasoning. Helps the user to judge the expert system. Knowledge Acquisition Facility Get and update knowledge. Provide a way to capture and store knowledge. Can be semi-automated. User Interface Help users interact with the system. Improve usability. Explanation in Expert Systems: A Survey By Johanna D. Moore and William R. Swartout

Explanation capabilities Explanation Facility Explanation capabilities A basic component of an expert system that enables the user to query the expert system about how it reached a particular conclusion . They can show the sequence of the rules they applied to reach a solution, but cannot relate accumulated, heuristic knowledge to any deeper understanding of the problem domain. Enable the user to ask the expert system how a particular conclusion is reached and why a specific fact is needed. An expert system must be able to explain its reasoning and justify its advice, analysis or conclusion. Explanation in Expert Systems: A Survey By Johanna D. Moore and William R. Swartout

The explanation facilities of most current systems can be characterized as: Narrow: only a few types of questions can be answered. Inflexible: explanations can be presented in only one way. Insensitive: explanations cannot be tailored to meet the needs of different users or of different situations. Unresponsive: the system cannot answer follow-up questions or offer an alternative explanation ,if a user does not understand a given explanation. inextensible: new explanation strategies cannot be added easily. Explanation in Expert Systems: A Survey By Johanna D. Moore and William R. Swartout

Early Approaches to Explanation in Expert Systems Early attempts to provide programs with an ability to explain: 1-Those that produce explanations from text prepared a priori and associated with structures or procedures in the program, and 2-Those that produce explanations by translating directly from the program code and execution traces. Explanation in Expert Systems: A Survey By Johanna D. Moore and William R. Swartout

1-Explanation From Canned Text or Templates In the first approach, system builders anticipate what questions are likely to be asked and construct the natural language text of the responses to be given. This text is often referred to as canned text and explanations produced by displaying this text are canned explanations. The canned text may contain variables to be filled in with values from a specific execution of the program. Structures that mix canned text with slots to be filled in are called templates. Example: Error messages in programs are a common example of this approach. Explanation in Expert Systems: A Survey By Johanna D. Moore and William R. Swartout

2-Explanation By Translating the Code Researchers developed explanation systems which produce their programs are written in a language to which simple transformations can be applied to produce natural language explanations of the code’s behavior. Explanation in Expert Systems: A Survey By Johanna D. Moore and William R. Swartout

dialogue structure))User interface User interface is the means of communication between a user seeking a solution to the problem and an expert system. The communication should be as meaningful and friendly as possible. External interface allows an expert system to work with external data files and programs written in conventional programming languages such as C, Pascal, FORTRAN and Basic. Developer interface usually includes knowledge base editors, debugging aids and input/output facilities. ArtificialArtificial A Guide to Intelligent Systems, Second Edition. By MICHAEL NEGNEVITSKY.

Quality Assurance in An Expert System

Quality assurance in ES The main assurance provided by the knowledge engineer , project manager or the quality manager was that the system was built in accordance with quality assurance standards. Quality assurance is an essential part of the design of any KBS The Quality control of an expert system appear under the terms Verification , Validation , and Evaluation (VV&E) that are designed to: Verification Verify to show the system is built right. Validation Validate to show the right system was built. Evaluation Evaluate to show the usefulness of the system.

Expert system development process KB

Evaluation in KBS Evaluation of a KBS means checking that the KBS has acceptable performance levels, that the system is useable, efficient and cost-effective. Evaluation is therefore part of the overall quality control procedures in building a KBS and building the ES at all. The evaluation of a KBS involves two more terms, namely validation and verification. Validation Verification Evaluation

The Need for Evaluation Evaluation is required to ensure that knowledge of the real world has been correctly entered into the knowledge base.

Distortion in the knowledge transfer process Evaluation help to find these distortions in knowledge in various ways.

Verification Refers to building the system right. Verification is checking that the system has been built correctly. The objects in KB are logical and consistent with the knowledge obtained via the knowledge acquisition process.

The Verification Verification : is the task of determining that the system is built according to its specifications and its knowledge base is consistent and complete . Consistency of the KB means that there are no redundancies, conflicts or cycles. Completeness means that all facts are used, There are no unreachable conclusions, missing rules (in the rule-based expert systems context),

Verification Verification is likely to involve checks for the following: Syntactic coherence: to check that all rules in the KB are correctly defined with respect to the inference engine. Logical coherence: to detect logical contradictions. Contextual coherence: to check that the KB is consistent with the model of the problem.

The Verification Examples of the type of errors that verification of the KBS is trying to identify are as follows: Subsumed Rules These occur when two rules have the same conclusion but one rule has additional conditions. For example, Rule 1 is subsumed within Rule 2 and could automatically be eliminated from the knowledge base without affecting its reasoning. However, the knowledge acquisition process should really be checked to confirm which of the two rules are correct. Both rules cannot be logically correct; Rule 1 is incorrect if C is not necessary. If it is necessary, Rule 2 is incorrect. Rule 1. IF A AND B AND C THEN X Rule 2. IF A AND B THEN X

Rule 3. IF the patient has pink spots THEN the patient has measles. The Verification 2 ) Unnecessary IF Conditions This situation occurs when the conclusions of two rules are the same and, except for one, the conditions of the rules are the same and this condition is reversed. For example, These two rules could be combined to form one simpler rule. . . . However, once again the source of the two rules should be checked and the appropriate rules amended or deleted. Rule 1. IF the patient has pink spots AND has a fever THEN the patient has measles. Rule 2. IF the patient has pink spots AND does not have a fever THEN the patient has measles. Rule 3. IF the patient has pink spots THEN the patient has measles.

The Validation measures the performance of the KBS Is the process of ensuring that the output of the system is equivalent to those of human experts when given the same inputs. The validation refers to building the “right” system That mean that the expert system performs with an acceptable level of accuracy.

Some of Measures of Validation Accuracy How correct the knowledge is in the KB How well the system reflects the reality Validity The capability of KB for producing correct predictions Breadth How well the domain is covered Depth The degree of detailed the knowledge Sensitivity Impact of changes in the KB on the quality of the outputs Usefulness How the knowledge can solve the problems correctly Realism the KBS provides realistic solutions Adaptability Possibilities for future development and changes

Standards in KBS Development Using validation and verification controls will help to ensure that the finished KBS meets its objectives, and check that the knowledge base is providing correct answers to problems. There are other factors of standards for the general software development process, i.e., including: The organization producing the software needs to provide users with quality software that operates satisfactorily. (user satisfaction) The need to develop software within the constraints of time, money and available staff. The finished product must be at an acceptable level. The product must be easy to maintain,

Standard 9003-3 The International Standards Organization standard 9003-3 is a method of software validation is to use, which relates to software development generally Application of the ISO 9000-3 will therefore help to provide quality KBSs.