ACM Home Page
Please provide us with feedback. Feedback
Architectural issues in software reuse: it's not just the functionality, it's the packaging
Full text PdfPdf (389 KB)
Source Symposium on Software Reusability archive
Proceedings of the 1995 Symposium on Software reusability table of contents
Seattle, Washington, United States
Pages: 3 - 6  
Year of Publication: 1995
ISBN:0-89791-739-1
Also published in ...
Author
Mary Shaw  School of Computer Science & Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA
Sponsor
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 6,   Downloads (12 Months): 47,   Citation Count: 22
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/211782.211783
What is a DOI?

ABSTRACT

Effective reuse depends not only on finding and reusing components, but also on the ways those components are combined. The informal folklore of software engineering provides a number of diverse styles for organizing software systems. These styles, or architectures, show how to compose systems from components; different styles expect different kinds of component packaging and different kinds of interactions between the components. Unfortunately, these styles and packaging distinctions are often implicit; as a consequence, components with appropriate functionality may fail to work together. This talk surveys common architectural styles, including important packaging and interaction distinctions, and proposes an approach to the problem of reconciling architectural mismatches.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
Booch 86
Garlan et al 95
 
Lane 90
Thomas G. Lane. Studying Software Architecture Through Design Spaces and Rules. Carnegie Mellon University Technical Report , September 1990.
 
Shaw & Garlan 95

CITED BY  22