From inconsistency handling to non-canonical requirements management: A logical perspective

  • Authors:

  • Kedian Mu;Jun Hong;Zhi Jin;Weiru Liu

  • Affiliations:

  • School of Mathematical Sciences, Peking University, Beijing 100871, PR China;School of Electronics, Electrical Engineering and Computer Science, Queen's University Belfast, BT7 1NN, UK;Key Laboratory of High Confidence Software Technologies (Peking University), Ministry of Education, School of Electronics Engineering and Computer Science, Peking University, Beijing 100871, PR Ch ...;School of Electronics, Electrical Engineering and Computer Science, Queen's University Belfast, BT7 1NN, UK

  • Venue:
  • International Journal of Approximate Reasoning
  • Year:
  • 2013

Quantified Score

Hi-index 0.00

Visualization

Abstract

As a class of defects in software requirements specification, inconsistency has been widely studied in both requirements engineering and software engineering. It has been increasingly recognized that maintaining consistency alone often results in some other types of non-canonical requirements, including incompleteness of a requirements specification, vague requirements statements, and redundant requirements statements. It is therefore desirable for inconsistency handling to take into account the related non-canonical requirements in requirements engineering. To address this issue, we propose an intuitive generalization of logical techniques for handling inconsistency to those that are suitable for managing non-canonical requirements, which deals with incompleteness and redundancy, in addition to inconsistency. We first argue that measuring non-canonical requirements plays a crucial role in handling them effectively. We then present a measure-driven logic framework for managing non-canonical requirements. The framework consists of five main parts, identifying non-canonical requirements, measuring them, generating candidate proposals for handling them, choosing commonly acceptable proposals, and revising them according to the chosen proposals. This generalization can be considered as an attempt to handle non-canonical requirements along with logic-based inconsistency handling in requirements engineering.