对象解决方案——管理面向对象项目（影印版）

　　 本书是Grady Booch为读者精心打造的又一力作，他在本书中为项目开发人员和管理者应用对象技术提供了大量实用的建议。无论是对第一次开发面向对象项目的新手，还是对经验丰富的面向对象老手，本书都是非常有价值的学习资源。Booch基于其多年开发面向对象项目的经验，解释了如何应用面向对象技术的合理原则，以缩短系统开发周期、提高系统开发效率。本书提供给读者许多实用建议，包括推荐做法（recommended practice）和经验法则（rules of thumb），这些建议是项目成功的关键。总之，这是一本少有的、由著名的面向对象实践者总结其实用建议的好书！
　　 涵盖了大部分对面向对象技术管理者和开发人员来说非常重要的主题总结了作者多年在全球开发面向对象项目的经验通过提供项目问题、隐含意义、推荐做法和经验法则，着重强调了管理面向对象项目实践的方方面面提供了大量真实的项目实例，并演示了开发面向对象系统的各种方法
　　

chapter 1: first principles 1
when bad things happen to good projects 5
establishing a project's focus 9
understanding a project's culture 11
the five habits of successful object-oriented projects 22
issues in managing object-oriented projects 29
chapter 2: products and process 33
in search of excellent objects 37
object-oriented architectures 43
the artifacts of a software project 54
establishing a rational design process 63
chapter 3: the macro process 69
the one-minute methodology 74
conceptualization 80
analysis 86
design 108
evolution 129
maintenance 151
chapter 4: the micro process 155
i'm ok, my program's ok 159

　　 Early adopters of object-oriented technology took it on faith that object orientation was A Good Thing, offering hope for improving some ugly aspect of software development. Some of these primordial efforts truly flourished, some failed, but overall, a number of such projects quietly began to experience the anticipated benefits of objects: better time to market, improved quality, greater resilience to change, and increased levels of reuse. Of course, any new technology is fun to play with for a short while. Indeed, there is a part of our industry that thrives on embracing the latest fad in software development. However, the real business case for any mature technology is that it delivers measurable and sustainable benefits for real projects.
　　 Object-oriented technology has demonstrated its value in a multitude of applications around the world. I have seen object-oriented languages and methods used successfully in such diverse problem domains as securities trading, medical electronics, enterprise-wide information management, air traffic control, semiconductor manufacturing, interactive video gaming, telecommunications network management, and astronomical research. Indeed, I can honestly say that in every industrialized country and in every conceivable application area, I have come across some use of object-oriented technology.
　　Object-oriented stuff is indisputably a part of the mainstream of computing.
　　 There exists an ample and growing body of experience from projects that have applied object-oriented technology. This experience - both good and bad is useful in guiding new projects. One important conclusion that I draw from all such projects is that object-orientation can have a very positive impact upon software development, but that a project requires much more than just an object-oriented veneer to be successful. Programmers must not abandon sound
　　development principles all in the name of objects. Similarly, managers must understand the subtle impact that objects have upon traditional practices.
　　 SCOPE
　　 In almost every project I have come across, be it a modest two- or three-person effort, to undertakings of epic proportions wherein geopolitical issues dominate, a common set of questions always appears: How do I transition my organization to object-oriented practices? What artifacts should I manage to retain control? How should I organize my staff? How do I measure the quality of the software being produced? How can I reconcile the creative needs of my individual programmers with management's needs for stability and predictability? Can object-orientation help me help my customers better articulate what they really want? These are all reasonable questions, and their answers strike at the heart of what is different and special about object-oriented technology.
　　 This book serves to answer these and many other related questions, by offering pragmatic advice on the recommended practices and rules of thumb used by successful projects.
　　 This is not a theoretical book, nor is its purpose to explain all the dark corners of object-oriented analysis, design, and programming. My previous work, Object-Oriented Analysis and Design with Applications, serves those purposes: it examines the theoretical underpinnings of all things object-oriented, and offers a comprehensive reference to a unified method of object-oriented analysis and design.
　　 Object Solutions provides a direct and balanced treatment on all the important issues of managing object-oriented projects. I have been engaged in hundreds of projects; this book draws upon that broad experience. My intent is to explain what has worked, what has not, and how to distinguish between the two.
　　AUDIENCE
　　 My intended audience includes project managers and senior programmers who want to apply object-oriented technology successfully to their projects, while avoiding the common mistakes that can befall the unwary. Professional programmers will find this book useful as well, giving them insight into the larger issues of turning cool looking object-oriented code into real products; this book will also help to explain why their managers do what they do. Students on their way to becoming professional programmers will come to understand why software development is often not very tidy in the real world, and how industrial-strength projects cope with this disorder.
　　ORGANIZATION
　　 I have organized this book according to the various functional aspects of managing an object-oriented project. As such, it can either be read from cover to cover or selectively by topic. To make this material more accessible, my general style is to present an issue, discuss its implications, and then offer some recommended practices and rules of thumb. To distinguish these elements in the text, I use the following typographic conventions:
　　 This is an issue, usually stated in the form of a question followed by its answer, regarding some functional area of project management.
　　 This is a recommended practice, which represents a generally acceptable way of addressing a given issue.
　　 This is a rule of thumb, which represents some quantifiable measure about a particular practice.
　　 I've numbered these practices and rules sequentially, so that specific ones can be referred to easily.
　　 To reinforce certain lessons, I offer examples drawn from a variety of production object-oriented projects, whose details have been changed to protect the guilty. I highlight these examples in the following manner:
　　 This is an example, drawn from some production object-oriented project.