Object Solutions: Managing the Object-oriented Project
Object Solutions is a direct outgrowth of Grady Booch's experience with object-oriented project in development around the world. This book focuses on the development process and is the perfect resource for developers and managers who want to implement object technologies for the first time or refine their existing object-oriented development practice. The book is divided into two major sections. The first four chapters describe in detail the process of object-oriented development in terms of inputs, outputs, products, activities, and milestones. The remaining ten chapters provide practical advice on key issues including management, planning, reuse, and quality assurance. Drawing upon his knowledge of strategies used in both successful and unsuccessful projects, Grady Booch offers pragmatic advice for applying object-technologies and controlling projects effectively.
What people are saying - Write a review
We haven't found any reviews in the usual places.
The Five Habits of Successful ObjectOriented Projects
PRODUCTS AND PROCESS
22 other sections not shown
abstractionists abstractions activity analysis application approach architect architecture artifacts associated behavior building carry Chapter classes classes and objects collaboration common complex conceptualization consider continues cost creating cycle decisions describe development team diagrams distribution document domain model early end users engineers essential establish evolution example executable existing expect experience fact focus forces framework functionality identify implementation important individual integrity interfaces involves issues iterative kinds language macro means measure mechanisms ment micro process needs never object-oriented project objects operations organization particular patterns phase planning possible practice primary problem programming prototypes reasons release represent requirements responsibilities resulting risk roles rules scenarios schedule semantics serve simple software development specific step structure successful tend testing things tion typically ultimately understanding