Date Added: Mar 2011
The process of handling inconsistencies in software requirements is an important and challenging task. Most often in cases where multiple stakeholders interact with the requirement analysts, inconsistent, discrepant and conflicting information is gathered that needs to be understood and interpreted properly. Recent research has suggested that despite the fact that inconsistencies are not desirable by nature, they can be tolerated in order to better understand the nature of the problem domain and the stakeholders' line of thought. With this in mind, the authors propose an argumentative approach towards handling inconsistent requirement specifications.