Available:*
Library | Item Barcode | Call Number | Material Type | Item Category 1 | Status |
---|---|---|---|---|---|
Searching... | 30000003820242 | QA76.76.D47 P38 1995 | Open Access Book | Book | Searching... |
On Order
Summary
Summary
Design patterns is the most significant emerging area in the field of object-oriented technology. This work provides an overview of current approaches as well as practical guidelines for their use in software design. It builds a conceptual and terminological base and goes on to discuss how design patterns constitute a minimal yet sufficient means to meet the goal of capturing and communicating the design of complex object-oriented systems.
Author Notes
James O. Coplien is a member of the Software Production Research Department at ATandT Bell Laboratories. His research interests focus on multiparadigm development methods and organizational anthropology for software development processes. Douglas C. Schmidt is a faculty member at the computer science department at Washington University in St. Louis, Missouri. His research interests focus on experimental techniques to develop object-oriented parallel communication systems for high-speed networks.
Excerpts
Excerpts
This book is the culmination of an intensive effort to capture and refine a broad range of software development expertise in a systematic and highly accessible manner. The chapters are based on papers presented at the First Annual Conference of Pattern Languages of Programming (PLoP) held near Monticello, Illinois, in August 1994. This book is more than just a compendium of conference papers, however. It represents a broad offering from a new body of literature focusing on object-oriented design patterns. It is the first in a series of similar edited works on an ever-broadening spectrum of software patterns and pattern languages. Design patterns capture the static and dynamic structures of solutions that occur repeatedly when producing applications in a particular context. Because they address fundamental challenges in software system development, design patterns are an important technique for improving the quality of software. Key challenges addressed by design patterns include communication of architectural knowledge among developers, accommodating a new design paradigm or architectural style, and avoiding development traps and pitfalls that are usually learned only by (painful) experience. A large body of pattern literature already exists--not for software, but for constructing buildings. Christopher Alexander refined his architectural pattern form over 15 years ago, and isolated references to architectural patterns go back hundreds of years. Patterns have taken root in software only recently. Peter Coad noted the link between Alexandrian patterns and software architecture in a CACM article in 1992 Coad 1992. It wasn't until 1993 that patterns began to enter the vernacular as the result of seminars, conference sessions, and journal publications. Drafts of Erich Gamma et al.'s Design Patterns 1995 were widely circulated in 1993 and 1994. This landmark work offered the first comprehensive set of software patterns between two covers, and set new standards for the pattern form. Peter Coad's more recent work has culminated in Object Models: Strategies, Patterns, and Applications Coad 1995. A fledgling body of diverse literature precedes the patterns collected in this volume. As you examine the contents of the book carefully, you will observe a rich diversity of pattern forms. Some patterns draw on Alexander's style; others draw on the work of Erich Gamma and his colleagues; still others draw on the patterns of Peter Coad; and several are altogether original. We made every effort to preserve the authors' original forms. We avoided tampering with individual expression as much as possible: we made no attempt to enforce a uniform writing style. Although the book lacks the voice of a single author, we wouldn't have it any other way. We hope you join us in celebrating this diversity in the formative stage of a new body of literature. The chapters in this book are certainly among the most intensely edited works in contemporary software literature. Editing was an ongoing, iterative effort. Before the conference, authors worked with "shepherds" from the patterns community. The goal was for each pattern to contain bare essentials: a clear problem statement, a solution addressing the problem, and a clear statement of forces that motivate the solution. Then, each chapter underwent intensive editing in writers' workshops at the PLoP '94 conference. Authors, reviewers, and other workshop participants discussed the strengths and weaknesses of each paper. Reviewers were encouraged to accentuate the positive and to suggest improvements in content, style, and presentation. Production editing was also a team effort. Discussions with our colleagues in The Hillside Group steered early editorial decisions. While we focused on the logical organization of the material, our friends at Addison-Wesley created a unified design, swept out passive verbs and dangling prepositions, and richly supported us with logistics, copyright negotiation, and a host of details. Despite our scholarly inclinations to the contrary, page design and formatting contribute greatly to the readability of any written material. Thus, although we received manuscripts in a wide variety of formats, we have tried to integrate them in a single design while preserving the spirit of individual formats. We simply couldn't have done this without Deborah Lafferty, Penny Stratton, and Tom Stone, who treated this book with the same care and attention as if it were their own. We were proud and pleased--but most of all desparately grateful--to have them on our team. Finally, we want to emphasize that this book would not have been possible without the talents, hard work, and dedication of the authors. All the copy editing in the world doesn't take the place of high-quality material. We are honored to work in the company of outstanding authors. Coad92Coad, Peter.Object-oriented patterns.CACM 35, 9 (Sept. 1992), 152-159. Coad95Coad, Peter, with David North and Mark Mayfield.Object Models: Strategies, Patterns, and Applications.Prentice-Hall: c1995. Gamma95Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides.Design patterns: Elements of Reusable Object-Oriented Software.Reading, MA: Addison-Wesley, c1995. 0201607344P04062001 Excerpted from Pattern Languages of Program Design by James O. Coplien, Douglas C. Schmidt All rights reserved by the original copyright owners. Excerpts are provided for display purposes only and may not be reproduced, reprinted or distributed without the written permission of the publisher.Table of Contents
"Night Patterns" | p. iii |
Introduction | p. ix |
Preface | p. xi |
1 Frameworks and Components | |
1 Functionality Ala Carte | p. 7 |
2 A Pattern Language for Tool Construction and Integration Based on the Tools and Materials Metaphor | p. 9 |
3 Flexible Command Interpreter: A Pattern for an Extensible and Language-Independent Interpreter System | p. 43 |
4 New Clients with Old Servers: A Pattern Language for Client/Server Frameworks | p. 51 |
2 Systems and Distributed Processing | |
5 A Generative Pattern Language for Distributed Processing | p. 69 |
6 G++: A Pattern Language for Computer-Integrated Manufacturing | p. 91 |
7 Patterns for Generating a Layered Architecture | p. 119 |
8 Pattern: Half-object+Protocol (HOPP) | p. 129 |
9 The Master-Slave Pattern | p. 133 |
3 Business Objects | |
10 The CHECKS Pattern Language of Information Integrity | p. 145 |
11 Account Number: A Pattern | p. 157 |
12 Stars: A Pattern Language for Query-Optimized Schemas | p. 163 |
4 Process and Organization | |
13 A Generative Development-Process Pattern Language | p. 183 |
14 Lifecycle and Refactoring Patterns That Support Evolution and Reuse | p. 239 |
15 RAPPeL: A Requirements-Analysis-Process Pattern Language for Object-Oriented Development | p. 259 |
16 Caterpillar's Fate: A Pattern Language for the Transformation from Analysis to Design | p. 293 |
5 Design Patterns and Catalogs | |
17 A System of Patterns | p. 325 |
18 Relationships Between Design Patterns | p. 345 |
19 Discovering Patterns in Existing Applications | p. 365 |
20 Implementing Patterns | p. 395 |
6 Architecture and Communication | |
21 Streams: A Pattern for "Pull-Driven" Processing | p. 417 |
22 The Pipes and Filters Architecture | p. 427 |
23 Pattern-Based Integration Architectures | p. 441 |
24 Patterns for Software Architectures | p. 453 |
7 Object Usage and Style | |
25 Understanding and Using the ValueModel Framework in VisualWorks Smalltalk | p. 467 |
26 Client-Specified Self | p. 495 |
27 Reusability Through Self-Encapsulation | p. 505 |
8 Events and Event Handlers | |
28 A Pattern for Separating Assembly and Processing | p. 521 |
29 Reactor: An Object Behavioral Pattern for Concurrent Event Demultiplexing and Event Handler Dispatching | p. 529 |
30 Patterns of Events | p. 547 |
Appendix Request Screen Modification | p. 555 |
Index | p. 557 |