| M. Klein. Supporting Conflict Management in Cooperative Design Teams. Journal on Group Decision and Negotiation, 2:259-278, 1993. |
....components, the system must guide designers in creating new components, whose attributes may be drawn from an infinite set (e.g. rational numbers) or even a nonordered set (e.g. material) This decomposition is the one addressed by RAPPID, which uses a setnarrowing heuristic to avoid conflicts. [9, 10] also supports designers as agents, using conflict resolution heuristics to deal with conflicts after they arise. In many problem domains, the design process is dominated by complex tools (such as finite element codes for mechanical design, or circuit emulators for microprocessor design) These ....
....RAPPID bears most immediate comparison with the part centric and designer centric systems identified above. Systems focused on features, design tools, and design functions are largely orthogonal to RAPPID s objectives. RAPPID s set based dynamics offer a fundamental contrast to Klein s approach [9, 10]. Klein sees conflict as central to design, and so provides mechanisms primarily for the resolution of conflicts after they arise. RAPPID recognizes conflicts as a symptom of a defective design philosophy, one that jumps prematurely to point solutions. Its mechanisms focus on ways for designers to ....
M. Klein. Supporting Conflict Management in Cooperative Design Teams. Journal on Group Decision and Negotiation, 2:259-278, 1993.
....components, the system must guide designers in creating new components, whose attributes may be drawn from an infinite set (e.g. rational numbers) or even a nonordered set (e.g. material) This decomposition is the one addressed by RAPPID, which uses a setnarrowing heuristic to avoid conflicts. [9, 10] also supports designers as agents, using conflict resolution heuristics to deal with conflicts after they arise. In many problem domains, the design process is dominated by complex tools (such as finite element codes for mechanical design, or circuit emulators for microprocessor design) These ....
....RAPPID bears most immediate comparison with the part centric and designer centric systems identified above. Systems focused on features, design tools, and design functions are largely orthogonal to RAPPID s objectives. RAPPID s set based dynamics offer a fundamental contrast to Klein s approach [9, 10]. Klein sees conflict as central to design, and so provides mechanisms primarily for the resolution of conflicts after they arise. RAPPID recognizes conflicts as a symptom of a defective design philosophy, one that jumps prematurely to point solutions. Its mechanisms focus on ways for designers to ....
M. Klein. Supporting Conflict Management in Cooperative Design Teams. In Proceedings of 11th Inter. Workshop on DAI, pages 155-81, 1992.
....by the system. 4. EVALUATION: CONTRIBUTION TO IMPROVING AGENT BASED SYSTEMS The ideas described in this paper have already been substantially validated through nearly a decade of development and evaluation of successful systems for resolving multi agent exceptions in the collaborative design [14, 16, 26] and collaborative requirements capture [21] domains. This led to the development of the basic heuristic classification approach, software tools for exception diagnosis and resolution, a substantive standardized language for communication between agents and the exception handling service, a highly ....
Klein, M., Supporting Conflict Management in Cooperative Design Teams. Journal on Group Decision and Negotiation, 1993. 2: p. 259-278.
....the system must guide designers in creating new components, whose attributes may be drawn from an infinite set (e.g. rational numbers) or even a non ordered set (e.g. material) This decomposition is the one addressed by RAPPID, which uses a set narrowing heuristic to avoid conflicts. [10, 11] also supports designers as agents, using conflict resolution heuristics to deal with conflicts after they arise. In many problem domains, the design process is dominated by complex tools (such as finiteelement codes for mechanical design, or circuit emulators for microprocessor design) These ....
....RAPPID bears most immediate comparison with the part centric and designer centric systems identified above. Systems focused on features, design tools, and design functions are largely orthogonal to RAPPID s objectives. RAPPID s set based dynamics offer a fundamental contrast to Klein s approach [10, 11]. Klein sees conflict as central to design, and so provides mechanisms primarily for the resolution of conflicts after they arise. RAPPID recognizes conflicts as a symptom of a defective design philosophy, one that jumps prematurely to point solutions. Its mechanisms focus on ways for designers to ....
M. Klein. Supporting Conflict Management in Cooperative Design Teams. Journal on Group Decision and Negotiation, 2:259-278, 1993.
....the system must guide designers in creating new components, whose attributes may be drawn from an infinite set (e.g. rational numbers) or even a non ordered set (e.g. material) This decomposition is the one addressed by RAPPID, which uses a set narrowing heuristic to avoid conflicts. [10, 11] also supports designers as agents, using conflict resolution heuristics to deal with conflicts after they arise. In many problem domains, the design process is dominated by complex tools (such as finiteelement codes for mechanical design, or circuit emulators for microprocessor design) These ....
....RAPPID bears most immediate comparison with the part centric and designer centric systems identified above. Systems focused on features, design tools, and design functions are largely orthogonal to RAPPID s objectives. RAPPID s set based dynamics offer a fundamental contrast to Klein s approach [10, 11]. Klein sees conflict as central to design, and so provides mechanisms primarily for the resolution of conflicts after they arise. RAPPID recognizes conflicts as a symptom of a defective design philosophy, one that jumps prematurely to point solutions. Its mechanisms focus on ways for designers to ....
M. Klein. Supporting Conflict Management in Cooperative Design Teams. In Proceedings of 11th Inter. Workshop on DAI, pages 155-81, 1992.
.... make distant analogies, and utilize recombinant (mix andmatch) design techniques (Herman, Klein et al. 1998) The other key component of this work is nearly a decade of development and evaluation of systems for handling multi agent conflicts in collaborative design (Klein 1989; Klein 1991; Klein 1993) and collaborative requirements capture (Klein 1997) This work resulted in principles and technology for automatically detecting, diagnosing and resolving design conflicts between both human and computational agents, building upon a knowledge base of roughly 300 conflict types and resolution ....
....the preconditions for different exception types and handlers. Examples include questions about the status of a task, the status of a resource, the rationale for a task (e.g. its underlying goals) and so on. We are formalizing this set of questions into what we call the query language (Klein 1989; Klein 1993), with the goal of defining a fully capable query language that will be simple enough to allow substantial automation of the exception diagnosis process, i.e. where most or all questions are answerable by software systems. We plan to take advantage of the substantial emerging body of research of ....
Klein, M. (1993). Supporting Conflict Management in Cooperative Design Teams. Journal on Group Decision and Negotiation 2: 259-278.
....handling service interacts with the problem solving agents to detect, diagnose and resolve exceptions. The query language is used to get agent state information, and the action language is used to modify it. The query language we use builds upon that developed in earlier systems (Klein 1989; Klein 1993) extending it to include queries concerning normative agent behavior models. The query language is relatively large, and we will make the effort to consolidate it into a smaller set of critical query types. The action language, in contrast, consists we have found of a relatively small set of ....
.... Contribution to Improving Agent Based Systems The ideas described in this paper have already been substantially validated through nearly a decade of development and evaluation of successful systems for resolving multi agent exceptions in the collaborative design (Klein 1989; Klein 1991; Klein 1993) and collaborative requirements capture (Klein 1997) domains. This led to the development of the basic heuristic classification approach, software tools for exception diagnosis and resolution, a substantive standardized language for communication between agents and the exception handling service, ....
[Article contains additional citation context not shown here]
Klein, M. (1993). "Supporting Conflict Management in Cooperative Design Teams." Journal on Group Decision and Negotiation 2: 259-278.
No context found.
Klein, M. Supporting Conflict Management in Cooperative Design Teams. Journal on Group Decision and Negotiation 2(1993), 259-278.
No context found.
M. Klein. Supporting conflict management in cooperative design teams. Group Decision and Negotiation 2(3):259-278, 1993.
No context found.
Klein, M., Supporting Conflict Management in Cooperative Design Teams, Proceedings of the 11th International Workshop on DAI, Glen Arbor, MI, 1992.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC