1 / 15

Verification and Validation

Verification and Validation. To ensure quality in expert system verificaion and validation are important steps in the development lifecycle. Based on Chap. 16: The Engineering of Knowledge-based Systems: Theory and Practice, A. J. Gonzalez and D. D. Dankel. Errors may stem from:

winona
Download Presentation

Verification and Validation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Verification and Validation To ensure quality in expert system verificaion and validation are important steps in the development lifecycle. Based on Chap. 16: The Engineering of Knowledge-based Systems: Theory and Practice, A. J. Gonzalez and D. D. Dankel

  2. Errors may stem from: • Not Complying with the system specs. • Semantic and syntactic errors • Incorrect representation of the knowledge domain

  3. Verification and validation in expert systems is different from that of conventional expert system • ES are not purely objective • Uncertainty is accepted and may even be encouraged • ES output cannot be easily verified through experiments • Expert (or group of experts) decide on the accuracy of the system

  4. Verification The adherence to the system specification and correct implementation process.

  5. Compliance with specs • Knowledge representation • Reasoning technique • Modularity • Interfaces • Explanation facility • Performance • Maintainability • Security

  6. Redundant rules Identical rules or rules that have the same meaning: If a is true and b is true then the temp is -40 0 C If a is true and b is true then the temp is -40 0 F

  7. Conflicting rules Identical premises with conflicting conclusions: If a is true and b is true then x If a is true and b is true then ~x

  8. Subsumed rules • All the premises of one rule is a subset of another rule, and both have identical conclusion: If a is true and b is true then x If a is true and b is true and c is true then x

  9. Circular rules Conclusion of rule1 leads to rule2 firing, whose conclusion leads to rul1 firing: If a is true and b is true then x and y If x is true and y is true then a and b

  10. Unnecessary IF conditions Two rules have identical conclusion, but one of the premises is conflicting: If a is true and b is true and ~c is true then x If a is true and b is true and c is true then x

  11. Dead-end rules A rule whose action is not one of the conclusions of the system or whose conclusion is not used in the premise of any other rule.

  12. Missing rules Dead end rules could be caused by the removal of rules or the failure of the knowledge engineer to include a rule.

  13. Unreachable rules The premise of the rule will never ever be true.

  14. Validation Checks to see if the system is correct, i.e. the output is consistent with input.

  15. Validation issues • What is being validated? • Method • Criteria • When should validation occur?

More Related