Design patterns
Authors:
Open Access
- 1 March 1998
- conference paper
- Published by Association for Computing Machinery (ACM)
- Vol. 30 (1) , 153-160
Abstract
The field of software patterns has seen an explosion in interest in the last three years. Work to date has been on the recognition, cataloging, and finding of patterns with little attention to the use of patterns, especially by students and practitioners not well-versed in object-oriented technologies. This project addresses pattern use through the development of several programming and pedagogical frameworks that supply support for using patterns throughout a computer science curriculum. Although we do not claim that patterns are Brooks' silver bullet [10], their use can help cope with the accidental complexity of software development and, we argue, their use is essential for a successful adoption of object-oriented techniques in academic computer science programs. This project addresses practical concerns of the computer science and software engineering communities in using, teaching, and learning patterns. In this paper we argue that patterns are an essential programming and pedagogical tool and report on our work in making them accessible to the educational community.Keywords
This publication has 19 references indexed in Scilit:
- Animation, visualization, and interaction in CS 1 assignments1998
- Teaching OOP in C++ using an artificial life framework1997
- Strategic directions in computer science educationACM Computing Surveys, 1996
- The interaction of social issues and software architectureCommunications of the ACM, 1996
- A training experience with patternsCommunications of the ACM, 1996
- The pros and cons of adopting and applying design patterns in the real worldCommunications of the ACM, 1996
- Self-reference is an illustrative essential1994
- Supporting Pascal programming with an on-line template library and case studiesInternational Journal of Man-Machine Studies, 1993
- ET++—an object oriented application framework in C++ACM SIGPLAN Notices, 1988
- Learning to program = learning to construct mechanisms and explanationsCommunications of the ACM, 1986