Multiple instances and symbolic variables in executable sequence charts
OOPSLA '02 Proceedings of the 17th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Smart Play-out of Behavioral Requirements
FMCAD '02 Proceedings of the 4th International Conference on Formal Methods in Computer-Aided Design
Embedded Systems: Challenges in Specification and Verification
EMSOFT '02 Proceedings of the Second International Conference on Embedded Software
Specifying and executing requirements: the play-in/play-out approach
OOPSLA '02 Companion of the 17th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Agent Behavior Alignment: A Mechanism to Overcome Problems in Agent Interactions During Runtime
CIA '07 Proceedings of the 11th international workshop on Cooperative Information Agents XI
Patterns for monitoring scenarios to handle state based crosscutting concerns
Proceedings of the 15th Conference on Pattern Languages of Programs
Visualizing and simulating semantic web services ontologies
ICFEM'05 Proceedings of the 7th international conference on Formal Methods and Software Engineering
Lightweight formal methods for scenario-based software engineering
SMTT'03 Proceedings of the 2003 international conference on Scenarios: models, Transformations and Tools
| Hi-index | 0.00 |
A powerful methodology for specifying scenario-based requirements of reactive systems is described, in which the behavior is ``played in" directly from the system''s GUI or some abstract version thereof, and can then be ``played out". The approach is supported and illustrated by a tool, which we call the play-engine. As the requirements are played in, the play-engine automatically generates a formal version in the language of live sequence charts (LSCs). As they are played out, it causes the application to react according to the universal (``must") parts of the specification; the existential (``may") parts can be monitored to check their successful completion. Play-in is a user-friendly high-level way of specifying behavior and play-out is a rather surprising way of working with a fully operational system directly from its requirements. The ideas appear to be relevant to many stages of system development, including requirements engineering, specification, testing, analysis and implementation.