A logic for reasoning with inconsistency
Journal of Automated Reasoning
Managing inconsistent specifications: reasoning, analysis, and action
ACM Transactions on Software Engineering and Methodology (TOSEM)
Handling Obstacles in Goal-Oriented Requirements Engineering
IEEE Transactions on Software Engineering - special section on current trends in exception handling—part II
A framework for multi-valued reasoning over inconsistent viewpoints
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
2nd international workshop on living with inconsistency (IWLWI01)
ACM SIGSOFT Software Engineering Notes
Reconciling requirements: a method for managing interference, inconsistency and conflict
Annals of Software Engineering
A Formal Framework for Viewpoint Consistency
Formal Methods in System Design
Efficient Multiple-Valued Model-Checking Using Lattice Representations
CONCUR '01 Proceedings of the 12th International Conference on Concurrency Theory
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
Verifying Software Requirements Based on Answer Set Programming
KSEM '09 Proceedings of the 3rd International Conference on Knowledge Science, Engineering and Management
Hi-index | 0.00 |
It seems to be inevitable to confront vague information about customer’s needs during the software requirements stage. It may be desirable to record and clarify the vague information to avoid missing real requirements. In this paper, we provide an inconsistency-based strategy to handle vague information in the framework of Annotated Predicate Calculus. This strategy permits the stakeholder to describe the different vague information using statements with different levels of belief, where each level of belief is determined by the degree of vagueness. By checking consistency of the union of vague requirements and clear requirements, we then heighten the level of belief in uncontroversial vague requirements. We also lower the levels of belief in requirements involved in undesirable inferences and leave them to be articulated in some following stage. To support this, Annotated Predicate Calculus is used to represent the requirements specification. In particular, we present a special belief semilattice, which defines truth values appropriate for representing the strength of analyst’s belief in the truth of requirements statements.