Pushing Requirements Changes through to Changes in Specifications

Requirements changes can occur both during and after a phase of development. It is difficult and intensive work to integrate requirements changes made after specification is completed. Sequence-based specification was developed to convert ordinary functional requirements into complete, consistent, a...

Full description

Saved in:
Bibliographic Details
Published in2008 2nd IFIP/IEEE International Symposium on Theoretical Aspects of Software Engineering pp. 289 - 296
Main Authors Lan Lin, Poore, J.H.
Format Conference Proceeding
LanguageEnglish
Published IEEE 01.06.2008
Subjects
Online AccessGet full text

Cover

Loading…
More Information
Summary:Requirements changes can occur both during and after a phase of development. It is difficult and intensive work to integrate requirements changes made after specification is completed. Sequence-based specification was developed to convert ordinary functional requirements into complete, consistent, and traceably correct specifications through a constructive process. Algorithms for managing requirements changes meet a very great need in field application of the sequence-based specification method. In this paper we propose to capture requirements changes as a series of atomic changes in specifications, and present algorithms for managing these changes. The algorithms are built into the tool support with which users are able to push requirements changes through to changes in specifications, maintain old specifications over time and evolve them into new specifications with the least amount of human interaction and rework. All our change algorithms are supported by rigorous mathematical formulation and proof of correctness.
ISBN:0769532497
9780769532493
DOI:10.1109/TASE.2008.16