Skip Navigation

IEICE Transactions on Information and Systems 2008 E91-D(4):881-887; doi:10.1093/ietisy/e91-d.4.881
This Article
Right arrow Full Text (PDF)
Right arrow References
Right arrow Alert me when this article is cited
Right arrow Alert me if a correction is posted
Services
Right arrow Email this article to a friend
Right arrow Similar articles in this journal
Right arrow Alert me to new issues of the journal
Right arrow Add to My Personal Archive
Right arrow Download to citation manager
Right arrow Request Permissions
Google Scholar
Right arrow Articles by OHNISHI, A.
Social Bookmarking
Add to CiteULike   Add to Connotea   Add to Del.icio.us  
What's this?

Copyright © 2008 The Institute of Electronics, Information and Communication Engineers

Special Section on Knowledge-Based Software Engineering -- Papers -- Software Engineering

A Generation Method of Exceptional Scenarios from a Normal Scenario

Atsushi OHNISHI1

1 The author is with the Faculty of Information Science and Engineering, Ritsumeikan University, Kusatsu-shi, 525–8577 Japan. E-mail: ohnishi{at}cs.ritsumei.ac.jp


  Abstract

This paper proposes a method to generate exceptional scenarios from a normal scenario written with a scenario language. This method includes (1) generation of exceptional plans and (2) generation of exceptional scenario by a user's selection of these plans. The proposed method enables users to decrease the omission of the possible exceptional scenarios in the early stages of development. The method will be illustrated with some examples.

Key Words: requirements elicitation, scenario analysis, scenario generation

Manuscript received July 2, 2007. Manuscript revised October 8, 2007.


Add to CiteULike CiteULike   Add to Connotea Connotea   Add to Del.icio.us Del.icio.us    What's this?




Disclaimer:
Please note that abstracts for content published before 1996 were created through digital scanning and may therefore not exactly replicate the text of the original print issues. All efforts have been made to ensure accuracy, but the Publisher will not be held responsible for any remaining inaccuracies. If you require any further clarification, please contact our Customer Services Department.