This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Scenarios in System Development: Current Practice
March/April 1998 (vol. 15 no. 2)
pp. 34-45
ASCII Text
x 
 
Klaus Weidenhaupt, Klaus Pohl, Matthias Jarke, Peter Haumer, "Scenarios in System Development: Current Practice," IEEE Software, vol. 15, no. 2, pp. 34-45, March/April, 1998.
 
 
BibTex
x
 
@article{ 10.1109/52.663783,
author = {Klaus Weidenhaupt and Klaus Pohl and Matthias Jarke and Peter Haumer},
title = {Scenarios in System Development: Current Practice},
journal ={IEEE Software},
volume = {15},
number = {2},
issn = {0740-7459},
year = {1998},
pages = {34-45},
doi = {http://doi.ieeecomputersociety.org/10.1109/52.663783},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Scenarios in System Development: Current Practice
IS - 2
SN - 0740-7459
SP34
EP45
EPD - 34-45
A1 - Klaus Weidenhaupt,
A1 - Klaus Pohl,
A1 - Matthias Jarke,
A1 - Peter Haumer,
PY - 1998
VL - 15
JA - IEEE Software
ER -
 
The authors report on a survey of scenario-based requirements engineering practices at 15 different projects in four European countries. They conducted on-site interviews of project teams and examined documents produced and the environments and tools used. The Crews team noted that scenario purposes and uses varied more widely than expected, which suggests the need for better management and tool support to develop and maintain scenarios as artifacts in their own right.
Citation:
Klaus Weidenhaupt, Klaus Pohl, Matthias Jarke, Peter Haumer, "Scenarios in System Development: Current Practice," IEEE Software, vol. 15, no. 2, pp. 34-45, March-April 1998, doi:10.1109/52.663783
Usage of this product signifies your acceptance of the Terms of Use.