Requirement Conflict Restructuring

Requirements engineering necessitates the analysis of relationships among the requirements of system stakeholders. Poor analysis of these relationships has led to numerous failures. To improve such analysis, researchers have created models and methods for recording, analyzing, and modifying stakeholder requirements. However, the critical aspect of resolving conflicts among stakeholder requirements remains relatively implicit. Herein, we explicitly define: (1) an ontology for capturing stakeholder requirements, (2) restructuring transformations that generate alternative requirements that remove stakeholder conflicts, and (3) a strategy for guiding the resolution generation process. To validate the utility of our approach, we have applied it to the analysis of a distributed meeting scheduler. We conclude that good quality resolutions and substantial automated support can be had through a transformation approach to removing requirement conflicts.

[1]  Victor Lesser,et al.  Multistage negotiation in distributed planning , 1988 .

[2]  Thomas G. Dietterich.  What is machine learning? , 2020, Archives of Disease in Childhood.

[3]  Hugo Velthuijsen.  Distributed artificial intelligence for runtime feature-interaction resolution , 1993, Computer.

[4]  A. Marty.  Getting to YES. Negotiating Agreement Without Giving In , 1983 .

[5]  Victor R. Lesser,et al.  Understanding the Role of Negotiation in Distributed Search Among Heterogereous Agents , 1993, IJCAI.

[6]  Arthur M. Farley,et al.  Plan Abstraction Based on Operator Generalization , 1988, AAAI.

[7]  William N. Robinson,et al.  Electronic brokering for assisted contracting of software applets , 1997, Proceedings of the Thirtieth Hawaii International Conference on System Sciences.

[8]  Stefano Spaccapietra,et al.  View Integration: A Step Forward in Solving Structural Conflicts , 1994, IEEE Trans. Knowl. Data Eng..

[9]  Aris M. Ouksel,et al.  A classification of semantic conflicts in heterogeneous database systems , 1995, J. Organ. Comput..

[10]  Eric S. K. Yu,et al.  Using non-functional requirements to systematically support change , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[11]  Tawfik Jelassi,et al.  Negotiation support systems: an overview of design issues and existing software , 1989, Decis. Support Syst..

[12]  Mehdi T. Harandi,et al.  Workshop on software specification and design , 1988, SOEN.

[13]  William N. Robinson,et al.  Surfacing root requirements interactions from inquiry cycle requirements documents , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[14]  Michael Heym,et al.  Computer-aided methodology engineering , 1993, Inf. Softw. Technol..

[15]  William N. Robinson.  Interactive Decision Support for Requirements Negotiation , 1994 .

[16]  William N. Robinson,et al.  Managing Requirements Inconsistency with Development Goal Monitors , 1999, IEEE Trans. Software Eng..

[17]  H. Raiffa,et al.  Decisions with Multiple Objectives , 1993 .

[18]  William N. Robinson,et al.  Supporting multi-perspective requirements engineering , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[19]  Enid Mumford,et al.  Computer systems in work design--the ETHICS method : effective technical and human implementation of computer systems , 1979 .

[20]  I. Janis,et al.  Decision Making: A Psychological Analysis of Conflict, Choice, and Commitment , 1977 .

[21]  Eric Bennett Rasmusen,et al.  A Model of Negotiation, Not Bargaining , 1995 .

[22]  Barry W. Boehm,et al.  Identifying Quality-Requirement Conflicts , 1996, IEEE Softw..

[23]  Bashar Nuseibeh,et al.  Coordinating distributed ViewPoints: the Anatomy of a Consistency Check , 1994 .

[24]  Melvin F. Shakun,et al.  Airline Buyout: Evolutionary Systems Design and Problem Restructuring in Group Decision and Negotiation , 1991 .

[25]  Kuldeep Kumar,et al.  Methodology Engineering R : a proposal for situation-specific methodology construction , 1992 .

[26]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[27]  Vasant Dhar,et al.  Supporting Systems Development by Capturing Deliberations During Requirements Engineering , 1992, IEEE Trans. Software Eng..

[28]  Paolo Atzeni,et al.  A metamodel approach for the management of multiple models and translation of schemes , 1993, Inf. Syst..

[29]  Philippe Massonet,et al.  Goal-directed elaboration of requirements for a meeting scheduler: problems and lessons learnt , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[30]  Mark Klein,et al.  Supporting conflict resolution in cooperative design systems , 1991, IEEE Trans. Syst. Man Cybern..

[31]  Michael J. Muller,et al.  Participatory design , 1993, CACM.

[32]  Frank von Martial.  Coordinating Plans of Autonomous Agents , 1992, Lecture Notes in Computer Science.

[33]  Marc Roubens,et al.  Multiple criteria decision making , 1994 .

[34]  Jack Minker,et al.  Logic and Databases: A 20 Year Retrospective , 1996, Logic in Databases.

[35]  Matthias Jarke,et al.  Managing Multiple Requirements Perspectives with Metamodels , 1996, IEEE Softw..

[36]  Andrew Kusiak,et al.  Concurrent Engineering: Automation, Tools, and Techniques , 1992 .

[37]  W. N. Robinson,et al.  Integrating multiple specifications using domain goals , 1989, IWSSD '89.

[38]  Dov M. Gabbay,et al.  Inconsistency Handling in Multi-Perspective Specifications , 1993, ESEC.

[39]  Gregory R. Olsen,et al.  Collaborative Engineering Based on Knowledge Sharing Agreements , 1995 .

[40]  Robert Weihmayer,et al.  Conflict-resolution Strategies for Nonhierarchical Distributed Agents , 1989, Distributed Artificial Intelligence.

[41]  Matthias Jarke,et al.  Logic Programming and Databases , 1984, Expert Database Workshop.

[42]  L. Festinger.  Conflict, Decision, and Dissonance , 1964 .

[43]  William N. Robinson,et al.  Supporting the negotiation life cycle , 1998, CACM.

[44]  Steve M. Easterbrook,et al.  Using ViewPoints for inconsistency management , 1996, Softw. Eng. J..

[45]  Axel van Lamsweerde,et al.  Formal refinement patterns for goal-driven requirements elaboration , 1996, SIGSOFT '96.

[46]  Stan Matwin,et al.  Negoplan: an expert system shell for negotiation support , 1989, IEEE Expert.

[47]  Gregory E. Kersten,et al.  Negotiation in distributed artificial intelligence: drawing from human experience , 1994, 1994 Proceedings of the Twenty-Seventh Hawaii International Conference on System Sciences.

[48]  William N. Robinson,et al.  Negotiation behavior during requirement specification , 1990, [1990] Proceedings. 12th International Conference on Software Engineering.

[49]  M. Lynne Markus,et al.  If we build it, they will come: Designing information systems that people want to use , 1994 .

[50]  Douglas B. Lenat,et al.  Why AM and EURISKO Appear to Work , 1984, Artif. Intell..

[51]  Stephen Fickas,et al.  Knowledge Representation and Reasoning in the Design of Composite Systems , 1992, IEEE Trans. Software Eng..

[52]  Peter Checkland,et al.  Systems Thinking, Systems Practice , 1981 .

[53]  Jeffrey S. Rosenschein and Gilad Zlotkin.  Rules of Encounter , 1994 .

[54]  John Mylopoulos,et al.  On formal requirements modeling languages: RML revisited , 1994, Proceedings of 16th International Conference on Software Engineering.

[55]  Stephen Fickas.  Supporting the programmer of a rule based language , 1987 .

[56]  Bruce G. Buchanan,et al.  The MYCIN Experiments of the Stanford Heuristic Programming Project , 1985 .