Scenario support for effective requirements

Scenarios are widely used as requirements, and the quality of requirements is an important factor in the efficiency and success of a development project. The informal nature of scenarios requires that analysts do much manual work with them, and much tedious and detailed effort is needed to make a collection of scenarios well-defined, relatively complete, minimal, and coherent. We discuss six aspects of scenarios having inherent structure on which automated support may be based, and the results of using such support. This automated support frees analysts to concentrate on tasks requiring human intelligence, resulting in higher-quality scenarios for better system requirements. Two studies validating the work are presented.

[1]  Elisa Bertino,et al.  An Approach to Classify Semi-structured Objects , 1999, ECOOP.

[2]  Neil Maiden,et al.  Scenarios, Stories, Use Cases: Through the Systems Development Life-Cycle , 2004 .

[3]  Alistair G. Sutcliffe,et al.  Scenario-based requirements engineering , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[4]  Mordechai Ben-Menachem,et al.  Writing effective use cases , 2001, SOEN.

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

[6]  J. Kruskal An Overview of Sequence Comparison: Time Warps, String Edits, and Macromolecules , 1983 .

[7]  Colin Potts,et al.  Software-engineering research revisited , 1993, IEEE Software.

[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]  S. Uchitel,et al.  Monitoring and control in scenario-based requirements analysis , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..

[10]  Barry Boehm,et al.  Top 10 list [software development] , 2001 .

[11]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[12]  Ana I. Anton,et al.  Goal identification and refinement in the specification of software-based information systems , 1997 .

[13]  Brian Mathews,et al.  Matching conceptual graphs as an aid to requirements re-use , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

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

[15]  Laura J. Bode A Scenario Management Case Study: Measuring Scenario Similarity in the EMS , 2002 .

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

[17]  Alan M. Davis,et al.  Software requirements - analysis and specification , 1990 .

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

[19]  Alan M. Davis,et al.  The missing piece of software development , 2000, J. Syst. Softw..

[20]  Didar Zowghi,et al.  The Three Cs of Requirements : Consistency , Completeness , and Correctness , 2002 .

[21]  Björn Regnell,et al.  Evaluating automated support for requirements similarity analysis in market-driven development , 2001 .

[22]  James F. Allen Maintaining knowledge about temporal intervals , 1983, CACM.

[23]  Thomas A. Alspaugh,et al.  Scenario-driven Specification-based Testing against Goals and Requirements , 2005 .

[24]  Thomas A. Alspaugh,et al.  Relationships Between Scenarios , 2006 .

[25]  Laura @ Bodeonline An Empirical Study of Scenario Similarity Measures , 2003 .

[26]  Daniela E. Damian,et al.  Requirements Engineering and Downstream Software Development: Findings from a Case Study , 2005, Empirical Software Engineering.

[27]  Martin S. Feather,et al.  Utilizing Scenarios in the Software Development Process , 1993, Information System Development Process.

[28]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[29]  Aldo Dagnino,et al.  Deriving Goals from a Use-Case Based Requirements Specification , 2001, Requirements Engineering.

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

[31]  Neil A. M. Maiden,et al.  Analogical retrieval in reuse-oriented requirements engineering , 1996, Softw. Eng. J..

[32]  Philippe Massonet,et al.  Analogical reuse of requirements frameworks , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[33]  Thomas Rose,et al.  Task-oriented and similarity-based retrieval , 1994, Proceedings KBSE '94. Ninth Knowledge-Based Software Engineering Conference.

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

[35]  Neil A. M. Maiden,et al.  CREWS-SAVRE: Scenarios for Acquiring and Validating Requirements , 1998, Automated Software Engineering.

[36]  Barry W. Boehm,et al.  Software Defect Reduction Top 10 List , 2001, Computer.

[37]  Mary Shaw,et al.  The coming-of-age of software architecture research , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.

[38]  A. Tversky Features of Similarity , 1977 .

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

[40]  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.

[41]  Annie I. Antón,et al.  A Representational Framework for Scenarios of System Use , 1998, Requirements Engineering.

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

[43]  David Sankoff,et al.  Time Warps, String Edits, and Macromolecules: The Theory and Practice of Sequence Comparison , 1983 .

[44]  Doris L. Carver,et al.  Evaluation method for user requirements documents , 1989 .

[45]  Neil A. M. Maiden,et al.  Guiding use case authoring: results of an empirical study , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[46]  Julio Cesar Sampaio do Prado Leite,et al.  Supporting scenario evolution , 2004, Requirements Engineering.

[47]  Thomas A. Alspaugh,et al.  Scenario networks and formalization for scenario management , 2002 .

[48]  William N. Robinson,et al.  Reuse of scenario specifications using an automated relational learner: a lightweight approach , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[49]  Barry W. Boehm,et al.  Verifying and Validating Software Requirements and Design Specifications , 1989, IEEE Software.

[50]  Constance L. Heitmeyer,et al.  Consistency checking of SCR-style requirements specifications , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

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

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

[53]  Annie I. Antón,et al.  Contrasting use case, goal, and scenario analysis of the Euronet system , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[54]  Eda Marchetti,et al.  Cow Suite: A UML-based tool for test-suite planning and derivation , 2004 .

[55]  Thomas A. Alspaugh,et al.  The Importance of Clarity in Usable Requirements Specification Formats , 2006 .

[56]  Axel van Lamsweerde,et al.  Inferring Declarative Requirements Specifications from Operational Scenarios , 1998, IEEE Trans. Software Eng..

[57]  Sooyong Park,et al.  Implementation of an efficient requirements-analysis supporting system using similarity measure techniques , 2000, Inf. Softw. Technol..

[58]  Peter Haumer,et al.  Use Case-Based Software Development , 2006 .

[59]  Walter P. Bond,et al.  Sotware modularization using requirements attributes , 2004, ACM-SE 42.