M. Klein, Supporting conflict resolution in cooperative design systems, IEEE Transactions on Systems, Man and Cybernetics 21(6) (1991) 1379--1390.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....evidence for the validity of this claim. Early work on expert systems development revealed that it is useful to separate domainspecific problem solving and generic control knowledge [12, 13] Analogous insights were also confirmed in the domains of collaborative design conflict management [14] and in preliminary work on process exception management [15] Generic exception management strategies are easy to find [16] Some examples include: if an agent plan has failed, backtrack to a different plan for achieving the same goal . if a highly serial process is operating too slowly to ....

....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 Resolution in Cooperative Design Systems. IEEE Systems Man and Cybernetics, 1991. 21(6): p. 1379-1390.

....parallel decompositions that remove problems resulting from forced pre execution serialization. Parallel decompositions allow opportunistic collaboration. These map well to agents. This has led to a slow but steady growth in the amount of research into multi agent design systems. Examples include [Klein 1991], Kuokka et al. 1993] Lander Lesser 1991] Sycara 1990] Taleb Bendiab Oh 1993] Victor et al. 1993] Werkman Barone 1991] The study of Conflict Resolution and Negotiation is also growing. Klein s [1991] model of conflict resolution uses a hierarchy of conflicts with the most abstract ....

....growth in the amount of research into multi agent design systems. Examples include [Klein 1991] Kuokka et al. 1993] Lander Lesser 1991] Sycara 1990] Taleb Bendiab Oh 1993] Victor et al. 1993] Werkman Barone 1991] The study of Conflict Resolution and Negotiation is also growing. Klein s [1991] model of conflict resolution uses a hierarchy of conflicts with the most abstract conflicts at the top and most concrete conflicts at the leaves. A corresponding hierarchy of resolution strategies allows conflicts to be mapped to resolution strategies. Klein s agents have both design and conflict ....

Klein, M.: 1991: Supporting Conflict Resolution in Cooperative Design Systems, IEEE Transactions on Systems, Man, and Cybernetics 21(6), pp.1379-1390.

....their parameters, i.e. they have identical functions, targets and or points of view. This will prove to be useful in the design of the system, as well as interesting during the analysis of conflicts. Not all combinations of the three parameters will necessarily be meaningful. 1. 2 Previous Work Klein [Klein 1991] introduces an approach to conflict resolution based on classifying the conflict and mapping it to a specific strategy. Sycara s work (e.g. Sycara 1990] proposes methods for resolving conflicts via negotiation and is the seminal work in the area. SNEAKERS, the first SiFA system [Douglas et al. ....

Klein 1991 M. Klein. "Supporting Conflict Resolution in Cooperative Design Systems", IEEE Trans. Systems, Man & Cyb., Vol.21, No.6, Nov/Dec 1991.

....We will present research that has focused on conflict resolution and generated various models to support it. We will also present three systems that have been developed using the SiFA paradigm. Using Single Function Agents to Investigate Conflict March 29, 1995 11:12 pm 7 2. 1 Conflict Resolution Klein [Klein 1991] introduces an approach to conflict resolution based on conflict and strategy hierarchies (Figure 2 1) The first type of hierarchy consists of a tree of conflicts, the most abstract one at the top and the specialized conflicts at the bottom. If a conflict is detected, it is matched against the ....

Klein 1991 M. Klein. "Supporting Conflict Resolution in Cooperative Design Systems" in IEEE Transactions on Systems, Man, and Cybernetics, Vol. 21, No. 6, November/ December 1991.

....evidence for the validity of this claim. Early work on expert systems development revealed that it is useful to separate domain specific problem solving and generic control knowledge [14, 15] Analogous insights were also confirmed in the domains of collaborative design conflict management [16, 17] and workflow exception management [18] In our work to date we have found that every coordination protocol has its own characteristic set of domain independent exceptions, which in turn can be mapped to domain independent strategies potentially applicable for handing (anticipating and avoiding, ....

M. Klein, "Supporting Conflict Resolution in Cooperative Design Systems," IEEE Systems Man and Cybernetics, vol. 21, pp. 1379-1390, 1991.

....1995) under the GPGP (Generalized Partial Global Planning) model. Conflict resolution: Mark Klein proposed that conflict resolution information should receive first class information status in a MASD, due to the impact of this process on the final design solution. In his Cooperative Design Engine (Klein 1991), conflicts are classified in a hierarchy based on domain specificity. Each conflict type has conflict resolution advice attached to it. Whenever a conflict occurs, agents try to find the most specific node in the hierarchy matching the current situation and use the advice to instantiate their ....

M. Klein. "Supporting Conflict Resolution in Cooperative Design Systems," IEEE Trans. on Systems, Man and Cybernetics 21, 6 (Nov.-Dec. 1991): 1379-1390.

....their parameters, i.e. they have identical functions, targets and or points of view. This will prove to be useful in the design of the system, as well as interesting during the analysis of conflicts. Not all combinations of the three parameters will necessarily be meaningful. 1. 2 Previous Work Klein [Klein 1991] introduces an approach to conflict resolution based on classifying the conflict and mapping it to a specific strategy. Sycara s work (e.g. Sycara 1990] proposes methods for resolving conflicts via negotiation and is the seminal work in the area. SNEAKERS, the first SiFA system [Douglas et al. ....

Klein 1991 M. Klein. "Supporting Conflict Resolution in Cooperative Design Systems", IEEE Trans. Systems, Man & Cyb., Vol.21, No.6, Nov/Dec 1991.

.... [2, 63] in which the effect of utterances are explicitly represented and can be reasoned about by the sender in order to try and induce specific mental states in the receiver, has been used as the basis of a number of multi agent systems [53, 66] Other illustrations occur in conflict resolution [46, 47] in which resolution strategies are categorized and selected according to the desired objective and the prevailing circumstances; in persuasion and negotiation [13, 73] in which agents reason about how to induce greater cooperativeness in other community members; in the definition of hedonic ....

M. Klein, Supporting Conflict Resolution in Cooperative Design Systems, IEEE Trans. on Systems, Man and Cybernetics 21 (6) (1991) 1379-1390.

....on their actual run time situations and the nature of their conflicts, may further increase the power of the conflict resolution process. Klein s research, conflict resolution for cooperative design problems, demonstrates one approach for matching conflict situations to resolutions strategies [15]. Under Klein s approach, conflict resolution strategies are classified according to the preconditions that must hold before the strategy can be put into effect. Different classes of conflict resolution strategies form a taxonomy that includes more general classes near the top, and more specific ....

Klein, M. 1991. Supporting Conflict Resolution in Cooperative Design Systems. IEEE Transactions on systems, man, and cybernetics 21(6): 1379-1390.

....on agent adaptability. Various researchers have identified motivations for agent adaptation including the ability to respond to the failure of another agent or to a communication failure (Decker and Sycara, 1997; Tambe, 1997) to coordinate plans schedules and resolve conflict (Jennings, 1996; Klein, 1991), to balance tasks equally among agents (Fatima and Uma, 1998) to improve system performance (Glance and Huberman, 1995) and to respond to other types of uncertainty present in the environment. Agent adaptation can occur at different levels using a variety of mechanisms ranging from an ....

Klein, M. (1991) Supporting Conflict Resolution in Cooperative Design Systems. IEEE Transactions on Systems, Man, and Cybernetics 21(6): 1379-1390.

....conflict resolution. It is also possible to combine several methods in the same system. Researchers have developed conflict resolution strategies for various types of conflicts: introducing an approach to conflict resolution based on classifying the conflict and mapping it to a specific strategy (Klein 1991); resolving conflicts in resources allocation among cooperative agents (Conry, Meyer, and Lesser 1995) resolving conflicts via negotiation (Sycara 1990; Chu Carroll and Carberry 1995; Dunskus et al. 1995; Bahler, Dupont, and Bowen 1994) assisting the designer by using expert systems that offer ....

Klein, M. (1991) Supporting Conflict Resolution in Cooperative Design Systems. IEEE Trans. Systems, Man & Cyb., 21(6).

....Table 1. Evolution of Concepts for Requirements Interaction Management Before 1970 1970s 1980s 1990s Theory Codified negotiation techniques: log rolling , condition restructuring[203] Requirements Negotiation Behavior[12] 222] Negotiation experts: case based[260] rule based [130] Domain independent resolution generation[228] Strategy (Goals) Programming goals[274] Software qualities[15] Software development goal structure[20] Software quality attributes[8] Management by Objectives [49] Software metrics[86] Software quality interaction experts[20] MAUT[205] ....

.... commonly used to identify interactions, from those among system requirements, to those among lower level design or production requirements [135] However, other methods, such as heuristic conflict classification and resolution, have been used to identify and resolve undesirable design interactions[130]. Feature interaction. Detection and resolution of undesirable functional (feature) interaction is Table 2. Disciplines Influencing Requirements Interaction Management Software Development . Requirements engineering . Concurrent engineering . Quality architecting . Feature interaction ....

[Article contains additional citation context not shown here]

Klein, M., Supporting Conflict Resolution in Cooperative Design Systems, IEEE, Transactions on Systems, Man, and Cybernetics, 21 (6), November 1991, 1379-1390.

....much research over the past several years has focused on agent adaptability. Various researchers have identified motivations for agent adaptation including the ability to respond to the failure of another agent or a communication failure [17, 44] to coordinate plans and resolve conflict [29, 31] , to distribute tasks equally among agents [20] to improve system performance [23] and to respond to other types of uncertainty present in the 1 10 100 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 Degree of Autonomy Number of Decision Making Agents D True Consensus Locally Autonomous ....

M. Klein, "Supporting Conflict Resolution in Cooperative Design Systems," IEEE Transactions on Systems, Man, and Cybernetics, vol. 21(6), pp. 1379-1390, 1991.

.... systems analysts) 48] In requirements engineering, stakeholder analysis aims to derive a system description that covers all relevant interests by incorporating the varied developer, user, and other system perspectives[6] It is a technique aimed to better development through cooperative work[34], as well as better systems use through analysis of stakeholder interactions[57] Stakeholder analysis has three major subtasks: Conflict identification seeks to determine requirements whose satisfaction reduces the satisfaction of other requirements. Resolution generation seeks to ....

....in context, two streams of related research are presented: 1) methods for generating resolutions to stakeholder requirements are summarized and 2) models of stakeholder requirements and relationships. C. Related Resolution Research Methods for resolving stakeholder conflicts have developed[1] 33][34][69] However, currently there is no formal model that explicitly links requirement conflicts to automated resolution producing requirements transformations. In fact, most resolution procedures and strategies, from a variety of domains, are implicitly defined in the code of programs[1] 31] ....

[Article contains additional citation context not shown here]

Klein, M., Supporting conflict resolution in cooperative design systems, IEEE, Transactions on Systems, Man, and Cybernetics, 21 (6), November 1991, 1379-1390.

No context found.

M. Klein, Supporting conflict resolution in cooperative design systems, IEEE Transactions on Systems, Man and Cybernetics 21(6) (1991) 1379--1390.

No context found.

Klein, M. (1991). "Supporting Conflict Resolution in Cooperative Design Systems." IEEE Systems Man and Cybernetics 21(6): 1379-1390.

.... by constraining the value of module attributes, connecting module interfaces (to represent module interactions) decomposing modules into sub modules and specializing modules by refining their class (Figure 3) Specifications and attribute values are described using a constraint language [43] [24]. Mark Klein Conflict Management 7 Constrain Attribute Value Module Module Module Module Module Module Module Specialize Connect Connect Specialize Decompose Decompose Figure 3: The design refinement process. If we were designing an airplane, for example, we might decompose the ....

....as electrical, hydraulic and mechanical subsystem modules. Interactions between modules (e.g. physically connected components) are represented as connections between module interfaces. This design model is based on classical Systems Engineering work as well as AI models of artifact design [50] [24] and planning [43] These models have been applied successfully to a wide variety of domains including electrical, electronic, hydraulic and mechanical systems as well as software. All human design agents are provided with a direct manipulation WIMP (window icon menu pointer) graphical interface ....

[Article contains additional citation context not shown here]

Klein, M. Supporting Conflict Resolution in Cooperative Design Systems. IEEE Systems Man and Cybernetics 21, 6 (December 1991).

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

Klein, M. (1991). Supporting Conflict Resolution in Cooperative Design Systems. IEEE Systems Man and Cybernetics 21(6): 1379-1390.

....of this claim. Early work on expert systems development revealed that it is useful to separate domain specific problem solving and generic control knowledge (Barnett 1984; Gruber 1989) Analogous insights were also confirmed in the domains of collaborative design conflict management (Klein 1989; Klein 1991) and workflow exception management (Klein 1997) We have identified over 100 such strategies to date; in the CNET domain, some examples include: To detect agent death, periodically poll active subcontractors. Consolidate polling in order to minimize the number of are you alive messages ....

Klein, M. (1991). "Supporting Conflict Resolution in Cooperative Design Systems." IEEE Systems Man and Cybernetics 21(6): 1379-1390.

....retrieve, contrast and customize interesting examples, make distant analogies , and utilize recombinant (mix and match) design techniques. 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 [6, 7] and collaborative requirements capture [8] 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 strategies. ....

M. Klein, Supporting Conflict Resolution in Cooperative Design Systems, IEEE Transactions on Systems, Man and Cybernetics, 21(6) (1991) 1379-1390.

No context found.

K. Klein. Supporting conflicts resolution in cooperative design system. IEEE Transactions on Systems, Man and Cybernetics, 21(6):1379--1390, 1991.

No context found.

Klein, M., "Supporting Conflict Resolution in Cooperative Design Systems", IEEE Transactions on Systems, Man, and Cybernetics, Vol. 21, No. 6, pp1379-1390, Nov/Dec 1991.

No context found.

K. Klein. Supporting conflicts resolution in cooperative design system. IEEE Transactions on Systems, Man and Cybernetics, 21(6):1379--1390, 1991.

No context found.

Klein, M., Supporting conflict resolution in cooperative design systems, IEEE, Transactions on Systems, Man, and Cybernetics, 21 (6), November 1991, 1379-1390.

No context found.

M.Klein (1991) Supporting conflict resolution in cooperative design systems. IEEE Trans. Systems, Man, and Cybernetics, November/December, Vol. 21, No. 6, pp.

First 50 documents  Next 50

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