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

Scott W. Ambler (Author), Larry Constantine (Author)

Book Description

ISBN-10: 192962901X | ISBN-13: 978-1929629015 | Publication Date: January 22, 2000 | Edition: 1

Is the Unified Process the be all and end all standard for developing object-oriented component-based software? This book is the second in a four volume series that presents a critical review of the Unified Process. The authors present a survey of the alt

This second volume of a four-book series focuses on the design and implementation skeletal versions of new systems for purposes of testing early in the life cycle for quality control. This series is designed to fill the gap between theory and practice with a software process that goes beyond the UP with details of development and production. Fill the gap between theory and practice! Implement a software process that goes beyond the UP with details of development and production. You get a master's collection of best practices from Software Development magazine experts. This volume focuses on the design and implementation skeletal versions of new systems for purposes of testing early in the life cycle for quality control.

Editorial Reviews

About the Author

Scott W. Ambler started developing software in the early 80s, and has worked in object-oriented development for the past ten years in an array of roles. He is presently engaged as a software process mentor with AmbySoft Inc., a contributing editor

Product Details

• Paperback: 295 pages
• Publisher: CMP; 1 edition (January 22, 2000)
• Language: English
• ISBN-10: 192962901X
• ISBN-13: 978-1929629015
• Product Dimensions: 9.2 x 7.4 x 0.9 inches
• Shipping Weight: 1.5 pounds (View shipping rates and policies)
• Average Customer Review: 4.3 out of 5 stars  See all reviews (7 customer reviews)
• Amazon Best Sellers Rank: #2,290,568 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

4 of 4 people found the following review helpful:

5.0 out of 5 stars The RUP would be RIP without this book, May 8, 2001

By A Customer

This review is from: The Unified Process Construction Phase: Best Practices in Implementing the UP (Paperback)

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.

4 of 4 people found the following review helpful:

5.0 out of 5 stars Fills in many of the holes, May 8, 2001

By 

Scott W. Ambler "Author, Agile Database Techn... (Toronto, Canada) - See all my reviews

This review is from: The Unified Process Construction Phase: Best Practices in Implementing the UP (Paperback)

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.

3 of 3 people found the following review helpful:

4.0 out of 5 stars Best of Software Development Magazine, January 2, 2001

By 

Greg (United States) - See all my reviews

Amazon Verified Purchase

This review is from: The Unified Process Construction Phase: Best Practices in Implementing the UP (Paperback)

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.