Supporting scenario evolution

Authors:
Koogan Breitman;Prado Leite;M. Berry
Affiliations:
Departamento de Informática, Pontifícia Universidade Católica, 22453, Rio de Janeiro, RJ, Brazil;Departamento de Informática, Pontifícia Universidade Católica, 22453, Rio de Janeiro, RJ, Brazil;Computer Science Department, University of Waterloo, Computer Science Department, 22453, Waterloo, ON, Canada
Venue:
Requirements Engineering
Year:
2005

Citing 0
Cited 3

Scenario support for effective requirements

Information and Software Technology
Athena: A collaborative approach to requirements elicitation

Computers in Industry
Non-functional user interface requirements notation (NfRn) for modeling the global execution context of tasks

TAMODIA'06 Proceedings of the 5th international conference on Task models and diagrams for users interface design

Quantified Score

Hi-index	0.00

Visualization

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.