Managing Inconsistent Specifications: Reasoning, Analysis, and Action.
ACM Transactions on Software Engineering and Methodology
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 the application of labeled QC logic in the analysis of multiperspective specifications. Such specifications are developed by multiple participants who hold overlapping, often inconsistent, views of the systems they are developing.
|Title:||Managing Inconsistent Specifications: Reasoning, Analysis, and Action|
|Keywords:||D.2 [Software]: Software Engineering, D.2.1 [Software Engineering]: Requirements/Specifications - languages, D.2.2 [Software Engineering]: Tools and Techniques - computer-aided software engineering (CASE)|
|UCL classification:||UCL > School of BEAMS > Faculty of Engineering Science
UCL > School of BEAMS > Faculty of Engineering Science > Computer Science
Archive Staff Only