This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
To Boldly Go Where No One Has Gone Before
January/February 2012 (vol. 29 no. 1)
pp. 23-25
ASCII Text
x 
 
Frank Buschmann, "To Boldly Go Where No One Has Gone Before," IEEE Software, vol. 29, no. 1, pp. 23-25, January/February, 2012.
 
 
BibTex
x
 
@article{ 10.1109/MS.2012.18,
author = {Frank Buschmann},
title = {To Boldly Go Where No One Has Gone Before},
journal ={IEEE Software},
volume = {29},
number = {1},
issn = {0740-7459},
year = {2012},
pages = {23-25},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2012.18},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - To Boldly Go Where No One Has Gone Before
IS - 1
SN - 0740-7459
SP23
EP25
EPD - 23-25
A1 - Frank Buschmann,
PY - 2012
KW - architecture
KW - domain-driven design
KW - interface design
KW - interaction design
KW - integration design
VL - 29
JA - IEEE Software
ER -
 
Frank Buschmann, Siemens Corporate Technology
Architecture mastery is more than professional expertise in modern software engineering methods and techniques. It is mainly in how architects approach design. Particularly, the "things between things" require the architect's full attention: domain concepts hidden between the lines of code; interactions and interfaces residing between components; and even choices between design options. This is the architect's territory, and successful architecture uncovers the things "in-between" as early as possible, make them explicit, and decide about them!

1. J-J. Levy, "Un Petit Bogue, Un Grand Boum!" (in French), 2010; http://moscova.inria.fr/~levy/talks/10enslongo enslongo.pdf.
2. J-L. Lions et al., "Ariane 501 Inquiry Board Report," 1996; http://esamultimedia.esa.int/docs/esa-x-1819eng.pdf.
3. E. Evans, Domain Driven Design, Addison-Wesley, 2004.
4. F. Buschmann and K. Henney, "Five Considerations for Software Architecture, Part 1, IEEE Software, vol. 27, no. 3, 2010, pp. 63–65.
5. E. Woods, "Architecting in the Gaps," 2011; http://gotocon.com/aarhus-2011/presentation/Architecting%20in%20the%20Gaps.
6. F. Buschmann, "Unusable Software Is Useless, Part 1," IEEE Software, vol. 28, no. 1, 2011, pp. 92–94.
7. F. Buschmann, K. Henney, and D.C. Schmidt, Pattern-Oriented Software Architecture—A Pattern Language for Distributed Computing, John Wiley and Sons, 2007.
8. G. Hohpe and B. Woolf, Enterprise Integration Patterns—Designing, Building, and Deploying Messaging Solutions, Addison-Wesley, 2003.
9. F. Buschmann, "Learning from Failure, Part 2: Featuritis, Performitis, and Other Diseases," IEEE Software, vol. 27, no. 1, 2010, pp. 10–11.
10. K. Henney, "Use Uncertainty as a Driver," 97 Things Every Software Architect Should Know, R. Monson-Haefel ed., O'Reilly, 2009, pp. 321–361.

Index Terms:
architecture, domain-driven design, interface design, interaction design, integration design
Citation:
Frank Buschmann, "To Boldly Go Where No One Has Gone Before," IEEE Software, vol. 29, no. 1, pp. 23-25, Jan.-Feb. 2012, doi:10.1109/MS.2012.18
Usage of this product signifies your acceptance of the Terms of Use.