Scenario Networks for Software Specification and Scenario Management TR-2001-15

Scenarios are widely used to specify the desired behavior of a system, but managing the large collection of scenarios that frequently result and making a scenario-based specification complete are challenging tasks. Scenario networks address these challenges while retaining the many advantages of scenarios during software specification activities. A scenario network is a collection of scenarios that has been integrated into a single entity by the specification of the sequential and concurrent relationships among its component scenarios. The addition of these relationships specifies the larger-scale behavior that is typically missing from a collection of scenarios, and ties scenarios together in a way that either indicates no gaps in the description are present, or makes gaps obvious. Scenario networks provide procedural guidance for scenario creation and support for scenario management. Gaps in the structure of a scenario network correspond to missing or incomplete scenarios, and the closing of these gaps result in the completion of the scenario collection. A scenario network organizes the collection of its scenarios, and its structure indicates several kinds of scenario relationships, including equivalence relations dividing them into equivalence classes. These relationships address some of the challenges associated with scenario management.

[1]  Bashar Nuseibeh,et al.  Expressing the relationships between multiple views in requirements specification , 1993, ICSE '93.

[2]  Bashar Nuseibeh,et al.  Managing inconsistencies in an evolving specification , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

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

[4]  Henri Briand,et al.  An approach based on the concept of use case to produce dynamic object-oriented specifications , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[5]  Tiffany Barnes,et al.  An integrated scenario management strategy , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[6]  Shailey Minocha,et al.  Supporting Scenario-Based Requirements Engineering , 1998, IEEE Trans. Software Eng..

[7]  K. K. Sandhu,et al.  Specification and description language (SDL) , 1992 .

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

[9]  Sjouke Mauw,et al.  Message Sequence Chart (MSC) , 1996 .

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

[11]  Michel A. Reniers,et al.  High-level message sequence charts , 1997, SDL Forum.

[12]  Martín Abadi,et al.  A Theory of Objects , 1996, Monographs in Computer Science.

[13]  Matthias Jarke,et al.  Scenario Management: An Interdisciplinary Approach , 1998, Requirements Engineering.

[14]  Shailey Minocha,et al.  CREWS-SAVRE: systematic scenario generation and use , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[15]  Raymond J. A. Buhr,et al.  Use Case Maps as Architectural Entities for Complex Systems , 1998, IEEE Trans. Software Eng..

[16]  Robin Milner,et al.  Communication and concurrency , 1989, PHI Series in computer science.

[17]  R. J. A. Buhr,et al.  Use Case Maps for Object-Oriented Systems , 1995 .

[18]  Shane Sendall,et al.  From Use Cases to System Operation Specifications , 2000, UML.

[19]  L. Finneran,et al.  Experience applying the CoRE method to the Lockheed C-130J software requirements , 1994, Proceedings of COMPASS'94 - 1994 IEEE 9th Annual Conference on Computer Assurance.

[20]  G. L. Coleman,et al.  Experience in modeling a concurrent software system using STATEMATE , 1990, COMPEURO'90: Proceedings of the 1990 IEEE International Conference on Computer Systems and Software Engineering@m_Systems Engineering Aspects of Complex Computerized Systems.

[21]  Rolv Bræk SDL Basics , 1996, Comput. Networks ISDN Syst..

[22]  Annie I. Antón,et al.  Scenario Networks: A Case Study of the Enhanced Messaging System , 2001 .

[23]  Rance Cleaveland,et al.  The concurrency workbench: a semantics-based tool for the verification of concurrent systems , 1993, TOPL.

[24]  Pierre America,et al.  Inheritance and Subtyping in a Parallel Object-Oriented Language , 1987, ECOOP.

[25]  Marc Frappier,et al.  Integration of Sequential Scenarios , 1998, IEEE Trans. Software Eng..

[26]  Colette Rolland,et al.  Guiding the Construction of Textual Use Case Specifications , 1998, Data Knowl. Eng..

[27]  Ekkart Rudolph,et al.  Tutorial on Message Sequence Charts , 1996, Comput. Networks ISDN Syst..

[28]  Colette Rolland,et al.  Guiding Goal Modeling Using Scenarios , 1998, IEEE Trans. Software Eng..

[29]  William Pugh,et al.  The Omega test: A fast and practical integer programming algorithm for dependence analysis , 1991, Proceedings of the 1991 ACM/IEEE Conference on Supercomputing (Supercomputing '91).

[30]  Annie I. Antón,et al.  The use of goals to surface requirements for evolving systems , 1998, Proceedings of the 20th International Conference on Software Engineering.

[31]  Anthony J. H. Simons,et al.  Use cases considered harmful , 1999, Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275).

[32]  David Harel,et al.  Statecharts: A Visual Formalism for Complex Systems , 1987, Sci. Comput. Program..

[33]  Amnon Naamad,et al.  The STATEMATE semantics of statecharts , 1996, TSEM.

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

[35]  Annie I. Antón,et al.  Goal Decomposition and Scenario Analysis in Business Process Reengineering , 1994, CAiSE.

[36]  Daniel Amyot,et al.  Use case maps for the capture and validation of distributed systems requirements , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[37]  Roel Wieringa,et al.  A survey of structured and object-oriented software specification methods and techniques , 1998, CSUR.

[38]  James L. Peterson,et al.  Petri Nets , 1977, CSUR.