We use our experience with the Dipmeter Advisor system for well-log interpretation as a case study to examine the development of commercial expert system. We argue that the tools and ideas of rapid prototyping and successive refinement accelerate the development process. We note that different types of people are required at different stages of expert system development: Those who are primarily knowledgeable in the domain, but who can use the framework to expand the domain knowledge; and those who can actually design and build expert systems. Finally, we discuss the problem of technology transfer and compare our experience with some of the traditional wisdom of expert system development.

We use our experience with the Dipmeter Advisor system for well-log interpretation as a case study to examine the development of commercial expert system. We discuss the nature of these systems as we see them in the coming decade, characteristics of the evolution process, development methods, and skills required in the development team. We argue that the tools and ideas of rapid prototyping and successive refinement accelerate the development process. We note that different types of people are required at different stages of expert system development: Those who are primarily knowledgeable in the domain, but who can use the framework to expand the domain knowledge; and those who can actually design and build expert systems. Finally, we discuss the problem of technology transfer and compare our experience with some of the traditional wisdom of expert system development.

This article describes our initial experience with building applications programs in a hybrid AI tool environment. Traditional AI systems developments have emphasized a single methodology, such as frames, rules or logic programming, as a methodology that is natural, efficient, and uniform. The applications we have developed suggest that natural-ness, efficiency and flexibility are all increased by trading uniformity for the power that is provided by a small set of appropriate programming and representation tools. The tools we use are based on five major AI methodologies: frame-based knowledge representation with inheritance, rule-based reasoning, LISP, interactive graphics, and active values. Object-oriented computing provides a principle for unifying these different methodologies within a single system.

Most work in automatic programming has focused primarily on the roles of deduction and programming knowledge. However, the role played by knowledge of the task domain seems to be at least as important, both for the usability of an automatic programming system and for the feasibility of building one which works on non-trivial problems. This perspective has evolved during the course of a variety of studies over the last several years, including detailed examination of existing software for a particular domain (quantitative interpretation of oil well logs) and the implementation of an experimental automatic programming system for that domain. The importance of domain knowledge has two important implications: a primary goal of automatic programming research should be to characterize the programming process for specific domains; and a crucial issue to be addressed in these characterizations is the interaction of domain and programming knowledge during program synthesis.

Most work in automatic programming has focused primarily on the roles of deduction and programming knowledge. However, the role played by knowledge of the task domain seems to be at least as important, both for the usability of an automatic programming system and for the feasibility of building one which works on non-trivial problems. This perspective has evolved during the course of a variety of studies over the last several years, including detailed examination of existing software for a particular domain (quantitative interpretation of oil well logs) and the implementation of an experimental automatic programming system for that domain. The importance of domain knowledge has two important implications: a primary goal of automatic programming research should be to characterize the programming process for specific domains; and a crucial issue to be addressed in these characterizations is the interaction of domain and programming knowledge during program synthesis.

Artificial intelligence, or AI, is largely an experimental science—at least as much progress has been made by building and analyzing programs as by examining theoretical questions. MYCIN is one of several well-known programs that embody some intelligence and provide data on the extent to which intelligent behavior can be programmed. As with other AI programs, its development was slow and not always in a forward direction. But we feel we learned some useful lessons in the course of nearly a decade of work on MYCIN and related programs. In this book we share the results of many experiments performed in that time, and we try to paint a coherent picture of the work. The book is intended to be a critical analysis of several pieces of related research, performed by a large number of scientists. We believe that the whole field of AI will benefit from such attempts to take a detailed retrospective look at experiments, for in this way the scientific foundations of the field will gradually be defined. It is for all these reasons that we have prepared this analysis of the MYCIN experiments.

The complete book in a single file.

This report covers two main AI areas: natural language processing and expert systems. The discussion of each area includes an assessment of the state-of-the-art, an enumeration of problems areas and opportunities, recommendations for the next 5-10 years, and an assessment of the resources required to carry them out. A discussion of possible university-industry-government cooperative efforts is also included.

ABSTRACT: Objects move, collide, flow, bend, heat up, cool down, stretch, compress . and boil. These and otherthings that cause changes in objects over time are intuitively characterized as processes . To understandcommonsense physical reasoning and make programs that interact with the physical world as well aspeople do we must understand qualitative reasoning about processes, when they will occur, theireffects, and when they will stop. Qualitative process theory defines a simple notion of physical processthat appears useful as a language in which to write dynamical theories. Reasoning about processesalso motivates a new qualitative representation for quantity in terms of inequalities, called thequantity space . This paper describes the basic concepts of qualitative process theory, several differentkinds of reasoning that can be performed with them, and discusses its implications for causalreasoning. Several extended examples illustrate the utility of the theory, including figuring out that aboiler can blow up, that an oscillator with friction will eventually stop, and how to say that you canpull with a string, but not push with it. Journal-length version of Ph.D. dissertation, , MIT, 1985.Artifiicial Intelligence. Also In Bobrow, D. (Ed.), Qualitative Reasoning About Physical Systems, pp. 85–186. MIT Press. Also in Artificial Intelligence 24:85-168 (1984).

AI research at CMU is closely integrated with other activities in the Computer Science Department, and to a major degree with ongoing research in the Psychology Department. Although there are over 50 faculty, staff and graduate students involved in various aspects of AI research, there is no administratively (or physically) separate AI laboratory. To underscore the interdisciplinary nature of our AI research, a significant fraction of the projects listed below are joint ventures between computer science and psychology.

Time is a critical context for understanding how things function. It serves as the digital history for businesses. When you think about institutional knowledge, that's not just bound up in people. Data is part of that knowledge base as well. So, when companies can capture, store and analyze that data in an effective way, it produces better results.