DRCS: An Integrated System for Capture of Designs and Their Rationale

In current design practice, the rationale for design decisions is captured, if at all, as a collection of paper documents, project and personal notebook entries as well as designer’s recollections, and is maintained distinctly from the description of the design itself. Increasing demands for higher product quality and lower cost, the growing complexity of the artifacts we design as well as the highly distributed nature of modern manufacturing enterprises is making it increasingly critical that design rationale be captured in a highly usable form, and in particular one that allows us to harness the power of computers to support our activities. Existing rationale capture systems, however, have important limitations: they are either not oriented specifically towards the design process or use a representation not easily generalizable to the full range of potential design problems. This document presents a rationale capture language and system that transcends these limitations by being able to capture designs and their rationale in an integrated way.

[1]  GruberThomas Learning Why by Being Told What , 1991 .

[2]  Mark Stefik,et al.  Planning with Constraints (MOLGEN: Part 1) , 1981, Artif. Intell..

[3]  Thomas P. Moran,et al.  Design rationale: the argument behind the artifact , 1989, CHI '89.

[4]  Slawomir Zadrozny,et al.  An interactive multi-user decision support system for consensus reaching processes using fuzzy logic with linguistic quantifiers , 1988, Decis. Support Syst..

[5]  Tom M. Mitchell,et al.  A Knowledge Based Approach to VLSI CAD the Redesign System , 1984, 21st Design Automation Conference Proceedings.

[6]  Colin Potts,et al.  Recording the reasons for design decisions , 1988, Proceedings. [1989] 11th International Conference on Software Engineering.

[7]  Mark Klein,et al.  Insight into Cooperative Group Design: Experience with the LAN Designer System , 1991 .

[8]  John McDermott,et al.  VT: an expert elevator designer , 1987 .

[9]  Jack Mostow,et al.  Automated reuse of design plans , 1989, Artif. Intell. Eng..

[10]  Tom M. Mitchell,et al.  LEAP: A Learning Apprentice for VLSI Design , 1985, IJCAI.

[11]  Jintae Lee,et al.  What's in design rationale? , 1991 .

[12]  Tom M. Mitchell,et al.  A Knowledge-Based Approach to Design , 1985, IEEE Transactions on Pattern Analysis and Machine Intelligence.

[13]  Paul R. Cohen,et al.  Design for Acquisition: Principles of Knowledge-System Design to Facilitate Knowledge Acquisition , 1987, Int. J. Man Mach. Stud..

[14]  John P. McDermott,et al.  R1: A Rule-Based Configurer of Computer Systems , 1982, Artif. Intell..

[15]  David C. Brown,et al.  Failure handling in a design expert system , 1985 .

[16]  Raymond McCall,et al.  Design environments for constructive and argumentative design , 1989, CHI '89.

[17]  Sanjay Mittal,et al.  A Knowledge-Based Framework for Design , 1986, AAAI.

[18]  Thomas R. Gruber,et al.  Learning why by being told what: interactive acquisition of justifications , 1991, IEEE Expert.

[19]  Gerald Jay Sussman,et al.  CONSTRAINTS - A Language for Expressing Almost-Hierarchical Descriptions , 1980, Artif. Intell..

[20]  David Chapman,et al.  Planning for Conjunctive Goals , 1987, Artif. Intell..

[21]  Raymond McCall,et al.  Making argumentation serve design , 1991 .

[22]  K. C. Burgess Yakemovic,et al.  Report on a development project use of an issue-based information system , 1990, CSCW '90.

[23]  Judea Pearl,et al.  Reverend Bayes on Inference Engines: A Distributed Hierarchical Approach , 1982, AAAI.

[24]  Wolter J. Fabrycky,et al.  Systems engineering and analysis , 1981 .

[25]  Johan de Kleer,et al.  Choices Without Backtracking , 1984, AAAI.

[26]  Mark Klein,et al.  Supporting conflict resolution in cooperative design systems , 1991, IEEE Trans. Syst. Man Cybern..

[27]  Michael L. Begeman,et al.  gIBIS: a hypertext tool for team design deliberation , 1987, Hypertext.