Essentially a survey of the development of PC-based expert systems and a review of existing applications, languages, and shells, this book leaves many of the important questions unanswered.

Proc. Tenth Intl. Joint Conference on Artificial Intelligence (pp. 334-337). Milan, Italy: IJCAII.

IEEE Computer, pages 100-109, January

Letters to the Editor

Other interesting topics in superb, it still contains inadequacies. This statement is more this chapter include nonmonotonic reasoning and modal and a testament to how remarkably difficult it is to write an adequate intentional logic. Perhaps the most intriguing chapter is introductory AI text than it is a criticism of the job done "Memory Organization and Deduction," which touches by the authors. Because there really are no single volumes upon the topics of frame-based representation and deductive yet that provide a satisfactory introduction to AI, the best retrieval and introduces the time-order representation approaches way to approach the problem of selecting text material for an of temporal system analysis and time map management introductory AI course seems to be use a book such as this .

Other interesting topics in superb, it still contains inadequacies. This statement is more this chapter include nonmonotonic reasoning and modal and a testament to how remarkably difficult it is to write an adequate intentional logic. Perhaps the most intriguing chapter is introductory AI text than it is a criticism of the job done "Memory Organization and Deduction," which touches by the authors. Because there really are no single volumes upon the topics of frame-based representation and deductive yet that provide a satisfactory introduction to AI, the best retrieval and introduces the time-order representation approaches way to approach the problem of selecting text material for an of temporal system analysis and time map management introductory AI course seems to be use a book such as this .

Initial Development Approach In the following eight subsections, we present a brief discussion of methodology for expert system development, selection of problem and tools, knowledge engineering and prototype implementation, operational feasibility, and the actual development of a working prototype of a process planning expert system. Methodology for Expert System Development Expert systems require a software development methodology that differs in some respects from those methodologies used for conventional systems. Most knowledge-based development methodologies used by organizations experienced in building expert systems are similar in that they concentrate on the early (feasibility) stages of a project. Very little has been published on the later stages, which are concerned with expert system delivery, integration, and maintenance. During the development of OPGEN, we incorporated the lessons learned in these early stages and revised our original approach to provide for integration and maintenance. Most expert system development methodologies are a variation on the following theme, which paraphrases Haycs-Roth (1985): (1) expert system technology is determined to be relevant to a product; (2) management provides an opportunity for action; (3) a preliminary business application is assembled; (4) a knowledge engineering consultant verifies the opportunity; (5) a knowledge engineering project team is formed and assesses the knowledge; (6) the knowledge engineering project manager plans the project; (7) the user organization Figure 2 OPGEN bzput Circuit Layout Diagram.

To know that the other suffers, we have to close the gap between us in an act of empathy. Only then can we begin Editor. Whatever his other attitudes, Dr. Frankenstein knows that his creation suffers In his interesting article "Artificial Intelligence and Ethics: and knows it in the way he knows human beings suffer. An Exercise in the Moral Imagination," Michael LaChat Closely connected to this is the point that just as we have says that the basic outline of Shelley's Frmkensteirz needs to the moral obligation not to err on the wrong side in the fulfillment be recapitulated "even if, as is usually the case, the reader of our obligations toward suffering human beings (that has seen only the poor image of the book in movie form " is, WC should not fail to fulfill our obligations toward them Contrary to what Mr. LaChat says, I think the poor image just because we think they are not really suffering or, worse, most people have of the book is sufficient reason to give a because we haven't been able to prove that they are really short outline of the original story. Doing this, we find one or suffering), we ought not to err on the wrong side for the two arguments that were not mentioned in LaChat's article wrong reason in the case of suffering artifacts.

Large engineering projects, such as the engineering development of computers, involve a large number of activities and require cooperation across a number of departments. Due to technological and market uncertainties, these projects involve the management of a large number of changes. The Callisto project was born out of realization that the classical approaches to project management do not provide sufficient functionally to manage large engineering projects. Callisto was initiated as a research effort to explore project scheduling, control and configuration problems during the engineering prototype development of large computer systems and to devise intelligent project management tools that facilitate the documentation of project management expertise and its reuse from one project to another. In the first phase of the project, rule-based prototypes were used to build quick prototypes of project management expertise and the project management knowledge required to support expert project managers. In the second phase, the understanding of point solutions was used to capture the underlying models of project management in distributed project negotiations and comparative analysis. This article provides an overview of the problems, experiments, and the resulting models of project knowledge and constraint-directed negotiation.

Letters to the Editor