%0 Book %1 hendler88 %A Hendler, James %B Human/Computer Interaction %C Norwood, NJ %D 1988 %I Ablex Publishing %K information knowledge acquisition visualization %T Expert Systems: The User Interface %X This book takes a broad view of the work going on in the development of user interfaces for expert systems and examines the expert system building process both in academic and industrial surroundings. The development of an expert system is viewed as containing three separate, but highly interacting components: knowledge capture, programming and debugging the system, and finally placing the system before an active user community. Some of the issues addressed include: providing tools for the different personnel involved in each of the three components, the application of general human factors principles in the design of expert systems, the special needs in the design of expert systems, and the efficacy of these interfaces.

@book{hendler88, abstract = {This book takes a broad view of the work going on in the development of user interfaces for expert systems and examines the expert system building process both in academic and industrial surroundings. The development of an expert system is viewed as containing three separate, but highly interacting components: knowledge capture, programming and debugging the system, and finally placing the system before an active user community. Some of the issues addressed include: providing tools for the different personnel involved in each of the three components, the application of general human factors principles in the design of expert systems, the special needs in the design of expert systems, and the efficacy of these interfaces.}, added-at = {2006-03-24T16:34:33.000+0100}, address = {Norwood, NJ}, author = {Hendler, James}, biburl = {https://www.bibsonomy.org/bibtex/2966ef8ae7119f92610dbc422f629b7c7/neilernst}, citeulike-article-id = {121850}, comment = {..rapid growth often leads to difficult to use systems.. will ES be the same?" most definitely was poses some questions 1- does snazzy new AI tech mean we can ignore UI? yeah right 2 - are ES any different than traditional tech? no, some differences but not that distinct - must represent exactly the decisions the system makes (can't trust MYCIN?) 3 - what design areas are often overlooked? why is ES not adopted? Hendler says : skepticism over AI in general, being told what is correct by a machine, no stats that show the benefits, other problems: workplace differences, new hardware(? not that relevant now). Calls for a dialogue similar to the KA dialogue between interface designer and user (15 ya!) 4 - any examples? THEO given. Interesting but a little ancient. Calls for an iterative design approach. 5 - other considerations: conceptual model with explanation 6 - interface consideration is a large part of it!}, description = {sdasda}, interhash = {5435f2d9611caaf242fe780e46971358}, intrahash = {966ef8ae7119f92610dbc422f629b7c7}, keywords = {information knowledge acquisition visualization}, priority = {0}, publisher = {Ablex Publishing}, series = {Human/Computer Interaction}, timestamp = {2006-03-24T16:34:33.000+0100}, title = {Expert {S}ystems: {T}he {U}ser {I}nterface}, year = 1988 }