To Be and Not to Be: On Managing Inconsistency in Software Development (1996)
| Citations: | 19 - 6 self |
BibTeX
@MISC{Nuseibeh96tobe,
author = {Bashar Nuseibeh},
title = {To Be and Not to Be: On Managing Inconsistency in Software Development},
year = {1996}
}
OpenURL
Abstract
The development of software systems involves the detection and handling of inconsistencies. These inconsistencies arise in system requirements, design specifications and, quite often, in the descriptions that form the final implemented software product. This paper presents a critical review of approaches that explicitly tolerate and manage inconsistencies, and explores different kinds of inconsistencies that arise during different stages of software development. Managing inconsistency refers not only to the detection and removal of inconsistencies, but also to activities that facilitate continued development in their presence. Such activities include procedures for controlled amelioration or avoidance of inconsistency, which in turn may require analysis and reasoning in the presence of inconsistency.







