|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
It Is What It Is Because It Was What It Was
January/February 2007 (vol. 24 no. 1)
pp. 14-15
| ASCII Text | x | ||
| Grady Booch, "It Is What It Is Because It Was What It Was," IEEE Software, vol. 24, no. 1, pp. 14-15, January/February, 2007. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2007.19, author = {Grady Booch}, title = {It Is What It Is Because It Was What It Was}, journal ={IEEE Software}, volume = {24}, number = {1}, issn = {0740-7459}, year = {2007}, pages = {14-15}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2007.19}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - It Is What It Is Because It Was What It Was IS - 1 SN - 0740-7459 SP14 EP15 EPD - 14-15 A1 - Grady Booch, PY - 2007 KW - architecture KW - architectural pattern KW - software engineering KW - problem solving VL - 24 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2007.19
Software systems usually have the same basic architectural pattern as their earlier incarnations, manifesting in decreasingly refined forms as we move back in time. Similarly, when a new problem confronts us, we try many different approaches, but over time, for the same kind of problem, solutions tend to converge to the same, more constrained, solution space.
Index Terms:
architecture, architectural pattern, software engineering, problem solving
Citation:
Grady Booch, "It Is What It Is Because It Was What It Was," IEEE Software, vol. 24, no. 1, pp. 14-15, Jan.-Feb. 2007, doi:10.1109/MS.2007.19
Usage of this product signifies your acceptance of the Terms of Use.