Articles Next»

Architectural Mismatch: Why Reuse is Still So Hard

David Garlan, Carnegie Mellon University
Robert Allen, IBM
John Mark Ockerbloom, University of Pennsylvania

Article comments

Appeared in IEEE Software 26:4, July/August 2009, pp. 66-69. Copyright 2009 IEEE. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the IEEE.

Abstract

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.

Suggested Citation

David Garlan, Robert Allen, and John Mark Ockerbloom. "Architectural Mismatch: Why Reuse is Still So Hard" Scholarship at Penn Libraries (2009).
Available at: http://works.bepress.com/john_mark_ockerbloom/12