Architectural Mismatch: Why Reuse is Still So Hard
Loading...
Penn collection
Scholarship at Penn Libraries
Degree type
Discipline
Subject
architectural mismatch
software architecture
software reuse
Software Engineering
Systems Architecture
software architecture
software reuse
Software Engineering
Systems Architecture
Funder
Grant number
License
Copyright date
Distributor
Related resources
Contributor
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.
Advisor
Date Range for Data Collection (Start Date)
Date Range for Data Collection (End Date)
Digital Object Identifier
Series name and number
Publication date
2009-07-01
Journal title
Volume number
Issue number
Publisher
Publisher DOI
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.