did-you-know? rent-now

Amazon no longer offers textbook rentals. We do!

did-you-know? rent-now

Amazon no longer offers textbook rentals. We do!

We're the #1 textbook rental company. Let us show you why.

9780201607345

Pattern Languages of Program Design

by ;
  • ISBN13:

    9780201607345

  • ISBN10:

    0201607344

  • Edition: 1st
  • Format: Paperback
  • Copyright: 1995-05-02
  • Publisher: Addison-Wesley Professional
  • Purchase Benefits
  • Free Shipping Icon Free Shipping On Orders Over $35!
    Your order must be $35 or more to qualify for free economy shipping. Bulk sales, PO's, Marketplace items, eBooks and apparel do not qualify for this offer.
  • eCampus.com Logo Get Rewarded for Ordering Your Textbooks! Enroll Now
List Price: $54.99

Summary

The first conference on Pattern Languages of Program Design (PLoP)was a watershed event that gave a public voice to the software designpattern movement. Seventy software professionals from around theworld worked together to capture and refine software experience thatexemplifies the elusive quality called "good design." This volume isthe result of that work--a broad compendium of this new genre ofsoftware literature. Patterns are a literary form that take inspiration from literateprogramming, from a design movement of the same name in contemporaryarchitecture, and from the practices common to the ageless literatureof any culture. The goal of pattern literature is to help programmersresolve the common difficult problems encountered in design andprogramming. Spanning disciplines as broad as client/serverprogramming, distributed processing, organizational design, softwarereuse, and human interface design, this volume encodes designexpertise that too often remains locked in the minds of expertarchitects. By capturing these expert practices as problem-solutionpairs supported with a discussion of the forces that shape alternativesolution choices, and rationales that clarify the architects' intents,these patterns convey the essence of great software designs. 0201607344B04062001

Author Biography

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.

Table of Contents

"Night Patterns"p. iii
Introductionp. ix
Prefacep. xi
Frameworks and Components
Functionality Ala Cartep. 7
A Pattern Language for Tool Construction and Integration Based on the Tools and Materials Metaphorp. 9
Flexible Command Interpreter: A Pattern for an Extensible and Language-Independent Interpreter Systemp. 43
New Clients with Old Servers: A Pattern Language for Client/Server Frameworksp. 51
Systems and Distributed Processing
A Generative Pattern Language for Distributed Processingp. 69
G++: A Pattern Language for Computer-Integrated Manufacturingp. 91
Patterns for Generating a Layered Architecturep. 119
Pattern: Half-object+Protocol (HOPP)p. 129
The Master-Slave Patternp. 133
Business Objects
The CHECKS Pattern Language of Information Integrityp. 145
Account Number: A Patternp. 157
Stars: A Pattern Language for Query-Optimized Schemasp. 163
Process and Organization
A Generative Development-Process Pattern Languagep. 183
Lifecycle and Refactoring Patterns That Support Evolution and Reusep. 239
RAPPeL: A Requirements-Analysis-Process Pattern Language for Object-Oriented Developmentp. 259
Caterpillar's Fate: A Pattern Language for the Transformation from Analysis to Designp. 293
Design Patterns and Catalogs
A System of Patternsp. 325
Relationships Between Design Patternsp. 345
Discovering Patterns in Existing Applicationsp. 365
Implementing Patternsp. 395
Architecture and Communication
Streams: A Pattern for "Pull-Driven" Processingp. 417
The Pipes and Filters Architecturep. 427
Pattern-Based Integration Architecturesp. 441
Patterns for Software Architecturesp. 453
Object Usage and Style
Understanding and Using the ValueModel Framework in VisualWorks Smalltalkp. 467
Client-Specified Selfp. 495
Reusability Through Self-Encapsulationp. 505
Events and Event Handlers
A Pattern for Separating Assembly and Processingp. 521
Reactor: An Object Behavioral Pattern for Concurrent Event Demultiplexing and Event Handler Dispatchingp. 529
Patterns of Eventsp. 547
Request Screen Modificationp. 555
Indexp. 557
Table of Contents provided by Syndetics. All Rights Reserved.

Supplemental Materials

What is included with this book?

The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.

The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.

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 aCACMarticle 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.'sDesign Patterns1995 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 inObject Models: Strategies, Patterns, and ApplicationsCoad 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 pass

Rewards Program