![](bg7.png)
validation-frame does not check them.
6 CONCLUSIONS
The authors proposed a scenario checking method
with rules based on the security evaluation criteria.
We can specify the occurrence times of events
and/or the time sequence among events as rules.
Both scenario and rules can be transformed into the
internal representation so that we can check scenario
with rules and evaluate the correctness of one
particular observed scenario.
The proposed method was demonstrated by
the example and was evaluated. The evaluation
results show that errors (the lack of events, extra
events, the wrong sequence among events, and
wrong behaviors against the security common
criteria) in scenario can be effectively detected by
checking the scenario with rules. By using this
correctness checking method, we can get a scenario
that satisfies security common criteria more
effectively in system development.
ACKNOWLEDGEMENTS
The authors thank to Mr. Tatsuya Toyama and Mr.
Kenta Nishiyuki for their contributions to the
research.
REFERENCES
Alexander, I. F., and Maiden, N., 2004. “Scenarios,
Stories, Use Cases – Through the Systems
Development Life-Cycle”, John Wiley & Sons.
Barish, R, 1997. ACM Conference Committee Job
Description, Conference Manual, Section No. 6.1.1,
http://www.acm.org/sig_volunteer_info/conference_m
anual/6-1-1PC.HTM.
Carroll, J.M., 2000. “Making Use: Scenario-based Design
of Human Computer Interactions”, MIT Press.
Cockburn, A., 2001. “Writing Effective Use Cases”,
Addison Wesley, USA.
Fillmore, C. J., 1968. “The Case for Case”, Universals in
Linguistic Theory, ed. Bach & Harms, Holt, Rinehart
and Winston Publishing, Chicago.
“IEEE Std. 830-1998, 1998.” IEEE Recommended
Practice for Software Requirements Specifications.
“ISO/IEC 15408 common criteria, 2005.”
McDermott, J. and Fox, C., 1999. “Using Abuse Case
Models for Security Requirements Analysis”,
Proceedings of the 15th IEEE Annual Computer
Security Applications Conference (ACSAC’99), pp.
55-65.
Ohnishi, A., 1996. “Software requirements specification
database based on requirements frame model”,
Proceedings of the Second IEEE International
Conference on Requirements Engineering (ICRE’96),
pp. 221-228.
Ohnishi, A., Potts, C. 2001. Grounding Scenarios in
Frame-Based Action Semantics, Proc. of 7th
International Workshop on Requirements Engineering:
Foundation of Software Quality (REFSQ’01),
Interlaken, Switzerland, June 4-5, pp.177-182.
Railway Information System Co., Ltd., 2001. JR System,
http://www.jrs.co.jp/keiki/en/index_main.html.
Schneier, B., 2001. Secrets & Lies Digital Security in a
Networked World, John Wiley & Sons.
Sindre, G. and Opdahl, A. L., 2005. “Eliciting security
requirements with misuse cases,” Requirements
Engineering, Vol. 10, pp. 34-44.
Sutcliffe, A. G., Maiden, N. A. M., Minocha S., Manuel
D., 1998. Supporting Scenario-Based Requirements
Engineering, IEEE Trans. Software Engineering,
Vol.24, No.12, pp.1072-1088.
Toval, A., Nicolaus, J. Moros, B. and Gracia, F., 2002.
Requirements Reuse for Improving Information
Systems Security: A Practitioner’s Approach,
Requirements Engineering, Vol. 6, No. 4, pp. 205-219.
Toyama, T., Ohnishi, A., 2005. Rule-based Verification of
Scenarios with Pre-conditions and Post-conditions,
Proc. Of the 13
th
IEEE International Conference on
Requirements Engineering (RE’05), Paris, France,
pp.319-328.
Weidenhaupt, K., Pohl, K., Jarke, M., Haumer, P., 1998.
Scenarios in System Development: Current Practice,
IEEE Software, Vol.15, No.2, pp.34-45.
Zhang, H. and Ohnishi, A., 2004. “Transformation
between Scenarios from Different Viewpoints”, IEICE
Transactions on Information and Systems, Vol. E87-
D, No. 4, pp. 801-810.
VERIFICATION OF SCENARIOS USING THE COMMON CRITERIA
11