Abstract
We need ways to describe designs that communicate the reasons for our design decisions, not just the results. Design patterns have been proposed as ways of communicating design information. This paper shows that patterns can be used to derive an architecture from its problem statement. The resulting description makes it easier to understand the purpose of the various architectural features.
Preview
Unable to display preview. Download preview PDF.
Bibliography
Christopher Alexander, Sara Ishikawa and Murray Silverstein, with Max Jacobson, Ingrid Fiksdahl-King and Shlomo Angel. A Pattern Language. Oxford University Press, New York, 1977.
Christopher Alexander. The Timeless Way of Building. Oxford University Press, New York, 1979.
Bruce Anderson. Workshop Report-Towards an Architecture Handbook. OOPSLA'92: Addendum to the Proceedings, printed as OOPSLA Messenger, 4(2): 109–114, April 1993
Peter Coad, “Object-Oriented Patterns”, Communications of the ACM, 35(9):153–159, 1992.
Peter Coad and Mark Mayfield. Workshop Report-Patterns. OOPSLA'92: Addendum to the Proceedings, printed as OOPSLA Messenger, 4(2): 93–95, April 1993
L. Peter Deutsch, “Design Reuse and Frameworks in the Smalltalk-80 Programming System”, pp 55–71, Software Reusability, Vol II, ed. Ted J. Biggerstaff and Alan J.Perlis, ACM Press, 1989.
Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides, “Design patterns: Abstraction and reuse of object-oriented design”. In European Conference on Object-oriented Programming, Kaiserlauten, German, July 1993. Published as Lecture notes in Computer Science #707, pp. 406–431, Springer-Verlag.
Erich Gamma, Richard Helm, Ralph Johnson.and John Vlissides. Design Patterns: Elements of Object-Oriented Software Architecture Addison-Wesley, 1994.
David Garlan and Mary Shaw, “An Introduction to Software Architecture”, in Advances in Software Engineering and Knowledge Engineering Volume I, World Scientific Publishing Company, 1993.
Ralph E. Johnson and Brian Foote,“Designing Reusable Classes” Journal of Object-Oriented Programming, 1(2):22–25, 1988.
Ralph E. Johnson, “Documenting Frameworks with Patterns” OOPSLA '92 Proceedings, SIGPLAN Notices, 27(10): 63–76, Vancouver BC, October 1992.
Norman Kerth, John Hogg, Lynn Stein, and Harry Porter, “Summary of Discussions from OOPSLA-87's Methodology and OOP Workshop”, OOPSLA'87: Addendum to the Proceedings, printed as SIGPLAN Notices, 23(5), pp. 9–16, 1988.
Glenn E. Krasner and Stephen T. Pope,“A Cookbook for Using the Model-View Controller User Interface Paradigm in Smalltalk-80”, Journal of Object-Oriented Programming, 1(3):26–49, 1988.
Richard Helm and Ian M. Holland and Dipayan Gangopadhyay, “Contracts: Specifying Behavioral Compositions in Object-Oriented Systems”, OOPSLA '90 Proceedings, SIGPLAN Notices, 25(10), pp. 169–180,Vancouver BC, October 1990.
David L. Parnas and P.C. Clements “A Rational Design Process: How and Why to Fake It”, IEEE Transactions on Software Engineering, SE-12:2 February 1986.
Author information
Authors and Affiliations
Corresponding authors
Editor information
Rights and permissions
Copyright information
© 1994 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Beck, K., Johnson, R. (1994). Patterns generate architectures. In: Tokoro, M., Pareschi, R. (eds) Object-Oriented Programming. ECOOP 1994. Lecture Notes in Computer Science, vol 821. Springer, Berlin, Heidelberg. https://doi.org/10.1007/BFb0052180
Download citation
DOI: https://doi.org/10.1007/BFb0052180
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-58202-1
Online ISBN: 978-3-540-48567-4
eBook Packages: Springer Book Archive