Information sharing and decision coordination are central problems for large-scale product development. This paper proposes a framework for supporting a knowledge medium [32]: a computational environment in which explicitly represented knowledge serves as a communication medium among people and their programs. The framework is designed to support information sharing and coordinated communication among members of a product development organization, particularly for the tasks of design knowledge capture, dynamic notification of design changes, and active management of design dependencies. The proposed technology consists of a shared knowledge representation (language and vocabulary), protocols for foreign data encapsulation and posting to the shared environment, and mechanisms for content-directed routing of posted information to interested parties via subscription and notification services. A range of possible applications can be explored in this framework, depending on the ...

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 ...

Many researchers have proposed representational schemes to capture complex reasoned discourses. In this paper, we use our experiences with argument representation to examine some of the issues affecting the design of these representational schemes. Our discussions focus on how well a particular scheme, Toulmin structures, maps into the domain of argumentative discourse and captures and highlights various phenomena we consider central to argumentation. We then use this analysis to explore several complementary representational schemes. Finally, we discuss some relatively unexplored factors that influence the usability of these schemes. 1.

Technology development in HCI can be interpreted as a co-evolution of tasks and artifacts. The tasks people actually engage in (successfully or problematically) and those they wish to engage in (or perhaps merely to imagine) define requirements for future technology, and specifically for new HCI artifacts. These artifacts, in turn, open up new possibilities for human tasks, new ways to do familiar things, entirely new kinds of things to do. In this paper we describe psychological design rationale as an approach to augmenting HCI technology development and to clarifying the sense in which HCI artifacts embody psychological theory. A psychological design rationale is an enumeration of the psychological claims embodied by an artifact for the situations in which it is used. As an example, we present our design work with the View Matcher, a Smalltalk programming environment for coordinating multiple views of an example application. In particular, we show how psychological design rationale was used to develop a view matcher for code reuse from prior design rationales for related programming tasks and environments. 1. TASKS AND ARTIFACTS In 1605, Sir Francis Bacon called for a "natural history of trades." He urged that technical tools, techniques and processes be made more public and explicit. This was one element in his broader project of developing practical science, and hinged on the assumption that if such knowledge could be more systematically considered and integrated, human progress would necessarily result. Thus, Bacon suggested that new concepts and inventions would result "by a connexion and transferring of the observations of one Arte, to the use of another, when the experiences of several misteries shall fall under the consideration of one man's minde."(1970: Book...

A design rationale is an explanation of why something is designed as it is. In this paper we analyze the sources of knowledge and inference underlying design rationale. We examine protocols of people talking about designs in several domains to identify kinds of design information that are requested and used. We classify the information types along dimensions including the source of the information, how the information is or could be captured, and whether it is retrieved or inferred. We find that the sources of knowledge used to explain a design are manifold, including models of the artifact and how it works, models of design methods and decision making processes, and understanding of the intended functionality and other requirements. We observe that design rationale explanations are often constructed from several of these sources, supported by activities such as information retrieval, simulation, hypothesis testing, and decision making. These observations can inform the design of desig...

A few representations have been used for capturing design rationale. It is important to know in what ways they are adequate or limited so that we know how to improve them. In this paper, we develop a framework for evaluating design rationale representations based on a set of generic design tasks. We build the framework by progressively differentiating the elements of design rationale that, when made explicit, support an increasing number of the design tasks. With this framework, we evaluate the expressiveness of the existing representations. We also present a language, DRL, that we believe is the most expressive of the existing representations without being too complex for human users. We also discuss the limitations of DRL as open problems for further research.