One way to master OO design<\/a> is do design and implementation of a large number of classes. This book guides you through exercises to design dozens of classes that must work together to create a large \u2013 and reasonably complete \u2013 application. We\u2019ll discuss the design in some detail to reveal an approach to object-oriented design.<\/p>\n While it is also important to read examples of good design, a finished product doesn\u2019t reveal the designer\u2019s decision-making process<\/a>. Our goal in this book is to help programmer understand the design process that leads to a final product.<\/p>\n Everything is Design It\u2019s important to note that all software development involves considerable skill in design. In some circles, there is an attempt to distinguish between architects (or designers) and coders. The idea is that someone can be able to work with a language \u2013 coding<\/a> \u2013 but not quite ready to do design work. The coders can be given a detailed \u201cspecification\u201d from which they can write code.<\/p>\n This distinction between designers and coders doesn\u2019t really exist. It\u2019s unhelpful to try and make this distinction. All programming involves<\/a> design at some level.<\/p>\n If we attempt to write a design specification so detailed that someone else can transform it into code without them having to make any design decisions, the specification is isomorphic to code, but written in some non-technical language like English. The design has all the details of code. An automated translation could produce code from this magically complete with fewer errors than a person.<\/p>\n If we write specifications at somewhat more abstract level, we\u2019re demanding that the \u201ccoder\u201d makes some design decisions to move from the abstraction to concrete code. The more abstract the specification, the more design work must be done. The amount of design work is non-zero.<\/p>\n The point of this book is to build skills in object-oriented design<\/a> prior to a project with a fixed budget and a looming deadline<\/a>.<\/p>\n This book provides a sequence of interesting and moderately complex exercises in OO design. The exercises are not hypothetical but must lead directly to working programs.<\/p>\n The applications we will build are a step above trivial, and will require some careful thought as part of creating a workable design. Further, because the applications are largely recreational in nature, they are interesting and engaging. This book allows the reader to explore the processes and artifacts of OO design before project deadlines make good design seem impossible.<\/p>\n The first part will be quite detailed. The third part will summarize the designs at a higher level of abstraction<\/p>\n","protected":false},"excerpt":{"rendered":"1.2 What You\u2019ll Do<\/h4>\n