Using Abduction to Evolve Inconsistent Requirements Specification
Keywords: requirement engineering, abduction, specification, consistency
AbstractRequirements specifications are often inconsistent. Inconsistencies may arise because multiple conflicting requirements are embodied in these specifications, or because the specifications themselves are in a transient stage of evolutionary development. In this paper we argue that such inconsistencies, rather than being undesirable, are actually useful drivers for changing the requirements specifications in which they arise. We present a formal technique to reason about inconsistency handling changes. Our technique is an adaptation of logical abduction - adapted to generate changes that address some specification inconsistencies, while leaving others. We represent our specifications in quasi-classical (QC) logic - an adaptation of classical logic that allows continued reasoning in the presence of inconsistency. The paper develops a sound algorithm for automating our abductive reasoning technique and presents illustrative examples drawn from a library system case study.
How to Cite
Nuseibeh, B., & Russo, A. (1). Using Abduction to Evolve Inconsistent Requirements Specification. Australasian Journal of Information Systems, 6(2). https://doi.org/10.3127/ajis.v6i2.296
Copyright (c) 1969 Bashar Nuseibeh, Alessandra Russo
This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.
AJIS publishes open-access articles distributed under the terms of a Creative Commons Non-Commercial and Attribution License which permits non-commercial use, distribution, and reproduction in any medium, provided the original author and AJIS are credited. All other rights including granting permissions beyond those in the above license remain the property of the author(s).