This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Architectural Mismatch: Why Reuse Is So Hard
November 1995 (vol. 12 no. 6)
pp. 17-26
Architectural mismatch stems from mismatched assumptions a reusable part makes about the system structure it is to be part of. These assumptions often conflict with the assumptions of other parts and are almost always implicit, making them extremely difficult to analyze before building the system. To illustrate how the perspective of architectural mismatch can clarify our understanding of component integration problems, we describe our experience of building a family of software design environments from existing parts. On the basis of our experience, we show how an analysis of architectural mismatch exposes some fundamental, thorny problems for software composition and suggests some possible research avenues needed to solve them.
Citation:
David Garlan, Robert Allen, John Ockerbloom, "Architectural Mismatch: Why Reuse Is So Hard," IEEE Software, vol. 12, no. 6, pp. 17-26, Nov. 1995, doi:10.1109/52.469757
Usage of this product signifies your acceptance of the Terms of Use.