From Tetherless World Wiki
Citation: Thomas R. Gruber and Daniel M. Russell. (1994) Generative design rationale: Beyond the record and replay paradigm. In Design rationale: concepts, techniques and use, ,,1994.
| Publication article ( Edit )
|
| type | Article
|
| bibtype | article
|
| Bibtex basics
|
| author | Thomas R. Gruber and Daniel M. Russell
|
| title | Generative design rationale: Beyond the record and replay paradigm
|
| journal | Design rationale: concepts, techniques and use
|
| year | 1994
|
| Bibtex more
|
| note | Updated February 1993.
|
| publisher | Lawrence Erlbaum Associates
|
| Access Paper
|
| abstract | Research in design rationale support must confront the fundamental questions of what kinds of design rationale information should be captured, and how rationales can be used to support engineering practice. This paper examines the kinds of information used in design rationale explanations, relating them to the kinds of computational services that can be provided . Implications for the design of software tools for design rationale support are given. The analysis predicts that the "record and replay" paradigm of structured note-taking tools (electronic notebooks, deliberation notes, decision histories) may be inadequate to the task. Instead, we argue for a generative approach in which design rationale explanations are constructed, in response to information requests, from background knowledge and information captured during design. Support services based on the generative paradigm, such as design dependency management and rationale by demonstration, will require more formal integration between the rationale knowledge capture tools and existing engineering software.
|
| KSL Technical Report ID: KSL-92-59
|
Facts about Generative design rationale: Beyond the record and replay paradigmRDF feed
| Abstract | Research in design rationale support must … Research in design rationale support must confront the fundamental questions of what kinds of design rationale information should be captured, and how rationales can be used to support engineering practice. This paper examines the kinds of information used in design rationale explanations, relating them to the kinds of computational services that can be provided . Implications for the design of software tools for design rationale support are given. The analysis predicts that the "record and replay" paradigm of structured note-taking tools (electronic notebooks, deliberation notes, decision histories) may be inadequate to the task. Instead, we argue for a generative approach in which design rationale explanations are constructed, in response to information requests, from background knowledge and information captured during design. Support services based on the generative paradigm, such as design dependency management and rationale by demonstration, will require more formal integration between the rationale knowledge capture tools and existing engineering software. e tools and existing engineering software. |
| Author | Thomas R. Gruber and Daniel M. Russell + |
| Bibtype | article + |
| Has author | Thomas R. Gruber and Daniel M. Russell + |
| Has identifier | KSL-92-59 + |
| Has publishing details | ,,1994 + |
| Has title | Generative design rationale: Beyond the record and replay paradigm + |
| Has where published | Design rationale: concepts, techniques and use + |
| Has year | 1994 + |
| Journal | Design rationale: concepts, techniques and use + |
| Ksl tr id | KSL-92-59 + |
| Note | Updated February 1993. |
| Process note | GOOGLE + |
| Publisher | Lawrence Erlbaum Associates + |
| Title | Generative design rationale: Beyond the record and replay paradigm + |
| Year | 1994 + |
