In 2/3rds of projects surveyed for scenario use by Weidenhaupt et al.
(1998), scenario generation and usage was interrelated with rapid
prototyping or even building first versions of the the new system.
Combining these approaches yielded symbiotic effects. That is, without
prototyping, the value of using scenarios would drop to almost zero, and
vice versa. Such combination was essential to selling the overall project
to the customer.
A typical process was identified. In early project stages, domain experts
created a first set of scenarios to communication application knowledge
and their system vision to systems engineers. Based on these,
requirements engineers developed a requirements specification with
which to develop prototypical implementations. Prototypes developed
could vary widely.
The initial scenarios served to validate the prototypes and, indirectly, the
requirements specification. Evaluating the prototypes led to detection of
misunderstanding between the domain experts and the system
developer. Equally important, validating prototypes against the initial
scenarios let the domain experts validate the initial scenarios themselves
to detect missing functionality, over-specifications, errors, and even
unintended side effects.
Unearthing the gaps helped developers improve the scenarios or adapt
the prototype or specification to the new detected requirements. This
established an evolutionary systems development process in which the
domain experts worked closely with the software developers.
Weidenhaupt K., Pohl K., Jarke M. & Haumer P., Scenarios in Systems Development: Current Practice’, IEEE
Software 15(2), 34-45
Reference: Reference: Neil Maiden (2011) Requirements Engineering Lecture Notes