Combining Scenario-based Requirements with Static Verification and Dynamic Testing

Abstract. Two important prerequisites for achieving high quality softwareare solid requirements engineering and systematic testing. Scenarios and usecases are gaining increased attention in requirements engineering, as meansfor eliciting, documenting and validating requirements. Scenarios may alsobe a basis for testing. This paper identifies a number of possibilities of com-bining scenario-based requirements engineering with systematic approachesfor software verification and validation. It presents outlines of strategies forutilizing scenarios created during requirements engineering as input to staticverification and dynamic testing. Special attention is given to the opportunityof (1) using prioritized scenarios for guiding inspections, (2) combining sce-narios with reliability testing, and (3) scenario elicitation through strategiescommon in testing. Several issues of further research are identified. 1. Introduction There is a general consensus on the importance of good RequirementsEngineering (RE) for achieving high quality software. It is unlikely thatpoorly understood requirements yield a software system that fits its pur-poses. Another important process component for ensuring high qualitysoftware is Verification and Validation (V&V). This paper presentsmotives for and ideas behind the use of scenarios as a common denomina-tor for both RE and V&V. The main contribution of the paper is a numberof proposals on how scenarios from RE can be combined with differentareas of V&V.Scenarios and use cases

[1]  John D. Musa,et al.  Operational profiles in software-reliability engineering , 1993, IEEE Software.

[2]  Matthias Jarke,et al.  Scenario usage in system development: a report on current practice , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[3]  Claes Wohlin,et al.  Statistical Usage Testing for Software Reliability Control , 1995, Informatica.

[4]  Björn Regnell,et al.  Improving the use case driven approach to requirements engineering , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

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

[6]  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).

[7]  C. Wohlin,et al.  User-Centred Software Engineering – A Comprehensive View of Software Development1 , 1993 .

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

[9]  Shailey Minocha,et al.  A Software Tool and Method for Scenario Generation and Use , 1997 .

[10]  Richard Bache,et al.  The effect of fault size on testing , 1997, Softw. Test. Verification Reliab..

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

[12]  Björn Regnell,et al.  A hierarchical use case model with graphical representation , 1996, Proceedings IEEE Symposium and Workshop on Engineering of Computer-Based Systems.

[13]  Ivar Jacobson,et al.  Object-Oriented Software Engineering , 1991, TOOLS.

[14]  P. Combes,et al.  MSCs to Express Service Requirements as Properties on a SDL Model , 1995 .

[15]  Joachim Karlsson,et al.  A Cost-Value Approach for Prioritizing Requirements , 1997, IEEE Softw..

[16]  Claes Wohlin,et al.  Towards integration of use case modelling and usage-based testing , 2000, J. Syst. Softw..

[17]  Mikael Lindvall A study of traceability in object-oriented systems development , 1994 .

[18]  Björn Regnell,et al.  From Requirements to Design with Use Cases - Experiences from Industrial Pilot Projects , 1997 .