Pattern Languages of Program Design 4

Overview

Design patterns have moved into the mainstream of commercial software development as a highly effective means of improving the efficiency and quality of software engineering, system design, and development. Patterns capture many of the best practices of software design, making them available to all software engineers.. "This book covers a wide range of topics, with patterns in the areas of object-oriented infrastructure, programming strategies, temporal patterns, security, domain-oriented patterns, human-computer...
See more details below
Available through our Marketplace sellers.
Other sellers (Paperback)
  • All (7) from $37.40   
  • New (2) from $122.04   
  • Used (5) from $37.40   
Close
Sort by
Page 1 of 1
Showing All
Note: Marketplace items are not eligible for any BN.com coupons and promotions
$122.04
Seller since 2010

Feedback rating:

(30)

Condition:

New — never opened or used in original packaging.

Like New — packaging may have been opened. A "Like New" item is suitable to give as a gift.

Very Good — may have minor signs of wear on packaging but item works perfectly and has no damage.

Good — item is in good condition but packaging may have signs of shelf wear/aging or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Acceptable — item is in working order but may show signs of wear such as scratches or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Used — An item that has been opened and may show signs of wear. All specific defects should be noted in the Comments section associated with each item.

Refurbished — A used item that has been renewed or updated and verified to be in proper working condition. Not necessarily completed by the original manufacturer.

New
0201433044 PAPERBACK. NEW. Never used. We do not ship to PO Box/APO/FPO addresses.

Ships from: Cupertino, CA

Usually ships in 1-2 business days

  • Canadian
  • International
  • Standard, 48 States
  • Standard (AK, HI)
  • Express, 48 States
  • Express (AK, HI)
$195.00
Seller since 2014

Feedback rating:

(136)

Condition: New
Brand new.

Ships from: acton, MA

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
Page 1 of 1
Showing All
Close
Sort by
Sending request ...

Overview

Design patterns have moved into the mainstream of commercial software development as a highly effective means of improving the efficiency and quality of software engineering, system design, and development. Patterns capture many of the best practices of software design, making them available to all software engineers.. "This book covers a wide range of topics, with patterns in the areas of object-oriented infrastructure, programming strategies, temporal patterns, security, domain-oriented patterns, human-computer interaction, reviewing, and software management.
Read More Show Less

Editorial Reviews

Booknews
Documents design patterns for professional software developers. Chapters were originally presented at recent Pattern Languages of Programming (PLoP) conferences, and provide tested, versatile software design solutions for solving real-world problems in a variety of domains. Coverage encompasses object-oriented infrastructure, programming strategies, temporal patterns, security, domain-oriented patterns, human-computer interaction, and software management. The author is a consultant in telephony, software testing, and domain engineering. Annotation c. Book News, Inc., Portland, OR (booknews.com)
Read More Show Less

Product Details

  • ISBN-13: 9780201433043
  • Publisher: Addison Wesley Professional
  • Publication date: 12/23/1999
  • Series: Software Patterns Series
  • Edition number: 1
  • Pages: 784
  • Product dimensions: 7.49 (w) x 9.18 (h) x 1.56 (d)

Read an Excerpt

PREFACE:

Of Phish and Phugues

The year is 1621; the place, Plymouth, in what will eventually become Massachusetts. A group of settlers from England arrived the previous November and are now setting out to plant crops. Before long a native named Squanto stops by. Evidently a gardening enthusiast, he offers to tutor the settlers in farming techniques, first by placing fish in the ground to enrich the soil. This and other tricks of farming in the New World contribute to a bountiful harvest. The settlers survive the ensuing winter, thanks in large part to Squanto and his sage advice.

An apocryphal story, no doubt, but modern horticulturists can corroborate Squanto's fishy insights. In fact, you can buy fish fertilizers in many gardening stores. Our agricultural forebears may not have had a deep knowledge of plant physiology, but they knew what worked. And they passed it along.

Over a hundred years later and half a world away, in what is now Germany, a master of a different sort plies his trade. According to legend, Johann Sebastian Bach pays a visit to Frederick the Great, King of Prussia. After exchanging pleasantries, the king asks Bach to play something for him. Dutifully and without hesitation, Bach sits down at the organ and improvises a five-part fugue. The king, an eminent composer himself, is awed.

Bach's work is the very essence of baroque music. And he passes that mastery along—several of his children also become important musicians and composers.

Lore flows from one generation to the next. Languages are vivid examples, perpetuating and evolving through oral tradition—words and concepts passing from person toperson. A case in point is English, which traces its roots to numerous languages, including German, Greek, and Latin. Herein lies a problem: the multifaceted heritage of English creates a potpourri of spelling conventions that is downright bewildering. For example, we spell the "f" sound with the letters "ph" in "physics" but with "f" in "fish" and "fugue." There are historical and linguistic reasons for such anomalies, but they don't matter much to us. We just memorize that it's "fugue," not "phugue."

In software we don't have centuries of history to draw on. We didn't learn agriculture from ancient farmers, nor can we trace our roots through the Middle English of Chaucer. But we have been around long enough to learn a few things. The most important among them is this: We must share what we have learned. If we keep knowledge to ourselves, hoarding it like pack rats, then our field will surely stagnate. We doom colleague and successor alike to repeat our mistakes. Gradually, reinvention displaces innovation. Progress slows. The field goes fallow.

Patterns are conduits of knowledge, capturing and conveying time-proven practices. Patterns are more than tricks or seemingly arbitrary spelling rules—they impart understanding. They teach you not just what and how but also why and when. That's where their real power lies.

What can we reasonably expect of patterns? Maybe they will help other people develop better software than we have. Maybe they'll allow people to build on what we've done right. We certainly hope patterns will help others avoid the pitfalls we've experienced.

But we can expect more. The pervasiveness of computer technology exerts a strong influence on society. Influence of such magnitude must be exercised responsibly. While patterns won't force you to act responsibly, they can ease the grind of reinvention, freeing you to consider higher purposes. Ultimately, patterns make life better for everyone—software user and developer alike.

These are ambitious and humbling goals, to be sure. We dedicate this fourth volume in the Pattern Languages of Program Design series to their attainment.

ACKNOWLEDGMENTS

Now for a word about the contributors to this book. A compendium of this size won't come together without many people pulling together. We are hugely grateful for their work. Specifically, we thank the authors for making this book necessary, to paraphrase Yogi Berra. We're referring not just to the authors you find here but also to the 60 percent or so of submitters whose works were not accepted. The exceptionally high quality of the submissions guaranteed the quality of the book, although it also made our job more difficult!

We recruited a veritable army of reviewers to help sift through the submissions. We owe them our sanity: Francis Anderson, Brad Appleton, Jorge Arjona, Owen Astrannen, Ken Auer, Jeff Barcalow, Kent Beck, Mike Beedle, Steve Berczuk, Manish Bhatt, Rosana Braga, John Brant, Kyle Brown, Jose Burgos, Frank Buschmann, Andy Carlson, Ian Chai, Alistair Cockburn, Jens Coldewey, James Coplien, Ward Cunningham, David Cymbala, Fonda Daniels, Dennis DeBruler, Michel DeChamplain, David Delano, Dwight Deugo, Paul Dyson, Philip Eskelin, Javier Galve, Julio Garcia, Alejandra Garrido, John Goodsen, Robert Hanmer, Kevlin Henney, Robert Hirschfeld, Ralph Johnson, Wolfgang Keller, Elizabeth Kendall, Norm Kerth, Charles Knutson, Frederick Koh, Philippe Lalanda, Manfred Lange, Doug Lea, Mary Lynn Manns, Klaus Marquardt, Paulo Masiero, Skip McCormick, Regine Meunier, Oscar Nierstrasz, James Noble, Alan O'Callaghan, Don Olson, William Opdyke, Dorina Petriu, Irfan Pyarali, Andreas Rausch, Dirk Riehle, Linda Rising, Antonio Rito Silva, Don Roberts, Gustavo Rossi, Cecilia Rubira, Andreas Ruping, Doug Schmidt, Ari Schoenfeld, Dietmar Schutz, Christa Schwanninger, Joe Seda, Peter Sommerlad, Michael Stal, Paul Taylor, Jenifer Tidwell, Dwayne Towell, and David Ungar.

We would like to give special thanks to John Vlissides, the managing editor of the series. He has provided us with encouragement and, occasionally, a needed prod. Neil would like to especially thank his two coeditors. Working with you has been a joy.

Finally, we would like to give special thanks to our families, friends, and coworkers who have supported us through this process. We hope that by the time you read this, we will be back to our cheery selves.

Neil Harrison, Boulder, Colorado
Brian Foote, Urbana, Illinois
Hans Rohnert, Munich, Germany


Read More Show Less

Table of Contents

Preface
Introduction I
Introduction II
Pt. 1 Basic Object-Oriented Patterns
1 Abstract Class 5
2 Role Object 15
3 Essence 33
4 Object Recursion 41
5 Prototype-Based Object System 53
6 Basic Relationship Patterns 73
Pt. 2 Object-Oriented Infrastructure Patterns
7 Abstract Session: An Object Structured Pattern 95
8 Object Synchronizer 111
9 Proactor 133
Pt. 3 Programming Strategies
10 C++ Idioms 167
11 Smalltalk Scaffolding Patterns 199
12 High-Level and Process Patterns from the Memory Preservation Society: Patterns for Managing Limited Memory 221
Pt. 4 Time
13 Temporal Patterns 241
14 A Collection of History Patterns 263
Pt. 5 Security
15 Architectural Patterns for Enabling Application Security 301
16 Tropyc: A Pattern Language for Cryptographic Object-Oriented Software 337
Pt. 6 Domain-Oriented Patterns
17 Creating Reports with Query Objects 375
18 Feature Extraction: A Pattern for Information Retrieval 391
19 Finite State Machine Patterns 413
Pt. 7 Patterns of Human-Computer Interaction
20 Patterns for Designing Navigable Information Spaces 445
21 Composing Multimedia Artifacts for Reuse 461
22 Display Maintenance: A Pattern Language 489
23 An Input and Output Pattern Language: Lessons from Telecommunications 503
Pt. 8 Reviewing
24 Identify the Champion: An Organizational Pattern Language for Program Committees 539
25 A Pattern Language for Writers' Workshops 557
Pt. 9 Managing Software
26 Customer Interaction Patterns 585
27 Capable, Productive, and Satisfied: Some Organizational Patterns for Protecting Productive People 611
28 SCRUM: A Pattern Language for Hyperproductive Software Development 637
29 Big Ball of Mud 653
About the Authors 693
Index 705
Read More Show Less

Preface

Of Phish and Phugues

The year is 1621; the place, Plymouth, in what will eventually become Massachusetts. A group of settlers from England arrived the previous November and are now setting out to plant crops. Before long a native named Squanto stops by. Evidently a gardening enthusiast, he offers to tutor the settlers in farming techniques, first by placing fish in the ground to enrich the soil. This and other tricks of farming in the New World contribute to a bountiful harvest. The settlers survive the ensuing winter, thanks in large part to Squanto and his sage advice.

An apocryphal story, no doubt, but modern horticulturists can corroborate Squanto's fishy insights. In fact, you can buy fish fertilizers in many gardening stores. Our agricultural forebears may not have had a deep knowledge of plant physiology, but they knew what worked. And they passed it along.

Over a hundred years later and half a world away, in what is now Germany, a master of a different sort plies his trade. According to legend, Johann Sebastian Bach pays a visit to Frederick the Great, King of Prussia. After exchanging pleasantries, the king asks Bach to play something for him. Dutifully and without hesitation, Bach sits down at the organ and improvises a five-part fugue. The king, an eminent composer himself, is awed.

Bach's work is the very essence of baroque music. And he passes that mastery along—several of his children also become important musicians and composers.

Lore flows from one generation to the next. Languages are vivid examples, perpetuating and evolving through oral tradition—words and concepts passing from person to person. Acase in point is English, which traces its roots to numerous languages, including German, Greek, and Latin. Herein lies a problem: the multifaceted heritage of English creates a potpourri of spelling conventions that is downright bewildering. For example, we spell the "f" sound with the letters "ph" in "physics" but with "f" in "fish" and "fugue." There are historical and linguistic reasons for such anomalies, but they don't matter much to us. We just memorize that it's "fugue," not "phugue."

In software we don't have centuries of history to draw on. We didn't learn agriculture from ancient farmers, nor can we trace our roots through the Middle English of Chaucer. But we have been around long enough to learn a few things. The most important among them is this: We must share what we have learned. If we keep knowledge to ourselves, hoarding it like pack rats, then our field will surely stagnate. We doom colleague and successor alike to repeat our mistakes. Gradually, reinvention displaces innovation. Progress slows. The field goes fallow.

Patterns are conduits of knowledge, capturing and conveying time-proven practices. Patterns are more than tricks or seemingly arbitrary spelling rules—they impart understanding. They teach you not just what and how but also why and when. That's where their real power lies.

What can we reasonably expect of patterns? Maybe they will help other people develop better software than we have. Maybe they'll allow people to build on what we've done right. We certainly hope patterns will help others avoid the pitfalls we've experienced.

But we can expect more. The pervasiveness of computer technology exerts a strong influence on society. Influence of such magnitude must be exercised responsibly. While patterns won't force you to act responsibly, they can ease the grind of reinvention, freeing you to consider higher purposes. Ultimately, patterns make life better for everyone—software user and developer alike.

These are ambitious and humbling goals, to be sure. We dedicate this fourth volume in the Pattern Languages of Program Design series to their attainment.

ACKNOWLEDGMENTS

Now for a word about the contributors to this book. A compendium of this size won't come together without many people pulling together. We are hugely grateful for their work. Specifically, we thank the authors for making this book necessary, to paraphrase Yogi Berra. We're referring not just to the authors you find here but also to the 60 percent or so of submitters whose works were not accepted. The exceptionally high quality of the submissions guaranteed the quality of the book, although it also made our job more difficult!

We recruited a veritable army of reviewers to help sift through the submissions. We owe them our sanity: Francis Anderson, Brad Appleton, Jorge Arjona, Owen Astrannen, Ken Auer, Jeff Barcalow, Kent Beck, Mike Beedle, Steve Berczuk, Manish Bhatt, Rosana Braga, John Brant, Kyle Brown, Jose Burgos, Frank Buschmann, Andy Carlson, Ian Chai, Alistair Cockburn, Jens Coldewey, James Coplien, Ward Cunningham, David Cymbala, Fonda Daniels, Dennis DeBruler, Michel DeChamplain, David Delano, Dwight Deugo, Paul Dyson, Philip Eskelin, Javier Galve, Julio Garcia, Alejandra Garrido, John Goodsen, Robert Hanmer, Kevlin Henney, Robert Hirschfeld, Ralph Johnson, Wolfgang Keller, Elizabeth Kendall, Norm Kerth, Charles Knutson, Frederick Koh, Philippe Lalanda, Manfred Lange, Doug Lea, Mary Lynn Manns, Klaus Marquardt, Paulo Masiero, Skip McCormick, Regine Meunier, Oscar Nierstrasz, James Noble, Alan O'Callaghan, Don Olson, William Opdyke, Dorina Petriu, Irfan Pyarali, Andreas Rausch, Dirk Riehle, Linda Rising, Antonio Rito Silva, Don Roberts, Gustavo Rossi, Cecilia Rubira, Andreas Ruping, Doug Schmidt, Ari Schoenfeld, Dietmar Schutz, Christa Schwanninger, Joe Seda, Peter Sommerlad, Michael Stal, Paul Taylor, Jenifer Tidwell, Dwayne Towell, and David Ungar.

We would like to give special thanks to John Vlissides, the managing editor of the series. He has provided us with encouragement and, occasionally, a needed prod. Neil would like to especially thank his two coeditors. Working with you has been a joy.

Finally, we would like to give special thanks to our families, friends, and coworkers who have supported us through this process. We hope that by the time you read this, we will be back to our cheery selves.

Neil Harrison, Boulder, Colorado
Brian Foote, Urbana, Illinois
Hans Rohnert, Munich, Germany


Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously

    If you find inappropriate content, please report it to Barnes & Noble
    Why is this product inappropriate?
    Comments (optional)