The first part of the book concentrates on the common myths of object-oriented development. (For example, he clearly prefers Smalltalk and Java to C++ as a development language and he is not enthusiastic about today's computer-aided software engineering [CASE] tools.) He also cuts through the mire of software-engineering methodologies for development by stressing an incremental approach to creating software and gives many useful and practical suggestions for setting up and managing projects of varying sizes.
Throughout this lively and well-written text, the author mixes in anecdotes from actual managers and developers. He also presents actual case histories for projects (both small and large) and analyzes what was done correctly and what went wrong. The author develops 12 strategies for creating successful, on-time software using objects, which are collated in a handy appendix--there is even a detachable "crib sheet."
With its mix of common sense and real-world savvy, Surviving Object-Oriented Projects offers a refreshing take on the realities of developing object-oriented software. This concise and engaging title can improve the odds of success for your next programming project. --Richard Dragan
Today, many organizations claim competitive market advantages resulting from the application of object-oriented technology and approaches in their software development efforts. As the use of object technology has become increasingly widespread and mainstream, a growing number of project managers are faced with a daunting task: keeping the object technology project on track and within budget. These project managers are burdened by the weight of knowing that the survival and ultimate success of the project hinges on their insight when planning the project and their responses to events that lie ahead. Unfortunately, hidden costs, unpleasant surprises and unrealistic expectations lie in wait for the unprepared manager.
Although much has been written about object technology and the benefits of this paradigm, there is still a shortage of compiled knowledge about what to expect and to plan for during project implementation. This book provides information that managers need to combat the unforeseen challenges that await them, allowing them to survive and ultimately succeed with an object-oriented project.
To provide practical advice and guidelines for successfully managing an object-oriented project, the author borrows from the seasoned wisdom of numerous experts and successful consultants while also drawing on his personal experience and extensive knowledge. Surviving Object-Oriented Projects: A Manageris Guide points out potential hazards and names workable solutions by addressing the important issues of scheduling, budgeting, staffing, and cost justification. Key points are supported and illustrated through short case studies taken from real object-oriented projects, and an appendix collects these workable guidelines and solutions into brief icrib sheetsio ideal for handy reference.
Product Details
Would you like to update product info or give feedback on images?
|
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
15 of 16 people found the following review helpful:
5.0 out of 5 stars
Essential reading for OO management,
By A Customer
This review is from: Surviving Object-Oriented Projects (Paperback)
This book is essential reading for anyone interested in running an OO project, or for anyone who simply wants a balanced view of OO development. Unlike most other OO authors I've encountered, Alistair Cockburn is not interested in selling OO as the answer to all our prayers, but uses a wealth of case studies to show us the limits, pitfalls and negative side of OO development, as well as the benefits. Perhaps because of this, he doesn't ignore the management aspects of development, most of which are common to OO and non-OO projects. The book is also well presented and well written, and even has a sprinkling of humour. I particularly like his term "PolyBloodyHardReuse", the meaning of which will be obvious to anyone who's ever seen attempts to introduce software reuse into an organisation.
15 of 16 people found the following review helpful:
4.0 out of 5 stars
Strong on management tricks and techniques,
By Natasha (Philadelphia, MS USA) - See all my reviews
This review is from: Surviving Object-Oriented Projects (Paperback)
I bought this book as an introduction to changing to object oriented design. It was very easy to read (even for a beginner) and I did get a clearer idea of the way to go about designing an OO system, and what to expect in the way of timing and pitfalls. I will need to buy some more advanced books on OO analysis and design (as recommended by the writer), but this was a painless and easy start.
12 of 13 people found the following review helpful:
4.0 out of 5 stars
A pragmatic approach to iterative developpement transition,
By
This review is from: Surviving Object-Oriented Projects (Paperback)
First of all, the book is short and always go directly to the essential. It saves time and make the reading very efficient. The very goal of the book is to explain how to go to iterative developpement and what may cause success or failure. Everything is well illustrated by real cases, met by the author. You don't need courage to survive to this book, because the reading is pleasant. Very good.
Share your thoughts with other customers: Create your own review
|
|
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|