Generating statechart designs from scenarios

By J. Whittle, J. Schumann. Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium, 2000

415 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Matching and Merging of Statecharts Specifications (2007, methodology): “For example, [32] uses logical pre/post-conditions over object interactions for merging independentlydeveloped sequence diagrams, and [31] uses refinement relations for merging consistent state-machine models such that their behavioural properties are preserved.”
Monitoring Java Programs with Java PathExplorer (2001, methodology): “The Automated Software Engineering group at NASA Ames Research Center has for some time investigated advanced formal methods for insuring software correctness, in both areas of program synthesis [14,5,19] and program veri cation [8,9,18,7,11].”
Agent Technology from a Formal Perspective (2006, background): “This part of our research addresses an abstract aspect of the topic NASA has termed human-centered computing [34], and it is related to dialogue modeling (see [11], sec.”
Research Directions in Requirements Engineering (2007, methodology): “Of these, scenario-based notations [2, 5, 37, 41, 143, 146, 147, 159] have been the focus of much recent research – perhaps because scenarios are easiest for practitioners and nontechnical stakeholders to use, or perhaps because scenarios are naturally incomplete, and so they lend themselves to lots”