Requirements 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 ...
Inconsistency is a pervasive issue in software engineering. Both general rules of inconsistency mana...
This thesis examines the issue of software evolution from a Requirements Engineering perspective. Th...
Requirements documents can contain several thousand individual requirements. They must be error-free...
Requirements specifications are often inconsistent. Inconsistencies may arise because multiple confl...
In previous work, we have advocated continued development of speci-fications in the presence of inco...
Inconsistency has been considered as one of the main classes of defects in software requirements spe...
As a class of defects in software requirements specification, inconsistency has been widely studied ...
The development of requirements specifications inevitably involves modification and evolution. To su...
The initial expression of requirements for a computer-based system is often informal and possibly va...
In this paper, we propose a method to support for resolving “inconsistencies” in a requirement speci...
Multiple viewpoints are often used in requirements engineering to facilitate traceability to stake-h...
AbstractCorrecting design decay in source code is not a trivial task. Diagnosing and subsequently co...
Correcting design decay in source code is not a trivial task. Diagnosing and subsequently correcting...
Abstract. During the development of system requirements, software system specifications are often in...
The process of handling inconsistencies in software requirements is an important and challenging tas...
Inconsistency is a pervasive issue in software engineering. Both general rules of inconsistency mana...
This thesis examines the issue of software evolution from a Requirements Engineering perspective. Th...
Requirements documents can contain several thousand individual requirements. They must be error-free...
Requirements specifications are often inconsistent. Inconsistencies may arise because multiple confl...
In previous work, we have advocated continued development of speci-fications in the presence of inco...
Inconsistency has been considered as one of the main classes of defects in software requirements spe...
As a class of defects in software requirements specification, inconsistency has been widely studied ...
The development of requirements specifications inevitably involves modification and evolution. To su...
The initial expression of requirements for a computer-based system is often informal and possibly va...
In this paper, we propose a method to support for resolving “inconsistencies” in a requirement speci...
Multiple viewpoints are often used in requirements engineering to facilitate traceability to stake-h...
AbstractCorrecting design decay in source code is not a trivial task. Diagnosing and subsequently co...
Correcting design decay in source code is not a trivial task. Diagnosing and subsequently correcting...
Abstract. During the development of system requirements, software system specifications are often in...
The process of handling inconsistencies in software requirements is an important and challenging tas...
Inconsistency is a pervasive issue in software engineering. Both general rules of inconsistency mana...
This thesis examines the issue of software evolution from a Requirements Engineering perspective. Th...
Requirements documents can contain several thousand individual requirements. They must be error-free...