Regular papers Specifying and executing behavioral requirements: the play-in/play-out approach (2002)
BibTeX
@MISC{Harel02regularpapers,
author = {David Harel and Rami Marelly},
title = {Regular papers Specifying and executing behavioral requirements: the play-in/play-out approach},
year = {2002}
}
Bookmark
 |
 |
 |
 |
 |
 |
OpenURL
Abstract
Abstract. A powerful methodology for scenario-based specification 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 behavior is played in, the play-engine automatically generates a formal version in an extended version of 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 inter-object requirements. The ideas appear to be relevant to many stages of system development, including requirements engineering, specification, testing, analysis and implementation.
