Scenario-based software process

Scenarios are becoming ubiquitous artefacts in software development. Many researchers view scenarios as the product of the collaboration among developers and users during the requirements definition stage. We believe scenarios should be used in a wider scope, covering the whole development process. In this light, scenarios would be produced at different stages and, like other artefacts, would be in constant evolution. In order to support the scenario evolutionary process and aid the migration between stages, springs the need for a scenario-based software process. Recent research evidenced that the process dimension of scenarios is seldom considered in the literature. In this paper we propose a scenario-based process framework to support the evolution of scenarios. The framework relies on a set of scenario operations/relationships described previously and incorporates configuration management techniques.

[1]  Gustavo Rossi,et al.  Enhancing a requirements baseline with scenarios , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[2]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[3]  Matthias Jarke,et al.  Scenarios in System Development: Current Practice , 1998, IEEE Softw..

[4]  Karin K. Breitman,et al.  A framework for scenario evolution , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[5]  John Karat,et al.  Raison d'Etre: capturing design history and rationale in mutimedia narratives , 1994, CHI Conference Companion.

[6]  Morten Kyng,et al.  Creating contexts for design , 1995 .

[7]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[8]  David Chenho Kung,et al.  Formal approach to scenario analysis , 1994, IEEE Software.

[9]  Janusz Zalewski,et al.  Object-oriented software engineering. A use case driven approach , 1993 .

[10]  Julio Cesar Sampaio do Prado Leite,et al.  A client oriented requirements baseline , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[11]  Axel van Lamsweerde,et al.  Managing Conflicts in Goal-Driven Requirements Engineering , 1998, IEEE Trans. Software Eng..

[12]  Mary Beth Rosson,et al.  Narrowing the specification-implementation gap in scenario-based design , 1995 .

[13]  Alistair G. Sutcliffe,et al.  Requirements rationales: integrating approaches to requirement analysis , 1995, Symposium on Designing Interactive Systems.