|
ABSTRACT
A formal system specification is often written declaratively, in terms of the properties of the system components. This makes the system description modular and concise. However, this does not make the procedural aspects of the system easily understandable. Here arises the need for automatically generating interesting behavior patterns, specifically, scenarios.
This paper is a preliminary report of our research in generating interesting scenarios. We define several types of scenarios of interest and discuss the algorithms for generating them. At the center of the algorithms is a data structure, called “influence graphs,” that reflects how the objects in a system affect one another.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
| |
Aho 79
|
|
| |
Balzer 79
|
Balzer, R. M., and N. M. Goldman, "Principles of good software specification and their implications for specification languages," in Proceeding8 of the Specifications of Reliable Software Conference, pp. 58-67, Boston, Massachusetts, April 1979. (Also presented at the National Computer Conference, 1981.)
|
| |
Clarke 80
|
L. Clarke, "Symbolic evaluation methods in program analysis," in Muchnick S.S., Jones, N. D. (ed.), Program Flow Analysis , Prentice-Hall Inc., 1980.
|
| |
Cohen 84
|
Donald Cohen, "A forward inference engine to aid in understanding specifications," in Proceeding8 of National Conference on Artificial Intelligence, August 1984.
|
| |
Cohen 86
|
Donald Cohen, "Efficient Compilation of Virtual Database Specifications," in Proceedings of National Conference on Artificial Intelligence, August 1986.
|
| |
DeKleer 84
|
|
| |
Dubois 87
|
Eric Dubois and Jacques hagelstein, "Reasoning on Formal Requirements: A Lift Control System," in Proceedings of The Fourth International Workshop on Software Specification and Design, Monterey, California, U.S.A., April 1987.
|
| |
Fickas 87
|
Steve Fickas, "Automating the Analysis Process: An Example," in Proceedings of The Fourth International Workshop on Software Specification and Design, April 1987.
|
| |
Howden 75
|
W.E. Howden, "Methodology for the Generation of Program Test Data," IEEE Transaction Computer, May 1975.
|
| |
Johnson 87
|
Lewis Johnson, "Knowledge Based Specification Assistant," Unpublished, 1987.
|
| |
Kemmerer 85
|
Richard Kemmerer, "Testing Formal Specifications to Detect Design Errors," IEEE transactions on software engineering 11, (1), 1985.
|
| |
Mohammed 86
|
John Mohammed and Reid Simmons, "Qualitative Simulation of Semiconductor Fabrication," in Proceeding8 of the National Conference on Artificial Intelligence, Philadelphia, Pennsylvania, 1986.
|
| |
Rich 87
|
Charles Rich, Richard C. Waters, Howard B. Reubenstein, "Toward a Requirement Apprentice," in Proceeding8 of The Fourth International Workshop on Software Specification and DeMgn, Monterey, California, U.S.A., April 1987.
|
| |
Schank 77
|
Schank, Roger and Robert Abelson, Script, Plans, Goals and Understanding, John Wiley & Son, Hillsdale, New Jersey, 1977.
|
 |
Taylor 83
|
|
| |
Weld 86
|
|
| |
Yue 86
|
|
| |
Yue 87
|
Yue, Kaizhi, "What does it mean to say a specification is complete?," in Proceedings of The Fourth International Workshop on Software Specification and Design, Monterey, California, U.S.A., April 1987.
|
| |
Yue 88a
|
Yue, Kaizhi, "Directionality and Stability of System Behaviors," in Proceedings of The Fourth Conference on Artificial Intelligence Applications, San Diego, California, U.S.A., March 1988.
|
 |
Yue 88b
|
|
|