This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Dominant Design
March/April 2011 (vol. 28 no. 2)
pp. 8-9
ASCII Text
x 
 
Grady Booch, "Dominant Design," IEEE Software, vol. 28, no. 2, pp. 8-9, March/April, 2011.
 
 
BibTex
x
 
@article{ 10.1109/MS.2011.29,
author = {Grady Booch},
title = {Dominant Design},
journal ={IEEE Software},
volume = {28},
number = {2},
issn = {0740-7459},
year = {2011},
pages = {8-9},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2011.29},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Dominant Design
IS - 2
SN - 0740-7459
SP8
EP9
EPD - 8-9
A1 - Grady Booch,
PY - 2011
KW - architecture
KW - software-intensive system
KW - dominant design
KW - punctuated equilibrium
KW - software engineering
KW - history of computing
KW - standards
KW - best practices
VL - 28
JA - IEEE Software
ER -
 
The architecture of any innovative software-intensive system will experience many periods of growth and then collapse, with times of punctuated equilibrium in between. This appears to be a natural and desirable phenomenon. Fighting that reality wastes energy, yet to ignore it in ways that put you out of sync with that rhythm is even more disastrous.
Index Terms:
architecture, software-intensive system, dominant design, punctuated equilibrium, software engineering, history of computing, standards, best practices
Citation:
Grady Booch, "Dominant Design," IEEE Software, vol. 28, no. 2, pp. 8-9, March-April 2011, doi:10.1109/MS.2011.29
Usage of this product signifies your acceptance of the Terms of Use.