28.06.2013 Views

Papers in PDF format

Papers in PDF format

Papers in PDF format

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Introduction<br />

Put Your Experience on The Web:<br />

A Tool for Creat<strong>in</strong>g and Brows<strong>in</strong>g <strong>in</strong> Case Libraries<br />

VALERY A. PETRUSHIN, JANET L. KOLODNER<br />

EduTech Institute,<br />

Georgia Institute of Technology<br />

Atlanta, USA<br />

e-mail: {petr, jlk}@cc.gatech.edu<br />

This paper describes a class of AI software called Case-Based Aid<strong>in</strong>g Systems (CBAS) and a tool for creat<strong>in</strong>g<br />

and us<strong>in</strong>g such systems <strong>in</strong> both off-l<strong>in</strong>e and on-l<strong>in</strong>e modes. CBAS is <strong>in</strong>tended for improv<strong>in</strong>g human decision<br />

mak<strong>in</strong>g us<strong>in</strong>g Case-based Reason<strong>in</strong>g approach [Kolodner, 1993]. Accord<strong>in</strong>g to [Kolodner, 1991], a CBAS<br />

would provide cases to human problem solvers at appropriate times to help them with such tasks as com<strong>in</strong>g up<br />

with solutions, adapt<strong>in</strong>g old solutions, and warn<strong>in</strong>g of potential problems. A CBAS looks like a smart<br />

database. It retrieves cases based on user requests. But it is more than a database because it uses more<br />

sophisticated search<strong>in</strong>g methods for f<strong>in</strong>d<strong>in</strong>g partially match<strong>in</strong>g cases.<br />

A specific class of CBAS called Case-Based Design Aid (CBDA) has been developed over the past 6<br />

years at the Georgia Institute of Technology. A CBDA is “a tool to help a designer produce designs more<br />

successfully and more quickly” [Domeshek, 1994]. The CBDA serves as common memory for designers. It<br />

allows the designer to retrieve relevant cases and to <strong>in</strong>dex and store a new design creat<strong>in</strong>g a synergetic power<br />

of human-computer <strong>in</strong>teraction. It does not automate the process of design but serves as a source of <strong>in</strong>spiration<br />

and creativity for designers. Ow<strong>in</strong>g to efforts of many researchers, a shell Design-MUSE for build<strong>in</strong>g CBDA<br />

has been implemented [Domeshek, 1994]) and several CBDAs for different problem doma<strong>in</strong>s have been<br />

created: build<strong>in</strong>gs design - Archie and Archie-II [Domeshek & Kolodner, 1992], plann<strong>in</strong>g lessons - SciEd<br />

[Kolodner, 1991a], aircraft subsystem design - MIDAS [Domeshek, Herndon, Bennett, & Kolodner, 1994],<br />

susta<strong>in</strong>able technology - SUSIE. The above projects showed the feasibility and range of applicability of<br />

CBDA’s and taught many lessons about how cases needed to be represented and what the user's <strong>in</strong>terface<br />

should look like.<br />

The CBAS can be used to solve a wide range of problems <strong>in</strong> bus<strong>in</strong>ess and education. The salient<br />

feature of a CBAS is its extendibility. A CBAS may serve as a log or dairy of your professional or social<br />

growth from novice to expert. It is your extra m<strong>in</strong>d. It can also serve as a common shared memory for a group<br />

of experts or a corporation. In education a CBAS can serve as a source of knowledge when students browse it<br />

and as a cognitive tool when students create their own CBASs.<br />

ExtraM<strong>in</strong>d: a Shell for build<strong>in</strong>g Case-Based Aid<strong>in</strong>g Systems<br />

ExtraM<strong>in</strong>d <strong>in</strong>herits many features of the Design-MUSE’s case library structure and is designed to be more<br />

generally-applicable and run on both platforms (Mac<strong>in</strong>tosh and IBM PC) and on the WWW. Like Design-<br />

MUSE, it can be used to build CBASs. Such a system consists of a library of cases, retrieval eng<strong>in</strong>e, and user’s<br />

<strong>in</strong>terface. The case library conta<strong>in</strong>s of a set of cases. A case may represent an artifact or an event. Each case<br />

may have parts (subcases) and/or views. A part can also have parts and views. There are no limits on the<br />

number of parts or nest<strong>in</strong>g level. A part may belong to several superparts or cases. Cases, parts and views form<br />

a (partial) hierarchy of a CBA’s memory. Each case, part, or view can have l<strong>in</strong>ks to stories and sources. A<br />

story is an evaluated description of particular artifact or event which relates to the case(s) and illustrates<br />

problems and responses to the problems (decisions). Each story (and especially negative ones) should teach a<br />

lesson to the user. A story has l<strong>in</strong>ks to the relevant cases (parts and/or views), problems and responses. A<br />

problem presents the descriptions of some general difficulties which relate to the stories. A problem is tied to<br />

the relevant responses, stories and cases (parts and/or views). A response presents a general strategy which has<br />

been applied to solve a problem. It also has description and l<strong>in</strong>ks which tie it to relevant problems, stories and<br />

cases. A source is a reference to a source of <strong>in</strong><strong>format</strong>ion used <strong>in</strong> a case (part or view), story, problem or

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!