Enhancing a requirements baseline with scenarios

Scenarios are well recognized as an important strategy towards understanding the interface between the environment and the system, as well as a means to elicit and specify software behavior. We have a broader understanding of scenarios: for us, a scenario is an evolving description of situations in the environment. Our proposal is framed by Leite's (1995) work on a client-oriented requirements baseline, which aims at modeling the external requirements of a software system and its evolution. Scenarios start by describing the environmental situation, according to the main actions performed outside the software system. Scenarios also help the clarification of the interrelation between functional and non-functional requirements. We have validated our strategy and related representations based on case studies of a real situation.

[1]  Lorna A. Zorman.  Requirements Envisaging by Utilizing Scenarios (REBUS). , 1995 .

[2]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[3]  Gustavo Rossi,et al.  The object-oriented hypermedia design model , 1995, CACM.

[4]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[5]  Kenneth S. Rubin.  Object behavior analysis , 1992, CACM.

[6]  Klaus Pohl,et al.  PRO-ART * : Enabling Requirements Pre-Traceability 1 , 1996 .

[7]  S. M. Deen.  Fundamentals of Data Base Systems , 1977, Macmillan Computer Science Series.

[8]  Stewart A. Higgins,et al.  Scenarios-an industrial case study and hypermedia enhancements , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[9]  David Lorge Parnas,et al.  A Rational Design Process: How and Why to Fake It , 1985, TAPSOFT, Vol.2.

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