Abstract Scenarios have been shown to be very helpful in identifying and communicating requirements for computer-based systems (CBSs). However, they appear not to be applicable to the rest of the CBS development process. Making scenarios more useful for the entire software development lifecycle requires integrating scenarios to other representations used during CBS development. This integration is achieved with tracing technology. Having integrated scenarios into the entire software development lifecycle creates the necessity to maintain scenarios through the inevitable changes that they and other documents undergo and to subject them to configuration management. We have prototyped automated support for full-lifecycle scenario management and have applied it to some non-trivial systems.
This paper is an amalgamation and extension of the conference papers numbered 8, 9, 10, and 11 in the bibliography of this paper.
%0 Journal Article
%1 breitman05
%A Breitman, Karin Koogan
%A do Prado Leite, Julio Cesar Sampaio
%A Berry, Daniel M.
%D 2005
%J Requirements Engineering
%K evolution scenario
%N 2
%P 112-131
%T Supporting scenario evolution
%U http://dx.doi.org/10.1007/s00766-004-0199-z
%V 10
%X Abstract Scenarios have been shown to be very helpful in identifying and communicating requirements for computer-based systems (CBSs). However, they appear not to be applicable to the rest of the CBS development process. Making scenarios more useful for the entire software development lifecycle requires integrating scenarios to other representations used during CBS development. This integration is achieved with tracing technology. Having integrated scenarios into the entire software development lifecycle creates the necessity to maintain scenarios through the inevitable changes that they and other documents undergo and to subject them to configuration management. We have prototyped automated support for full-lifecycle scenario management and have applied it to some non-trivial systems.
This paper is an amalgamation and extension of the conference papers numbered 8, 9, 10, and 11 in the bibliography of this paper.
@article{breitman05,
abstract = {Abstract Scenarios have been shown to be very helpful in identifying and communicating requirements for computer-based systems (CBSs). However, they appear not to be applicable to the rest of the CBS development process. Making scenarios more useful for the entire software development lifecycle requires integrating scenarios to other representations used during CBS development. This integration is achieved with tracing technology. Having integrated scenarios into the entire software development lifecycle creates the necessity to maintain scenarios through the inevitable changes that they and other documents undergo and to subject them to configuration management. We have prototyped automated support for full-lifecycle scenario management and have applied it to some non-trivial systems.
This paper is an amalgamation and extension of the conference papers numbered 8, 9, 10, and 11 in the bibliography of this paper.},
added-at = {2006-09-25T05:51:57.000+0200},
author = {Breitman, Karin Koogan and do Prado Leite, Julio Cesar Sampaio and Berry, Daniel M.},
biburl = {https://www.bibsonomy.org/bibtex/2208316826085517ee972ba39c289068c/neilernst},
interhash = {30c6660d12ded49925e2f5faf9dfc7a0},
intrahash = {208316826085517ee972ba39c289068c},
journal = {Requirements Engineering},
keywords = {evolution scenario},
number = 2,
pages = {112-131},
timestamp = {2006-09-25T05:51:57.000+0200},
title = {Supporting scenario evolution},
url = {http://dx.doi.org/10.1007/s00766-004-0199-z},
volume = 10,
year = 2005
}