Produktinformation
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
Ist der Verkauf dieses Produkts für Sie nicht akzeptabel? |
The first part of the book concentrates on the common myths of object-oriented development. (For example, Cockburn 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 project case histories (both small and large) and analyses 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
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
Tags(Was ist das?)Bei einem Tag handelt es sich um ein Schlagwort, das zum Produkt passt.
Tags erleichtern allen Kunden die Suche und die Sortierung ihrer Lieblingsprodukte. |
|
Sagen Sie Ihre Meinung zu diesem Artikel:
|
||||||||||||||||||||||
|
Die hilfreichsten Kundenrezensionen
2 von 2 Kunden fanden die folgende Rezension hilfreich:
3.0 von 5 Sternen
COM? CORBA? OO without components?!,
Von Ein Kunde
Rezension bezieht sich auf: Surviving Object-Oriented Projects: A Manager's Guide (Addison-Wesley Object Technology) (Taschenbuch)
This book presents many good ideas but is overly concerned with the impact of languages (C++, Java, COBOL, Smalltalk) on OO development. Objects and components go hand-in-hand in 1999 (just as they did in 1998 when this book was published). This emphasis on language (rather than framework) leads me to believe that the author lacks recent experience and/or vision. Still, there is something to harvest here and (halfway through) I am glad I purchased the book.
Helfen Sie anderen Kunden bei der Suche nach den hilfreichsten Rezensionen
1 von 1 Kunden fanden die folgende Rezension hilfreich:
5.0 von 5 Sternen
Essential reading for OO management,
Von Ein Kunde
Rezension bezieht sich auf: Surviving Object-Oriented Projects: A Manager's Guide (Addison-Wesley Object Technology) (Taschenbuch)
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.
Helfen Sie anderen Kunden bei der Suche nach den hilfreichsten Rezensionen
1 von 1 Kunden fanden die folgende Rezension hilfreich:
5.0 von 5 Sternen
I wished I read this book two years ago....,
Von Ein Kunde
Rezension bezieht sich auf: Surviving Object-Oriented Projects: A Manager's Guide (Addison-Wesley Object Technology) (Taschenbuch)
Simply said, I loved this book!This book provides ALL kind of managers as well as team members with VERY valuable information about the project process, project control, pitfalls and ways to (bigger chances on) success. I wish we had read this book two years ago when we updated our software to a GUI-environment. Pitfall after pitfall were encountered, already clearly written down in this book. Reading it beforehand, might have saved the project... Thanks Alistair, for writing this book! Please keep writing... Helfen Sie anderen Kunden bei der Suche nach den hilfreichsten Rezensionen
Sagen Sie Ihre Meinung zu diesem Artikel: Eigene Rezension erstellen
|
Die neuesten Kundenrezensionen |
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
|
|
|