Rule-based verification of scenarios with pre-conditions and post-conditions

Scenarios that describe concrete situations of software operation play an important role in software development, especially in requirements engineering. Since scenarios are informal, the correctness of scenarios is hard to verify. The authors have developed a language for describing scenarios in which simple action traces are embellished. The purposes are to include typed frames based on a simple case grammar of actions and to describe the sequence among events. Based on this scenario language, this paper describes both (1) a correctness-verification method using rules to detect errors (lack of events, extra events, and wrong sequence among events) in a scenario and (2) a retrieval method of rules from rule DB that applicable to scenarios using pre and postconditions.

[1]  Gustavo Rossi,et al.  Enhancing a requirements baseline with scenarios , 1997, Requirements Engineering.

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

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

[4]  Alistair G. Sutcliffe,et al.  Experience with SCRAM, a SCenario Requirements Analysis Method , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

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

[6]  Colin Potts,et al.  Grounding Scenarios in Frame-Based Action Semantics , 2001 .

[7]  Camille Salinesi,et al.  Guiding Scenario Authoring , 1998, EJC.

[8]  Camille Salinesi.  Writing and Correcting Textual Scenarios for System Design , 1998, DEXA Workshop.

[9]  Atsushi Ohnishi.  Software requirements specification database based on requirements frame model , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[10]  N. Maiden.  CREWS validation frames: validating systems requirements , 1998 .

[11]  Neil A. M. Maiden,et al.  Problem domain categories in requirements engineering , 1998, Int. J. Hum. Comput. Stud..

[12]  Neil A. M. Maiden,et al.  CREWS Validation Frames: Patterns for Validating Systems Requirements , 1998, REFSQ.

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

[14]  Atsushi Ohnishi,et al.  A transformation method of scenarios from different viewpoints , 2004, 11th Asia-Pacific Software Engineering Conference.

[15]  Hiroshi Fujimoto,et al.  Transformation and integration method of scenarios , 2002, Proceedings 26th Annual International Computer Software and Applications.

[16]  Jolita Ralyté,et al.  Scenario Integration into Requirements Engineering Methods , 1997 .

[17]  Charles J. Fillmore,et al.  THE CASE FOR CASE. , 1967 .

[18]  Corina S. Pasareanu,et al.  Assume-guarantee verification of source code with design-level assumptions , 2004, Proceedings. 26th International Conference on Software Engineering.

[19]  Julio Cesar Sampaio do Prado Leite,et al.  Domain independent regularities in scenarios , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[20]  Atsushi Ohnishi,et al.  Visual software requirements definition environment , 1997, Proceedings Twenty-First Annual International Computer Software and Applications Conference (COMPSAC'97).