Customer Reviews

The Unified Process Construction Phase: Best Practices in Implementing the UP

5 star:		(5)
4 star:		(1)
3 star:		(0)
2 star:		(0)
1 star:		(1)

 

 

This, book, like the others in this series, is great. It goes into detail about an improved version of the lifecycle for the Unified Process, one that actually addresses the real world needs of most companies. Trying to use the RUP on multiple projects? Trying to have a common architecture between them? Worried about reuse across projects? This book covers these topics and more with some of the best articles ever published in Software Development magazine.

Personally, I can't imagine anyone adopting the RUP without first reading this book series. I think it's great that someone has gone to the effort to sort through the best articles written by some of the best minds in this industry. Kudos to Ambler and Constantine for having the courage to stand up and say what many others have been afraid to.

This book is a collection of articles from Software Development magazine. We put this book together to present an alternate view on some of the best practices of the Unified Process, as well as to fill in some of the holes that have yet to be addressed. This includes the addition of a new phase, Production, as well as two new workflows: operations & support and infrastructure management. We invest the first chapter describing the Construction Phase and what should happen during its workflows (including the new ones) and in the rest of the book present articles, along with some new material, for the key workflows of the phase.

For developers we have articles about frameworks written by Arther Jolin and Gregory Rogers; articles for building components by Bertrand Meyer, Desmond D'Souza, and Bruce Powel Douglass; Class normalization written by myself; user interface design by Susan Fowler; a series about persisting objects in relational databases that I wrote; two articles for writing superior code by Dan Saks; several testing articles written by Martin Fowler, James Bach, and others. Plus there are many more articles that I haven't mentioned.

Project managers will benefit from the surviving a death march project by Ed Yourdon; leadership lessons by Larry Constantine; project management best practices by Karl Wiegers; a collection of reuse articles by Meilir Page-Jones, myself, Steve Adolph, Roland Racko, and others. Once again, I didn't reference all the articles aimed at this audience.

Everyone will learn from the eXtreme Programming (XP) article by Warren Keuffel; the configuration management articles by Clemens Szyperski, Tani Haque, and others; as well as the traceability articles that I wrote.

In all I believe this is a really solid book, one that you should read if you are involved with a project following the Rational Unified Process (RUP). The chapter written about the Infrastructure Management workflow alone is likely worth the price of the book, particularly if your organization is trying to successfully manage several development projects at once.

Discusses the rewards and pitfalls encountered by software developers using OO techniques; reuse, patterns, project management, etc. This book is based on articles from Software Development Magazine; therefore, not all aspects of the art are covered to the depth you might find in other books. There are diagrams of how tasks and ideas relate as well as lots of well documented lists such as "Rules for Component Builders" and "Rules for Framework Development". This is not an introductory text; it is probably best for an advanced beginner or higher. I'm sure that every manager could benefit from the knowledge herein. This book has an infectious enthusiasm for its subject.

This is a great book that is part of a great book series. I wasn't sure that a collection of magazine articles was worth paying for, but this book is far more than that. It helps to put the Construction Phase of the RUP into context and actually goes beyond the vanilla version of the RUP to provide advice that I could actually use.

There was a lot of articles about storing objects in relational databases, an idea that put me off at first, but being on an EJB project right now I discovered that these articles really helped me out.

Be forewarned. This book expresses very little original thought and is merely a collection of "other peoples" articles. This provides for very little logical flow for someone wanting to apply RUP. Where are the examples, tips of the trade, and how-to's?

Shame on me for not having gone to the book store first to look at the book as the online description gives no indication that it was in a periodical format.

I expected more from Scott after having read is other great "original thought" books.

This book is great! As a hotshot developer who now finds himself in the ranks of management, this book is a life saver! It is harder and harder for me to get time to do all the reading I really need to do. This book brings together the articles with substance and then flavors the content with insightful editor review. Thanks for producing this series.

I appreciate this effort by Ambler & Constantine. It is hard for someone like me who has moved from hotshot developer to "visionary leader" (management) to keep up with all my reading. This series has been a blessing by consolidating the appropriate articles for me read. The contents give me many useful perspectives to consider. Thanks.