文档介绍：Managing Inconsistencies in an Evolving Specification Steve Easterbrook Bashar Nuseibeh School of Cognitive puting Sciences, Department puting, Imperial College University of Sussex, Brighton, BN1 9QH, UK. 180 Queen’s Gate, London, SW7 2BZ, UK.******@ ******@ Abstract In an evolving specification, considerable effort is spent handling recurrent inconsistencies. Detecting and resolving inconsistencies is only part of the problem: a resolved inconsistency might not stay resolved. Frameworks in which inconsistency is tolerated help by allowing resolu- tion to be delayed. However, evolution of a specification may affect both resolved and unresolved inconsistencies. We address these problems by explicitly recording relationships between partial specifications (ViewPoints), representing both resolved and unresolved inconsistencies. We assume that ViewPoints will often be inconsistent with one another, and we ensure that plete work record is kept, detailing any inconsistencies that have been detected, and what actions, if any, have been taken to resolve them. The work record is then used to reason about the effects of subsequent changes to ViewPoints, without constraining the development process. 1 . Introduction In an evolving specification, considerable development time and effort is spent handling recurrent inconsistencies. Such inconsistencies are particularly prevalent during requirements engineering, when conflicting and contra- dictory objectives are often required by different stake- holders. Tools and techniques for detecting and resolving inconsistencies only address part of the problem: they do not ensure that a resolution generated at a particular stage will apply at all subsequent stages of the process. In this paper, we propose an approach for managing inconsistencies that arise during the development of multi- perspective specifications, by explicitly recording consistency relationships between partial specifications, and by