Patterns-Based Engineering: Successfully Delivering Solutions Via Patterns

by Lee Ackerman, Celso Gonzalez

Successfully delivering Solutions via Patterns In Patterns-Based Engineering , two leading experts bring together true best practices for developing and deploying successful software-intensive systems. Drawing on their extensive enterprise development experience, the authors clearly show how to deliver on the promise of a patterns-based approach—and consistently create higher-quality solutions faster, with fewer resources. Lee Ackerman and Celso Gonzalez demonstrate how Patterns-Based Engineering (PBE) can help you systematically overcome common obstacles to success with patterns. By bringing discipline and clarity to patterns usage, their techniques enable you to replicate your success broadly and scale patterns to even the largest projects. The authors introduce powerful ways to discover, design, create, package, and consume patterns based on your organization’s experience and best practices. They also present extensive coverage of the nontechnical aspects of making patterns work, including a full chapter of guidance on clearing up misconceptions that stand in your way. Coverage includes Whether you’re an architect, designer, developer, analyst, project manager, or process engineer, Patterns-Based Engineering will help you to consistently derive greater business value and agility from patterns.

Genres: Technology

444 pages, Hardcover

First published July 2, 2010

Reviews

[Jeanne Boyarsky · Rating 4 out of 5]

"Patterns-Based Engineering is a big thick hardcover book with three parts. The audience is mainly architects/designers with OO, UML and patterns experience. The reader should also be comfortable dealing with abstract thought.

I had different reactions to each part so reviewing separately:

Part 1
The parts on how to generalize and look for patterns in what we do was interesting. It was approachable and I found myself scribbling in the margins.

Part 1a
There was a case study to walk you through how patterns based engineering works in practice. This was the least abstract part of the book, but it had one major problem - too much exposition on the dev team along with their names. Two pages later I was already backflipping to recall who these people are and by the next day/chapter I had no idea. Felt like I was missing something important.

Part 2
The patterns themselves are very reference like and dry. Nothing wrong with it, but didn't hold my attention. Maybe they aren't meant to be read straight through.

Part 3
I was back to being engaged and writing in the margins for the costs and benefits chapters. I think the misconceptions chapter could have been fleshed out more. Parts of it read like "X is a myth because X is not true" and could have used more examples.

---
Disclosure: I received a copy of this book from the publisher in exchange for writing this review on behalf of CodeRanch.