This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
July/August 2008 (vol. 25 no. 4)
pp. 4-7
ASCII Text
x 
 
Hakan Erdogmus, "Essentials of Software Process," IEEE Software, vol. 25, no. 4, pp. 4-7, July/August, 2008.
 
 
BibTex
x
 
@article{ 10.1109/MS.2008.87,
author = {Hakan Erdogmus},
title = {Essentials of Software Process},
journal ={IEEE Software},
volume = {25},
number = {4},
issn = {0740-7459},
year = {2008},
pages = {4-7},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2008.87},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Essentials of Software Process
IS - 4
SN - 0740-7459
SP4
EP7
EPD - 4-7
A1 - Hakan Erdogmus,
PY - 2008
KW - utilitarian view of software process
KW - human-centricity
KW - pragmatism
KW - empiricism
KW - experimentation
KW - value orientation
VL - 25
JA - IEEE Software
ER -
 
Hakan Erdogmus, National Research Council Canada
Process trends can be placed inside a triangular map according to their emphasis on three aspects, represented by the vertices: people, technology, and rigor. Plan-oriented, engineering, and research-based approaches tend to view software as a rigid artifact, so they stress technology and rigor over people. Evolutionary approaches tend to view software development as an organic, skills-driven technical activity, so they stress people and technology over rigor. But this scheme of positioning process approaches is rather rough. A more complete scheme requires dissection in terms of seven essential, mutually reinforcing characteristics: human-centricity, technical orientation, discipline, pragmatism, empiricism, experimentation, and value orientation.

[1] J. Procaccino and J.M. Verner, "What Do Software Practitioners Really Think about Project Success: An Exploratory Study," J. Systems and Software, vol. 78, no. 2, 2005, pp. 194–203.
[2] B.W. Boehm, Software Engineering Economics, Prentice-Hall, 1981.
[3] S.A. Frangos, "Motivated Humans for Reliable Software Products," Microprocessors and Microsystems, vol. 21, no. 10, 1997, pp. 605–610.
[4] S. Beecham et al., "Motivation in Software Engineering: A Systematic Literature Review," to be published in Information and Software Technology J., 2008; doi:10.1016/j.infsof.2007.09.004.
[5] J.R. Hackman and G.R. Oldman, Motivation through the Design of Work: Test of a Theory, Academic Press, 1976.
[6] D.J. Couger and R.A. Zawacki, Motivating and Managing Computer Personnel, John Wiley & Sons, 1980.
[7] A. Maslow, Motivation and Personality, Harper & Row, 1954.
[8] H. Sharp et al., "Models of Motivation in Software Engineering," to be published in Information and Software Technology J., 2008; doi:10.1016/j.infsof.2008.05.009.
[9] T. Hall et al., "A Systematic Review of Theory Use in Studies Investigating the Motivations of Software Engineers," to be published in ACM Trans. Software Eng. and Methodology, 2008; tosem.acm.org/Upcoming.php.
[10] F. Herzberg, The Motivation to Work, 2nd ed., Chapman & Hall, 1959.

Index Terms:
utilitarian view of software process, human-centricity, pragmatism, empiricism, experimentation, value orientation
Citation:
Hakan Erdogmus, "Essentials of Software Process," IEEE Software, vol. 25, no. 4, pp. 4-7, July-Aug. 2008, doi:10.1109/MS.2008.87
Usage of this product signifies your acceptance of the Terms of Use.