loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Are "Best Practices" Requirements Documents a Myth?
May/June 2006 (vol. 23 no. 3)
pp. 104, 103
ASCII Text
x 
 
Johann Rost, "Are "Best Practices" Requirements Documents a Myth?," IEEE Software, vol. 23, no. 3, pp. 104, 103, May/June, 2006.
 
 
BibTex
x
 
@article{ 10.1109/MS.2006.64,
author = {Johann Rost},
title = {Are "Best Practices" Requirements Documents a Myth?},
journal ={IEEE Software},
volume = {23},
number = {3},
issn = {0740-7459},
year = {2006},
pages = {104, 103},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2006.64},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Are "Best Practices" Requirements Documents a Myth?
IS - 3
SN - 0740-7459
SP
EP
EPD - 104, 103
A1 - Johann Rost,
PY - 2006
KW - software engineering
KW - best practices
KW - requirements
VL - 23
JA - IEEE Software
ER -
 
Johann Rost, University Politehnica of Bucharest
You might think that it would be fairly straightforward to find a requirements document that has been constructed according to the "best practices." You'd be wrong.
Index Terms:
software engineering, best practices, requirements
Citation:
Johann Rost, "Are "Best Practices" Requirements Documents a Myth?," IEEE Software, vol. 23, no. 3, pp. 104, 103, May/June 2006, doi:10.1109/MS.2006.64
Usage of this product signifies your acceptance of the Terms of Use.