China
Africa
Explore chapters and articles related to this topic
A Knowledge-based Mesh Generation System for Forging Simulation
Published in Takushi Tanaka, Setsuo Ohsuga, Moonis Ali, Industrial and Engineering Applications of Artificial Intelligence and Expert Systems, 2022
Osamu Takata, Koukichi Nakanishi, Nariaki Horinouchi, Hiroshi Yano, Tadao Akashi, Toyohide Watanabe
In the knowledge-based system (production system), the conflict resolution strategy is an important task. It is necessary to apply a rule to working memories at the same time and also to prefer the best N ones which are specified in rules, because GENMAI generates the best N patterns in each basic region at the same time. It is difficult for a simple conflict resolution strategy such as MEA and LEX to control these complicated ones [Ric83]. Therefore, GENMAI provides 7 conflict resolution strategies shown in Table 1.These strategies are specified in meta-rule by the predicate “inference_engine” as shown below. inference_engine(strategy, rule-set, world, instances)
Production Systems
Published in Konar Amit, Artificial Intelligence and Soft Computing, 2018
A production system with conflict resolution strategy selects only one rule at each recognize-act cycle for firing. Thus the fired rules are virtually time-tagged. Since the rules cause state-transition in a production system, stating the rule to the user during its firing, let the user understand the significance of the state transition. Presenting the set of the time-tagged rule in sequence thus gives the user an explanation of the sequence of the operators used to reach the goal.
Complementary and Substitutive Roles of Information Technology in the Relationship between Project Characteristics and Knowledge Integration in Software Teams
Published in Information Systems Management, 2023
Nikhil Mehta, Eric Jack, Randy Bradley, Sumedha Chauhan
This contributes positively to a team’s internal knowledge integration in two ways. First, having a conflict resolution strategy in place prevents everyday conflicts from disrupting a software team’s critical activities, such as internal knowledge integration, enabling the team to focus its valuable time and resources to perform these activities effectively (Xie et al., 2014). Second, having a “cooperative” approach to resolving resource-sharing conflicts with other codependent entities enables a software team to protect its valuable knowledge resources, such as team members, from being misused by other codependent teams. This facilitates the effective utilization of the team’s knowledge resources for project-critical activities such as internal knowledge integration. Overall, we propose: Hypothesis 2 (H2): Project interdependence is positively associated with team knowledge integration.