Table of Contents
| Foreword | |
| Foreword | |
| Preface | |
| Ch. 1 | Design Concepts | 1 |
| Ch. 2 | Responsibility-Driven Design | 39 |
| Ch. 3 | Finding Objects | 77 |
| Ch. 4 | Responsibilities | 109 |
| Ch. 5 | Collaborations | 149 |
| Ch. 6 | Control Style | 195 |
| Ch. 7 | Describing Collaborations | 239 |
| Ch. 8 | Reliable Collaborations | 277 |
| Ch. 9 | Flexibility | 315 |
| Ch. 10 | On Design | 355 |
| Bibliography | 375 |
| Index | 381 |
Forewords & Introductions
This is a book about designing object software. Like many human endeavors, design is part art, part engineering, part guesswork and experimentation. Discipline, hard work, inspiration, and sound technique all play their parts. Although a highly creative activity, software design fundamentals can be easily learned. There are fundamental strategies and techniques for developing a design solution. This book is packed with many practical design techniques that help you get the job done. We hope you become adept at thinking in objects and excited about devising solutions that exploit object technology.
Design choices can only be considered in light of what you know to be relevant and important. To achieve good results, however, you need to learn to discriminate important choices from mundane ones, and to acquire a good set of techniques that you intelligently practice. In this book, we present informal tools and techniques that don't require much more than a white board, a stack of index cards, a big sheet of paper and chairs around a table. Oh yeah, be sure to bring your brain, too!
But more important than a grab bag of techniques are the fundamental ways you view a design. Although the techniques we present in this book are independent of any particular implementation technology or modeling language or design method; our approach to object design requires a specific perspective:
Objects are not just simple bundles of logic and data... they are responsible members of an object community.
This approach, called Responsibility-Driven Design, forms the basis of how to reason about objects.
Most novice designers are searching for the right set oftechniques to rigidly follow in order to produce the correct design. In practice, things are never that straightforward. For any given problem there are many reasonable, and a few very good solutions. People don't produce identical designs, even if they follow similar practices or apply identical design heuristics. For each problem you approach, you make a different set of tactical decisions. The effects of each small decision accumulate. Your current design as well as your current lines of reasoning shape and limit subsequent possibilities. Given the potential impact of seemingly inconsequential decisions, designers need to thoughtfully exercise good judgment.
Your primary tool as a designer is your power of abstraction—forming objects that represent the essence of a working application. In a design, objects play specific roles and occupy well-known positions in an application's architecture. Each object is accountable for a specific portion of the work. Each has specific responsibilities. Objects collaborate in clearly-defined ways, contracting with each other to fulfill the larger goals of the application.
Design is both a collaborative and a solo effort. To work effectively you not only need a rich vocabulary for describing your design, but strategies for finding objects, recipes for developing a collaborative model, and a framework for discussing design trade-offs. You will find these tools in this book. We also explore how design patterns can be used to solve a particular design problem and demonstrate their effects on a design. We present you with strategies for increasing your software's reliability and flexibility. We discuss different types of design problems and effective ways to approach them. This book presents many tools and techniques for reasoning about a design's qualities and effectively communicating design ideas. Whether a student or a seasoned programmer, a senior developer or a newcomer to objects, there are many practical things you can take away from this book.
How to Read This Book
This book is organized into two major parts. The first six chapters—Design Concepts, Responsibility-Driven Design, Finding Objects, Responsibilities, Collaborations, and Control Style—form the core of Responsibility-Driven Design principles and techniques.You should get a good grounding by reading these chapters.
Design Concepts introduces fundamental views of object technology and explains how each element contributes to a coherent way of designing an application. Even if you are a veteran designer, a quick read will set the stage for thinking about object design in terms of their roles and responsibilities. Responsibility-Driven Design provides a brief tour of Responsibility-Driven Design in practice. Finding Objects presents strategies for selecting and, equally important, rejecting candidate objects in an emerging design model. Responsibilities presents many techniques for coming up with responsibilities and intelligently allocating them to objects. Collaborations gives many practical tips and examples of how to develop a collaboration model. Control Style describes strategies for developing your application's control centers and options for allocating decision-making and control responsibilities.
The last four chapters explore challenges you may encounter as you develop your design. Each chapter covers a specific topic that builds on the design concepts and techniques presented in the first part of the book. Describing Collaborations explores options for documenting and describing your design. Reliable Collaborations presents strategies for handling exceptions, recovering from errors and collaborating within and across a "trusted region." Flexibility discusses how to characterize software variations and design to support them. On Design discusses how to sort design problems into one of three buckets—the core, the revealing and the rest—and treat each accordingly.
Read an Excerpt
This book is about designing object software. Like many human endeavors, design is part art, part engineering, and part guesswork and experimentation. Discipline, hard work, inspiration, and sound technique all play their parts. Although software design is a highly creative activity, the fundamentals can be easily learned. Strategies and techniques exist for developing a design solution, and this book is packed with practical design techniques that help you get the job done. We hope you will become adept at thinking in objects and excited about devising solutions that exploit object technology.
You can consider design choices only in light of what you know to be relevant and important. To achieve good results, you need to learn how to discriminate important choices from mundane ones and how to acquire a good set of techniques that you intelligently practice. The informal tools and techniques in this book that don't require much more than a white board, a stack of index cards, a big sheet of paper, and chairs around a table. Oh yeah, be sure to bring your brain, too!
But more important than a grab bag of techniques are the fundamental ways you view a design. Although the techniques we present in this book are independent of any particular implementation technology or modeling language or design method, our approach to object design requires a specific perspective: Objects are not just simple bundles of logic and data. They are responsible members of an object community. This approach, called Responsibility-Driven Design, gives you the basis for reasoning about objects.
Most novice designers are searching for the right set of techniques to rigidlyfollow in order to produce the correct design. In practice, things are never that straightforward. For any given problem there are many reasonable solutions, and a few very good solutions. People don't produce identical designs even if they follow similar practices or apply identical design heuristics. For each problem you approach, you make a different set of tactical decisions. The effects of each small decision accumulate. Your current design as well as your current lines of reasoning shape and limit subsequent possibilities. Given the potential impact of seemingly inconsequential decisions, designers need to thoughtfully exercise good judgment.
Your primary tool as a designer is your power of abstraction--forming objects that represent the essence of a working application. In a design, objects play specific roles and occupy well-known positions in an application's architecture. Each object is accountable for a specific portion of the work. Each has specific responsibilities. Objects collaborate in clearly defined ways, contracting with each other to fulfill the larger goals of the application.
Design is both a collaborative and a solo effort. To work effectively you need not only a rich vocabulary for describing your design but also strategies for finding objects, recipes for developing a collaborative model, and a framework for discussing design trade-offs. You will find these tools in this book. We also explore how design patterns can be used to solve a particular design problem and demonstrate their effects on a design. We present you with strategies for increasing your software's reliability and flexibility. We discuss different types of design problems and effective ways to approach them. This book presents many tools and techniques for reasoning about a design's qualities and effectively communicating design ideas. Whether you're a student or a seasoned programmer, a senior developer or a newcomer to objects, you can take away many practical things from this book.
How to Read This Book
This book is organized into two major parts. The first six chapters--Chapter 1, Design Concepts, Chapter 2, Responsibility-Driven Design, Chapter 3, Finding Objects, Chapter 4, Responsibilities, Chapter 5, Collaborations, and Chapter 6, Control Style--form the core of Responsibility-Driven Design principles and techniques. You should get a good grounding by reading these chapters.
Chapter 1, Design Concepts, introduces fundamental views of object technology and explains how each element contributes to a coherent way of designing an application. Even if you are a veteran designer, a quick read will set the stage for thinking about object design in terms of objects' roles and responsibilities. Chapter 2, Responsibility-Driven Design, provides a brief tour of Responsibility-Driven Design in practice. Chapter 3, Finding Objects, presents strategies for selecting and, equally important, rejecting candidate objects in an emerging design model. Chapter 4, Responsibilities presents many techniques for defining responsibilities and intelligently allocating them to objects. Chapter 5, Collaborations, gives many practical tips and examples of how to develop a collaboration model. Chapter 6, Control Style, describes strategies for developing your application's control centers and options for allocating decision-making and control responsibilities.
Chapters 7-10 explore challenges you may encounter as you develop your design. Each chapter covers a specific topic that builds on the design concepts and techniques presented in the first part of the book. Chapter 7, Describing Collaborations, explores options for documenting and describing your design. Chapter 8, Reliable Collaborations, presents strategies for handling exceptions, recovering from errors, and collaborating within and across a "trusted region." Chapter 9, Flexibility, discusses how to characterize software variations and design to support them. Chapter 10, On Design, discusses how to sort design problems into one of three buckets--the core, the revealing, and the rest--and treat each accordingly.
loading...