This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Architectural Mismatch: Why Reuse Is Still So Hard
July/August 2009 (vol. 26 no. 4)
pp. 66-69
David Garlan, Carnegie Mellon University
John Ockerbloom, University of Pennsylvania
In this article, David Garlan, Robert Allen, and John Ockerbloom reflect on the state of architectural mismatch, a term they coined in their 1995 IEEE Software article, "Architectural Mismatch: Why Reuse Is So Hard." Although the nature of software systems has changed dramatically since the earlier article was published, the challenge of architectural mismatch remains an important concern for the software engineering field.

1. D. Garlan, R. Allen, and J. Ockerbloom, "Architectural Mismatch: Why Reuse Is So Hard," IEEE Software, Nov./Dec. 1995, pp. 17–26.
2. D. Garlan, R. Allen, and J. Ockerbloom, "Architectural Mismatch, or, Why It's Hard to Build Systems Out of Existing Parts," Proc. 17th Int'l Conf. Software Eng. (ICSE 95), IEEE CS Press, 1995, pp. 179–185.
3. M. Shaw and D. Garlan, Software Architecture: Perspectives on an Emerging Discipline, Prentice Hall, 1996.
4. F. Buschman et al., Pattern-Oriented Software Architecture: A System of Patterns, Vol. 1, John Wiley &Sons, 1996.
5. P. Clements et al., Documenting Software Architectures: Views and Beyond, Addison-Wesley, 2003.
6. Recommended Practice for Architectural Description of Software-Intensive Systems: ANSI/IEEE Std 1471 :: ISO/IEC 42010, IEEE, 2009; www.iso-architecture.orgieee-1471.

Index Terms:
architecture mismatch, software architecture, component-based systems, software engineering
Citation:
David Garlan, Robert Allen, John Ockerbloom, "Architectural Mismatch: Why Reuse Is Still So Hard," IEEE Software, vol. 26, no. 4, pp. 66-69, July-Aug. 2009, doi:10.1109/MS.2009.86
Usage of this product signifies your acceptance of the Terms of Use.