David Garlan
Robert Allen
- AAG93.Gregory Abowd, Robert Allen, and David Garlan. Using style to understand descriptions of software architecture, In Proceedings of SIGSOFT'93: Foundations of Software Engineering, Software Engineering Notes 18(5), pages 9-20. ACM Press, December 1993. Google Scholar
Digital Library
- AG94.Robert Allen and David Garlan. Formalizing architectural connection. In Proceedings of the Sixteenth international Conference on Softiare Engineering, pages 71-80, Sorrento, Italy, May 1994, Google ScholarDigital Library
- Bam90.J. Bamberger. STARS/users workshop: Final re-port - issues for discussion groups. Technical Report CMU/SEI-90-TR-32 ADA235776, Software Engineer-ing Institute (Carnegie Mellon University), 1990.Google Scholar
- BO92.Don Batory and Sean O'Malley. The design and implementation of hierarchical software systems with reusable components. ACM Transactions on Sojhvare Engineering and Methodology, 1(4):355-398, October 1992. Google ScholarDigital Library
- BP89.Ted J. Biggerstaff and Alan J. Perlis. Soflware Reusability.ACM Press, 1989.Google Scholar
- BS92.Barry Boehm and William Scherlis. Megaprogramming.In Proceedings of Sojiware Technology Conference,DARPA. ARPA, 1992.Google Scholar
- BSST93.Don Batory, Vivek Singhal, Marty Sirkin, and Jeff Thomas. Scalable software libraries. In Proceedings of SIGSOFT'93, pages 191-199, December 1993. Google ScholarDigital Library
- Cor91.The Common Object Request Broker Architecture and specification. OMG Document Number 91.12.1, December 1991. Revision 1.1 (Draft 10).Google Scholar
- Dra87.R. R. Draves. MIG - the MACH interface genera-tor, August 1987. Comment 1 by schlenk, Sat Jul 2 15:08:471988 MIG seem very similiar to the SUN rpcgen facility. Parameters are described in a formal language and compiled into stubs.Google Scholar
- GAO94.David Garlan, Robert Allen, and John Ockerbloom. Exploiting style in architectural design environments. In Proceedings of SIGSOFT'94: Foundations of Software Engineering. ACM Press, December 1994. Google ScholarDigital Library
- Ger89.Colin Gerety. HP Softbench: A new generation of software development tools. Technical Report SESD-89- 25, Hewlett-Packard Software Engineering Systems Division, Fort Collins, Colorado, November 1989.Google Scholar
- GHJV94.Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides. Design Patterns: Micro-Architectures for Reusable Object-Oriented Design. Addison-Wesley, 1994.Google Scholar
- GS93.David Garlan and Mary Shaw. An introduction to software architecture. In V.Ambriola and G.Tortora, editors, Advances in Software Engineering and Knowledge Engineering, Volume I, New Jersey, 1993. World Scientific Publishing Company.Google ScholarCross Ref
- IW95.pro-Paola Inverardi and Alex Wolf. Formal specification and analysis of software architectures using the chemical, abstract machine model. IEEE Transactions on Softare Engineering, 1995. To appear. Google ScholarDigital Library
- JC94.G.R. Ribeiro Justo and P.R. Freire Cunha. Deadlockfree configuration programming. In Proceedings of the Second International Workshop on Configurable Distributed Systems, March 1994.Google ScholarCross Ref
- Kru92.Charles W. Krueger. Software reuse. Computing Surveys,24(2):131-183, June 1992. Google ScholarDigital Library
- LAK+95.David C Luckham, Larv M. Aumrstin. John J. Kennev. James Veera, Doug Bryan, and Walter Mann. Specification and analysis of system architecture using rapide. IEEE Transactions on Software Engineering, 1995. To appear. Google ScholarDigital Library
- Lan90.Thomas G. Lane, A design space and design rules for user interface software architecture. Technical Report CMU/SEI-90-TR-22 ESD-90-TR-223, Carnegie Mel-lon University, Software Engineering Institute, Novem-ber 1990.Google ScholarCross Ref
- LVC89.Mark A. Linton, John M. Vlissides, and Paul R. Calder. Compusing user interfaces with interviews. IEEE Com-puter, 22(2), February 1989. Google ScholarDigital Library
- MG92.Erik Mettala and Marc H. Graham. The domainspecific software architecture program. Technical Report CMU/SEI-92-SR-9, Carnegie Mellon Software Engineering Institute, June 1992.Google ScholarCross Ref
- Par72.D. L. Pamas. On the criteria to be used in decomposing systems into modules. Communications of the ACM, 15(1 2): 1053-1058, December 1972, Google ScholarDigital Library
- PW92.Dewayne E. Perry and Alexander L. Wolf. Foundations for the study of software architecture. ACM SIG-SOFT Soflware Engineering Notes, 17(4):40-52, Oc-tober 1992. Google ScholarDigital Library
- Rei90.Steven P. Reiss. Connecting tools using message passing in the field program development environment. IEEE Softiare, July 1990. Google ScholarDigital Library
- SDK+95.Mary Shaw, Robert DeLine, Daniel V. Klein, Theodore L. Ross, David M. Young, and Gregory Zelesnik. Abstractions for software architecture and tools to support them. IEEE Transactions on Soflware Engineering,1995. To appear. Google ScholarDigital Library
- SG86.Robert W. Scheifler and Jim Gettys. The X window system. ACM Transactions on Graphics, 5(2):79-1 09, April 1986. Google ScholarDigital Library
- T+88.Richard N. Taylor et al. Foundations for the Arcadia environment architecture. In Proceedings of the ACM SIGSOFT/SIGPL4N Software Engineering Symposium on Practical Software Development Environments,Boston, MA, November 1988. Published as SIGPLAN NOTICES, 24(2). Google ScholarDigital Library
- VL90.John M. Vlissides and Mark A. Linton. Unidraw: A framework for building domain-slpecific graphical editors. ACM Transactions on Information Systems, 8(3):237-268, July 1990. Google ScholarDigital Library
- YS94.Daniel M. Yellin and Robert E. Strom. Interfaces, tocols, and the semi-automatic construction of software adaptors. Proceedings of 00PSLA '94, October 1994. Google ScholarDigital Library
Index Terms
- Architectural mismatch or why it's hard to build systems out of existing parts
Recommendations
Architectural Mismatch: Why Reuse Is Still So Hard
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 ...
Architectural Mismatch: Why Reuse Is So Hard
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 ...
GoRRiLA and hard reality
PSI'11: Proceedings of the 8th international conference on Perspectives of System InformaticsWe call a <em>theory problem</em> a conjunction of theory literals and a <em>theory solver</em> any system that solves theory problems. For implementing efficient theory solvers one needs benchmark problems, and especially hard ones. Unfortunately, hard ...
Comments