Pattern languages of program design 3 / edited by Robert C. Martin, Dirk Riehle, Frank Buschmann.

Contributor(s): Martin, Robert C | Riehle, Dirk, 1969- | Buschmann, Frank .

Material type: materialTypeLabel

BookSeries: Software patterns series: Publisher: Reading, MA : Addison-Wesley, 1998Description: xviii, 632 p. : ill. ; 24 cm + pbk.ISBN: 0201310112 (acidfree paper).Subject(s): Computer software -- Development

| Object-oriented programming (Computer science)

| Software patterns

DDC classification: 005.12

Contents:

Part 1: General Purpose Design Patterns -- Part 2: Variations on Design Patterns -- Part 3: Architectural Patterns -- Part 4: Distribution Patterns -- Part 5: Persistence Patterns -- Part 6: User Interface Patterns -- Part 7: Programming Patterns -- Part 8: Domain-Specific Patterns -- Part 9: Process Patterns -- Part 10: Patterns on Patterns.

Holdings
Item type	Current library	Call number	Copy number	Status	Date due	Barcode	Item holds
General Lending	MTU Bishopstown Library Lending	005.12 (Browse shelf(Opens below))	1	Available		00086053
General Lending	MTU Bishopstown Library Lending	005.12 (Browse shelf(Opens below))	1	Available		00086052

Total holds: 0

Enhanced descriptions from Syndetics:

A collection of current best practices and trends in reusable design patterns in software engineering, system design, and development, providing tested software design solutions for developers in all domains and organizations. Patterns are arranged by topic, with sections on general purpose design patterns and variations, and architectural, distribution, persistence, user-interface, programming, domain-specific, and process patterns, with a final chapter on a pattern language for pattern writing. Based on papers from American and European conferences held in 1996. Annotation copyrighted by Book News, Inc., Portland, OR

Includes bibliographical references and index.

Table of contents provided by Syndetics

I Language-Specific Patterns And Idioms
1 Localized Ownership: Managing Dynamic Objects in C++
2 Lazy Optimization: Patterns for Efficient Smalltalk Programming
3 Partitioning Smalltalk Code into ENVY/Developer Components.
II General-Purpose Patterns
4 Command Processor
5 Implementation Patterns for the Observer Pattern
6 Patterns for Encapsulating Class Trees
7 The Proxy Design Pattern Revisited
8 Moods: Models for Object-Oriented Design of State
9 Shopper
III Special-Purpose Patterns
10 Detachable Inspector/Removable: A Structural Pattern for Designing Transparent Layered Services
11 Design Patterns for Object-Oriented Hypermedia Applications
12 Organizational Multiplexing: Patterns for Processing Satellite Telemetry with Distributed Teams
13 Backup Pattern: Designing Redundancy in Object-Oriented Software
14 Crossing Chasms: A Pattern Language for Object-RDBMS Integration
15 Transactions and Accounts
IV Architectural Patterns
16 Some Patterns for Software Architectures
17 Reflection
18 Evolution, Architecture, and Metamorphosis
V Process And Organization
19 Prioritizing Forces in Software Design
20 Decision Deferral and Capture Pattern Language
21 Organizational Patterns for Teams
22 Accountability and Organizational Structures
23 Episodes: A Pattern Language of Competitive Development
VI Exposition
24 Patterns for Classroom Education
25 Demo Prep: A Pattern Language for the Preparation of Software Demonstrations
26 A Pattern Language for an Essay-Based Web Site
VII Concurrent Programming/Distributed Systems
27 Half-Sync/Half-Async: An Architectural Patte

Excerpt provided by Syndetics

This is the third in the series of PLoPD books; and it represents something of a departure from the previous two. This is the first book in the PLoPD series in which fewer than half of the papers submitted at the corresponding PLoP conferences have been published. This is also the first PLoPD book in which papers from more than one conference have been published. There were over 80 papers submitted to PLoP '96 and EuroPLoP '96 and there was no way that we could publish them all. Therefore we had the unhappy task of deciding which of those papersnotto publish. This task was not easy since all the papers submitted were of very high quality (Something we have come to expect from the PLoP conferences). Fortunately, our burden was lightened by all the folks who helped out with the review and selection process. The process of creating this book. We recruited a veritable army of reviewers, and each of the 80+ papers was reviewed by three of them. The reviewers' recommendations were then passed on to the three editors (Dirk Riehle, Frank Buschmann, and Robert Martin). Then began a rather long and heated exchange between us. None of us had any problem being choosy; and, indeed, the three of us settled on a large core of papers to be published. But there were a few papers that we did not agree upon. And thereupon laid the long and arduous process of defining the final contents of this book. None of us think that this book is perfect; but all of us think that it is a top-notch collection of superb papers.What were our selection criteria? The choice of papers was constrained by our target audience:software engineers. First and foremost the papers in this volume had to be of interest to this audience. Although patterns about music are interesting to musicians, we did not think that they should be included here. Secondly, the papers had to be of practical value to our audience. Although papers of abstract theory are certainly interesting, we gave preference to papers that provided techniques or tools that would be of immediate use to our audience. Finally, the papers should be patterns. There were lots of good papers that were written about software engineering, but we gave preference to those that described patterns related to software engineering.To be sure, these criteria were not unambiguously stated up front. Like all high quality projects, the requirements evolved during development. It was during the book definition process that we learned about each other's expectations and visions for the book. And it was during this process that our own expectations and visions were changed through discussion and argument. All in all, it was a very rewarding, if somewhat exhausting, experience.In the spirit of Ralph Johnson's suggestion to catalog patterns as design specimens, just like biology catalogs and classifies its animal and non-animal specimens, we organized the book by topic. It comprises general design patterns as well as patterns for specific technical or business domains. It also contains patterns for designing user interfaces, and helping with software processes; it even contains a chapter with patterns for writing patterns. We did not distinguish between patterns and pattern languages, but focussed on putting together patterns by topic so that you can take a look and see whether these patterns are of interest to your needs and your application domains. Design Patterns, a 1997 perspective. It has been two years since the publication of the GoF book. During that time interest in design patterns has increased at a phenomenal rate. Today it is very unlikely that any serious software is ignorant of the concept of design patterns. There are major magazines that run regular columns about design patterns. The C++ Report runs a monthlysectionabout design patterns. There are several other books by major authors that have been published on the topic of design p Excerpted from Pattern Languages of Program Design by John Vlissides, Frank Buschmann, Robert C. Martin, Dirk Riehle 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.

Author notes provided by Syndetics

Robert C. Martin has been a software professional since 1970 and an international software consultant since 1990. He is founder and president of Object Mentor, Inc., a team of experienced consultants who mentor their clients in the fields of C++, Java, OO, Patterns, UML, Agile Methodologies, and Extreme Programming.

Dirk Riehle is a software engineer at Ubilab. He is involved in the Geo project, which is setting up a reflective distributed object-oriented software architecture.

Frank Buschmann is a software engineer at Siemens, where he focuses on object-oriented technology, software reuse, and patterns. He is a member of the ANSI C++ standards committee.