On the logic of iterated belief revision
Artificial Intelligence
Managing inconsistent specifications: reasoning, analysis, and action
ACM Transactions on Software Engineering and Methodology (TOSEM)
Software Development
Machine Learning
A Cost-Value Approach for Prioritizing Requirements
IEEE Software
A Requirements Engineering Process Model Based on Defaults and Revisions
DEXA '00 Proceedings of the 11th International Workshop on Database and Expert Systems Applications
A Logical Framework for Modeling and Reasoning About the Evolution of Requirements
RE '97 Proceedings of the 3rd IEEE International Symposium on Requirements Engineering
Software Requirements
An Analysis-Revision Cycle to Evolve Requirements Specifications
Proceedings of the 16th IEEE international conference on Automated software engineering
A negotiation-style framework for non-prioritised revision
TARK '01 Proceedings of the 8th conference on Theoretical aspects of rationality and knowledge
Reasoning about inconsistencies in natural language requirements
ACM Transactions on Software Engineering and Methodology (TOSEM)
Just Enough Requirements Management: Where Software Development Meets Marketing
Just Enough Requirements Management: Where Software Development Meets Marketing
Iterated belief revision, revised
Artificial Intelligence
Identifying Acceptable Common Proposals for Handling Inconsistent Software Requirements
FORTE '07 Proceedings of the 27th IFIP WG 6.1 international conference on Formal Techniques for Networked and Distributed Systems
Inconsistency management and prioritized syntax-based entailment
IJCAI'93 Proceedings of the 13th international joint conference on Artifical intelligence - Volume 1
Hi-index | 0.00 |
For any proposed software project, when the software requirements specification has been established, requirements changes may result in not only a modification of the requirements specification but also a series of modifications of all existing artifacts during the development. Then it is necessary to provide effective and flexible requirements changes management. In this paper, we present an approach to managing requirements changes based on Booth's negotiation-style framework for belief revision. Informally, we consider the current requirements specification as a belief set about the system-to-be. The request of requirements change is viewed as new information about the same system-to-be. Then the process of executing the requirements change is a process of revising beliefs about the system-to-be. We design a family of belief negotiation models appropriate for different processes of requirements revision, including the setting of the request of requirements change being fully accepted, the setting of the current requirements specification being fully preserved, and that of the current specification and the request of requirements change reaching a compromise. In particular, the prioritization of requirements plays an important role in reaching an agreement in each belief negotiation model designed in this paper.