Managing inconsistent specifications
- 1 October 1998
- journal article
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Software Engineering and Methodology
- Vol. 7 (4) , 335-367
- https://doi.org/10.1145/292182.292187
Abstract
In previous work, we advocated continued development of specifications in the presence of inconsistency. To support this, we used classical logic to represent partial specifications and to identify inconsistencies between them. We now present an adaptation of classical logic, which we term quasi-classical (QC) logic, that allows continued reasoning in the presence of inconsistency. The adaptation is a weakening of classical logic that prohibits all trivial derivations, but still allows all resolvants of the assumptions to be derived. Furthermore, the connectives behave in a classical manner. We then present a development called labeled QC logic that records and tracks assumptions used in reasoning. This facilitates a logical analysis of inconsistent information. We discuss that application of labeled QC logic in the analysis of multiperspective specifications. Such specifications are developed by multiple particpants who hold overlapping, often inconsistent, views of the systems they are developing.Keywords
This publication has 26 references indexed in Scilit:
- Making inconsistency respectable: Part 2 — Meta-level handling of inconsistencyPublished by Springer Nature ,2005
- Using ViewPoints for inconsistency managementSoftware Engineering Journal, 1996
- Argumentative logics: Reasoning with classically inconsistent informationData & Knowledge Engineering, 1995
- A framework for expressing the relationships between multiple views in requirements specificationIEEE Transactions on Software Engineering, 1994
- Conjunction as compositionACM Transactions on Software Engineering and Methodology, 1993
- Consistency in software system developmentACM SIGSOFT Software Engineering Notes, 1992
- COMBINING KNOWLEDGE BASES CONSISTING OF FIRST‐ORDER THEORIESComputational Intelligence, 1992
- Proving properties of a safety-critical systemSoftware Engineering Journal, 1991
- An assumption-based TMSArtificial Intelligence, 1986
- Language features for flexible handling of exceptions in information systemsACM Transactions on Database Systems, 1985