| Main page |
In a wide range of application areas, behavior is modeled using variations of scenarios and state machines. In telecommunications, ITU standards SDL (Specification and Description Language) and MSC (Message Sequence Charts) are used for formal specifications and descriptions. Also, for behavioral modeling of object-oriented software systems, UML interaction diagrams (sequence or collaboration diagrams) and statechart diagrams are commonly used. Use cases can be conveniently realized using interaction diagrams, which in turn aid in recognizing the operations and associations of classes and in specifying the behavior of objects as statecharts. Tool support automating parts of this process have been suggested. The usefulness and importance of dynamic modeling is not limited to software design. Behavioral modeling is essential also for understanding existing systems. In dynamic reverse engineering, the object interactions are usually modeled using scenario-based approaches, and the usage of interfaces of software components is modeled using state machines. Scenarios can also be used for analyzing interactions in concurrent and real-time systems and for synthesizing behavioral specifications. In this workshop, we will discuss the usage of scenario-based approaches in software engineering, both for requirements and design specifications, with an emphasis on the relationship between scenarios and state machines. Areas of interest of this one day workshop include, but are not limited to the following three main discussion topics: Moreover, we will identify the limitations and shortcomings of current approaches and outline possible directions for future research in the domain. A related workshop (scenario-based round-trip engineering) was organized at OOPSLA 2000. |