A Proposal For A Scenario Classification Framework (1996)
Cached
Download Links
| Citations: | 53 - 16 self |
BibTeX
@MISC{Rolland96aproposal,
author = {C. Rolland and C. Ben Achour and C. Cauvet and J. Ralyté and A. Sutcliffe and N.A.M. Maiden and M. Jarke and P. Haumer and K. Pohl and E. Dubois and K. Pohl (rwth Aachen},
title = {A Proposal For A Scenario Classification Framework},
year = {1996}
}
Years of Citing Articles
Bookmark
 |
 |
 |
 |
 |
 |
OpenURL
Abstract
Interface Object AIO state Time axis Atomic Operation System Stimuli, Response, or System Message name name Figure 2 : Use case description and use case specification [Regnell et al., 1995] Scenarios which are designed systems and are then run as simulations to present a future vision of how the system will behave or how the users might interact with the system need a formally defined modelling language. For example, the underlying language of scenario descriptions proposed by M. Glinz [Glinz, 1995] is a statechart-based model [Harel, 1987]. In the same line, Hsia et al. [Hsia et al., 1994] show that a scenario can be adequately represented by a regular grammar from which a conceptual machine for prototyping may be constructed. Formal descriptions are useful support for validating the requirements specification, reasoning about it and generating cost-effective prototypes. A Proposal for a Scenario Classification Framework CREWS Report 96-01 - 7 - For stakeholders for wh...
