loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Software Process Improvement: Blueprints versus Recipes
September/October 2003 (vol. 20 no. 5)
pp. 86-93
ASCII Text
x 
 
Ivan Aaen, "Software Process Improvement: Blueprints versus Recipes," IEEE Software, vol. 20, no. 5, pp. 86-93, September/October, 2003.
 
 
BibTex
x
 
@article{ 10.1109/MS.2003.1231159,
author = {Ivan Aaen},
title = {Software Process Improvement: Blueprints versus Recipes},
journal ={IEEE Software},
volume = {20},
number = {5},
issn = {0740-7459},
year = {2003},
pages = {86-93},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2003.1231159},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Software Process Improvement: Blueprints versus Recipes
IS - 5
SN - 0740-7459
SP86
EP93
EPD - 86-93
A1 - Ivan Aaen,
PY - 2003
VL - 20
JA - IEEE Software
ER -
 
Ivan Aaen, Aalborg University

Viewing software processes as blueprints emphasizes that design is separate from use, and thus that software process designers and users are independent. In the approach presented here, software processes are viewed as recipes; developers individually and collectively design their own software processes through facilitation, reflection, and improvisation.

Citation:
Ivan Aaen, "Software Process Improvement: Blueprints versus Recipes," IEEE Software, vol. 20, no. 5, pp. 86-93, Sep./Oct. 2003, doi:10.1109/MS.2003.1231159
Usage of this product signifies your acceptance of the Terms of Use.