{"title":"The importance of expert systems in a hypermedia environment","authors":"J. P. Coyne","doi":"10.1109/MESPP.1990.122709","DOIUrl":"https://doi.org/10.1109/MESPP.1990.122709","url":null,"abstract":"It is argued that the success of hypermedia systems will ultimately depend on expert systems technology. The capabilities of hypermedia software that would exploit the speed and storage capacity of the computer while retaining the desirable characteristics of a good paper-based system are described.<<ETX>>","PeriodicalId":232478,"journal":{"name":"Proceedings [1990] IEEE Conference on Managing Expert System Programs and Projects","volume":"42 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1990-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128251119","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"The Fleet Command Center Battle Management Project: lessons learned","authors":"R. Saunders","doi":"10.1109/MESPP.1990.122676","DOIUrl":"https://doi.org/10.1109/MESPP.1990.122676","url":null,"abstract":"Lessons learned from the experience of the Fleet Command Center Battle Management Program (FCCBMP) are documented. FCCBMP is an element of the Defense Advanced Project Agency's Strategic Computing Program (SCP), which aims to stimulate the development and application of advanced technologies for military problems. FCCBMP has been the most successful of the SCP programs to date in bringing expert systems into operational use. It is noted that lessons from the FCCBMP program can help in managing the development of expert systems and systems developed using rapid prototyping. It is concluded that FCCBMP has demonstrated the feasibility of applying expert systems to operational military problems. When developing expert systems intended to support operational users, there are strong advantages in developing expert systems on-site in the operational environment. The use of rapid prototyping does not mean undisciplined development. Rapid prototyping can be managed by selectively adapting traditional software engineering techniques for use during the development phase. The knowledge engineering required by an expert system project can suggest improvements to existing methods of operation.<<ETX>>","PeriodicalId":232478,"journal":{"name":"Proceedings [1990] IEEE Conference on Managing Expert System Programs and Projects","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1990-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125685358","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Building on success-lessons learned (expert systems)","authors":"R. Crittenden","doi":"10.1109/MESPP.1990.122679","DOIUrl":"https://doi.org/10.1109/MESPP.1990.122679","url":null,"abstract":"The author examines a case study of a beginning expert systems program at a large regional life insurance company, a program that began with excellent success, but has not been able to follow up on that success. Through examination of this case, the author points out lessons that can be learned from this experience, and suggests means of preventing this type of failure in other beginning-expert-systems programs. The first lesson learned is that there must be strong and consistent messages to management that the major benefits of the technology will be missed if the primary purpose of an expert-systems program is seen as short-term cost reduction. Secondly, there must be strong and consistent messages to management that education of middle managers is essential to the success of the program. Third for long-term success of the technology, there must be a plan for the development of critical mass in the organization. In many organizations, the best way to achieve critical mass is through the utilization of the experts themselves as end-user developers.<<ETX>>","PeriodicalId":232478,"journal":{"name":"Proceedings [1990] IEEE Conference on Managing Expert System Programs and Projects","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1990-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115872170","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"A strategy for transferring expert systems technology to industry","authors":"F. J. Cantu-Ortiz","doi":"10.1109/MESPP.1990.122678","DOIUrl":"https://doi.org/10.1109/MESPP.1990.122678","url":null,"abstract":"A strategy is presented for transferring expert system technology from university to industry. This strategy is based on five years of experience in developing expert and knowledge-based systems for academic and industrial applications in Mexico. The strategy includes KBS (knowledge-based system) technology assimilation, applied research and development with graduate students in computer science and artificial intelligence, an annual program of seminars on expert systems, an annual international symposium on artificial intelligence applications, research agreements with companies to develop expert system prototypes in manufacturing, including the training of knowledge engineers from the sponsoring companies, and the formation of the Center for Artificial Intelligence to do human resources education, applied research, and technological development. Lessons learned in selling expert systems, problem domain selection, cost/benefit analysis, management of expert systems projects, and expert system tool selection are mentioned.<<ETX>>","PeriodicalId":232478,"journal":{"name":"Proceedings [1990] IEEE Conference on Managing Expert System Programs and Projects","volume":"37 3","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1990-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"113933630","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"The LQMS research project: a case study in knowledge-based system development","authors":"D. M. O'Neill, P. Mullarkey, P. Gingrich","doi":"10.1109/MESPP.1990.122677","DOIUrl":"https://doi.org/10.1109/MESPP.1990.122677","url":null,"abstract":"The Log Quality Monitoring System (LQMS) is a medium-sized knowledge-based system that was developed to address the problem of providing real-time assistance to the wireline field engineer. The authors discuss the motivation for the project, review the major decisions that were made, detail how they affected the direction of the project, and identify the basic lessons that were learned. The research version of LQMS was developed at Schlumberger-Doll Research over a period of about three and a half years. The project successfully dealt with several thorny issues in the development of knowledge-based systems: multiple domain experts, real time constraints, embedded environment, coordination and communication of multiple knowledge sources, and technology transfer. The project evolved from an exploratory, rapid prototyping style of development to a more traditional specify/design/implement/test methodology. Much of this evolution was driven by the field testing and technology transfer requirements of the later stages of the project.<<ETX>>","PeriodicalId":232478,"journal":{"name":"Proceedings [1990] IEEE Conference on Managing Expert System Programs and Projects","volume":"101 1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1990-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127447416","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Managing expert systems for New Federalism","authors":"W. Foskett","doi":"10.1109/MESPP.1990.122683","DOIUrl":"https://doi.org/10.1109/MESPP.1990.122683","url":null,"abstract":"Change in the locus of operating knowledge that accompanies 'New Federalism' policies implies different design and knowledge-engineering approaches for expert system applications. An expert systems strategy to implement a New Federalism approach in a Congressionally-mandated regulatory program is discussed. Tactical needs created by competition with conventional knowledge-delivery mechanisms are analyzed. Three knowledge-engineering tactics especially suitable for developing expert systems in this application environment are described.<<ETX>>","PeriodicalId":232478,"journal":{"name":"Proceedings [1990] IEEE Conference on Managing Expert System Programs and Projects","volume":"16 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1990-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127460869","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"A natural language interface for expert system help desks","authors":"C.F. Drew","doi":"10.1109/MESPP.1990.122710","DOIUrl":"https://doi.org/10.1109/MESPP.1990.122710","url":null,"abstract":"The author addresses how a natural language interface might be written entirely within IBM's Expert System Environment Shell (ESE). The interface is designed around the help desk application, a diagnostic knowledge base. The implementation uses techniques called FASTPATH, INHERIT, and CHGPATH.<<ETX>>","PeriodicalId":232478,"journal":{"name":"Proceedings [1990] IEEE Conference on Managing Expert System Programs and Projects","volume":"38 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1990-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123340843","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Lessons learned in developing an expert systems group","authors":"M. Bray","doi":"10.1109/MESPP.1990.122698","DOIUrl":"https://doi.org/10.1109/MESPP.1990.122698","url":null,"abstract":"The author discusses the experiences at the Idaho National Engineering Laboratory in developing an expert systems/advanced computer technology organization. A brief history of the group is presented with discussions of personnel, training, hardware, and software. Two example applications from the laboratory are briefly described to point out some lessons learned. The author presents several opinions/lessons learned in developing expert systems capability and applying expert systems technology.<<ETX>>","PeriodicalId":232478,"journal":{"name":"Proceedings [1990] IEEE Conference on Managing Expert System Programs and Projects","volume":"312 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1990-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134222995","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Expert system project management issues","authors":"G. Lynn, B. Procaccini","doi":"10.1109/MESPP.1990.122682","DOIUrl":"https://doi.org/10.1109/MESPP.1990.122682","url":null,"abstract":"Managers of expert system projects are likely to face three major challenges: uncertainty over the project scope, lack of sponsor commitment, and limitations of available resources. These issues are discussed and suggestions are offered for minimizing their impact.<<ETX>>","PeriodicalId":232478,"journal":{"name":"Proceedings [1990] IEEE Conference on Managing Expert System Programs and Projects","volume":"48 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1990-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134436907","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Mapping the expert systems development process to the Department of Defense life-cycle model","authors":"A.F.U. Khan","doi":"10.1109/MESPP.1990.122673","DOIUrl":"https://doi.org/10.1109/MESPP.1990.122673","url":null,"abstract":"The author reports on the results of a study performed by a team from RAND Corp. and the 7th Communications Group (USAF) for the Office of the Assistant Secretary of Defense for Production and Logistics. The study guides managers and technicians seeking expert systems (ES) solutions. It is noted that, as ES developments are software engineering efforts, the lessons learned building software over the past decades still apply. DoD software engineering and life-cycle policies can be applied to ES developments. The practical methodology elaborated in the study maps the rapid prototyping paradigm to DoD standards using the spiral model and risk containment strategies as described by B.W. Boehm. Furthermore, software life-cycle management and documentation standards reflect a hardware bias which also affects conventional software developments. Other peculiarities of ES developments are not totally unique to expert systems, either. Modern conventional software developments arc experiencing many of the same problems. Hence, it is concluded that the standards and acquisition practices of yesterday need to evolve to accommodate the nature of software development in the 1990s and beyond.<<ETX>>","PeriodicalId":232478,"journal":{"name":"Proceedings [1990] IEEE Conference on Managing Expert System Programs and Projects","volume":"93 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1990-09-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126209237","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}