A Report on the ChiliPLoP98 Hot Topic Workshop
by Eugene Wallingford Helping novice students learn how to write programs well is a difficult task. Students must learn, among other things, how to use a programming language; how to create readable, modifiable code; how to evaluate the quality of programs; and how to modify existing code. One way for us to help them is to have them study and use the patterns of good programs, just as experts do. Six educators interested in the use of patterns in the undergraduate computer science curriculum gathered for an intensive three-day workshop at ChiliPLoP'98 to consider this possibility. This report describes the origin of the Elementary Patterns workshop, the work done at the workshop, and some of the lessons that we learned. I also outline some of the post-workshop activities intended to help develop further the idea of elementary patterns in computer science education.
Keywords
Background on the Conference The patterns community runs a series of annual conferences called Pattern Languages of Programming (PLoP), at which pattern authors share and improve their work through writers workshops. The environment at PLoP is supportive and relaxed--but the conference focuses on improving the presentation of documented patterns. It provides only informal support for groups of practitioners interested in working together to explore the patterns of a specific domain. The organizers of ChiliPLoP'98 sought to provide an environment for such collaborative exploration. Billed as a "different kind of PLoP", ChiliPLoP offered two tracks. In the newcomer track, self-professed patterns novices worked with expert patterns trainers to learn how to find and write patterns. In "hot topic" track, small groups of domain experts worked on the discovery, use, and application of patterns in their domains. Groups worked in the areas of telecommunications, software organizations, software configuration management, and patterns of time in information. A fifth hot topic workshop was titled "Elementary Patterns and their Role in Instruction". This workshop explored the teaching side of patterns, especially patterns appropriate for novices first learning to design and write programs. We call such patterns elementary patterns.
Background on the Topic Computer science (CS) educators face an extreme form of this problem. Their students begin with little or no experience and hope to learn the art of computer programming. How can CS faculty help them to learn to use a programming language, create readable, modifiable code, evaluate the quality of programs, and modify existing code? Patterns may help to provide a culture for novices learning how to program. Ultimately, the software patterns movement is about communication: experienced developers documenting for their benefit and for the benefit of others the art of building software systems. As CS educators, we hope to communicate the knowledge, methodology, and culture of computer science. Perhaps patterns can help teachers communicate the art of building software systems to undergraduate students. Out of this idea grew the motivation for the Elementary Patterns workshop at ChiliPLoP. Over the last few years, activity in both the patterns community and the CS education community have demonstrated that many practitioners and academics were interested in the idea of elementary patterns. In the patterns community, patterns at a level appropriate for relative novices have become more common. For example, many of Kent Beck's Smalltalk Best Practice Patterns [3] document ideas and techniques that we teach in object-oriented (OO) programming courses. Ken Auer's self-encapsulation patterns [2] walk a class designer through the process of creating robust, reusable classes. At the PLoP'97 conference, James Noble presented patterns of relationships among objects [9] and patterns of method signatures [8]. At the same time, CS academics themselves were beginning to explore the use of patterns in their courses. This exploration was a natural outgrowth of earlier work, in the same spirit as patterns, by people such as Soloway [11] and Linn and Clancey [6]. An example of academic patterns work is Roundabout, my recursive programming pattern language reviewed at PLoP'97 [12]. I use Roundabout to teach students how to write recursive programs in a functional programming language and to teach the basics of recursion in my data structures course. The 1998 SIGCSE Technical Symposium featured a number of papers on patterns and their uses in early CS courses. Astrachan described One Loop for Linear Structures [1], a pattern of loops that operate on linear data structures. Nguyen [7] and Goodrich et al. [5] reported the use of several patterns from Design Patterns [4] to teach data structures. On a slightly different note, Reed [10] described the use of a binary reduction pattern as an organizing theme for his CS1 course. These patterns and uses of patterns indicated that elementary patterns were indeed a hot topic among practitioners and CS academics. ChiliPLoP'98 offered a convenient setting for a group of people to explore the domain more deeply.
Leading up to the Workshop The workshop's call for participation asked prospective participants to submit (1) a description of a course they teach using patterns, either in academia or industry, (2) a proposed elementary pattern language or catalog for teaching some topic to novices, or (3) a draft outline of an elementary textbook organized around patterns. We had hoped to receive requests to participate from practitioners and industry trainers as well as CS academics, but all applicants were full-time faculty members. On the basis of the submissions received, we selected six people were to participated in the three-day Elementary Patterns workshop:
Not only were all six participants computer science educators, but they were also all experienced in and deeply interested in the first-year courses typically taught to undergraduate CS students. This common interest provided a natural focus for the workshop. Prior to meeting at ChiliPLoP, we read each others' submissions and previous patterns papers. We also began to formulate a list of open questions relevant to the workshop. Among these questions were:
Another, somewhat more sociological question also arose: How can our efforts working on and with elementary patterns help educators unfamiliar with patterns see past the hype to the value that patterns bring to software development and understanding? This remains an important concern as people begin to explore elementary patterns more deeply.
Activities at the Workshop We then split into two groups for focused pattern mining and writing. One group (Astrachan, Mercer, and me) began to develop of a set of patterns for writing loops. Another group (Bergin, Duvall, and Epp) explored issues in object-oriented design.
Loops Group
Object Design Group
Recommendations Ultimately, the goal of work on elementary patterns is to transform courses from "learning C++" or "learning Java" to learning how to program. By this we mean to integrate a higher-level of thinking about programs into the first-year courses. Bergin sometimes refers to this as system-level thinking. Ultimately, students will be the users of the patterns and pattern languages that we document. At least initially, though, CS faculty members comprise an important audience, too. To the extent that the use of patterns opens new avenues for programming instruction, the roles and methods of the instructors must change. Questions of pedagogy will likely remain critical even after we are able to demonstrate an effective pattern language of programming to our students. As we begin to write elementary patterns, we must resist the temptation to "create" patterns, to write new solutions with which we have no experience. Certainly, there is a place for innovation, but that is not the role of patterns. Instead, we want to identify patterns of good programs that our students write and identify how they fit together to form a program. One way to resist the temptation to innovate is to begin with a focus on problems that our students encounter. Focus on concrete problems that students face--start with a specific programming assignment and specific code, both good and bad solutions. At the same time, resist the urge to "go meta-" too early. Over-abstraction can dull a student's attention to the subtleties of a problem and interfere with understanding the pattern. Finally, we must consider to what extent, if at all, we need to change the form of our patterns and pattern languages in order to incorporate additional pedagogical material, such as exercises or extra discussion of the forces and consequences of the pattern.
Beyond the Workshop
The members of the workshop intends to carry on the work begun at ChiliPLoP in a variety of ways. Here is a brief list to start:
We sincerely hope that others in the patterns community, the academic CS community, and the OO practitioner community will join is in the effort to improve undergraduate computer science education. Some believe that the use of patterns and pattern languages could lead to a radically different way of teaching computer science. If you are interested in any way, please visit the Elementary Patterns home page, subscribe to the discussion list, and join us!
Acknowledgements I thank the participants of the Elementary Patterns workshop for their help with this report, especially Joe Bergin, who wrote an early workshop report draft from which I borrowed liberally. We all thank Linda Rising and the folks behind ChiliPLoP'98--a first-rate event in a first-rate location. References
Note: PLoP is a trademark of The Hillside Group, Inc.
|