Is it vacuous to check redundancy, or is it redundant to check vacuity?

Elisabeth Henkel et al.

Requirements Engineering2025https://doi.org/10.1007/s00766-025-00438-5article
AJG 2
Weight
0.50

What the paper says

We present an automatic method to detect the existence of redundant requirements. A requirement is redundant if it does not represent an additional restriction on the intended behaviour of the specified system. If unintended, a redundancy may hint at a defect. The method applies to real-time requirements formalized in a particular kind of real-time logic formalism. The method uses techniques derived from real-time model checking. In particular, we use Phase Event Automata, a variant of timed automata. We introduce a novel determinism-preserving totalisation procedure for Phase Event Automata for the purpose of the automata-theoretic operation of complementation. The method is complete in the sense that it detects every redundancy in a given set of requirements. We have implemented the method. Preliminary experiments on industrial benchmarks indicate its scalability and its usefulness for discovering previously unknown defects. In spirit, redundancy is closely related to the property of vacuity. We show, however, that checking redundancy does not make checking vacuity redundant, and vice versa. This means that none of the two checks is superseeded by the other one. This article is the extension of a previous conference paper.

Open paper page →

Cite this paper

https://doi.org/https://doi.org/10.1007/s00766-025-00438-5

Or copy a formatted citation

@article{elisabeth2025,
  title        = {{Is it vacuous to check redundancy, or is it redundant to check vacuity?}},
  author       = {Elisabeth Henkel et al.},
  journal      = {Requirements Engineering},
  year         = {2025},
  doi          = {https://doi.org/https://doi.org/10.1007/s00766-025-00438-5},
}

Paste directly into BibTeX, Zotero, or your reference manager.

Flag this paper

Is it vacuous to check redundancy, or is it redundant to check vacuity?

Flags are reviewed by the Arbiter methodology team within 5 business days.


Evidence weight

0.50

Balanced mode · F 0.40 / M 0.15 / V 0.05 / R 0.40

F · citation impact0.50 × 0.4 = 0.20
M · momentum0.50 × 0.15 = 0.07
V · venue signal0.50 × 0.05 = 0.03
R · text relevance †0.50 × 0.4 = 0.20

† Text relevance is estimated at 0.50 on the detail page — for your query’s actual relevance score, open this paper from a search result.