Is the Unified Process the be all and end all standard for developing object-oriented component-based software? This book is the final in a four volume series that presents a critical review of the Unified Process. The authors present a survey of the alte
This book, the last in a four-volume series, offers a critical review of the UP and presents a masters' collection of best practices to use as guidelines in implementing a more robust software process. In the Transition phase, developers focus on testing and validating the complete system, operating the system in parallel with legacy systems and converting legacy databases and systems to support a new release.
A wealth of knowledge on how to be successful at developing software has been published in Software Development magazine and in its original incarnation, Computer Language. The people who have written for the magazine includes many of the industry’s best known experts: Karl Wiegers, Ellen Gottesdiener, James Bach, Jim Highsmith, Warren Keuffel, and Martin Fowler, to name a few. In short, the leading minds of the information industry have shared their wisdom with us over the years in the pages of this venerable magazine.
Lately, there has been an increased focus on improving the software process within most organizations. Starting in the mid−1990s, Rational Corporation was acquiring and merging with other tool companies. As they consolidated the companies, they consolidated the processes supported by the tools of the merging companies. The objective of the consolidation was to arrive at a single development approach. They named the new approach the Unified Process. Is it possible to automate the entire software process? Does Rational have a complete toolset even if it is? We’re not so sure. Luckily, other people were defining software processes too, so we have alternate views of how things should work. This includes the OPEN Consortium’s OPEN process, the process patterns of the Object−Oriented Software Process (OOSP), Extreme Programming (XP), and Agile Modeling (AM). These alternate views can be used to drive a more robust view of the Unified Process, resulting in an enhanced lifecycle that more accurately reflects the real−world needs of your organization. Believing that the collected wisdom contained in Software Development over the years could be used to flesh−out the Unified Process — truly unifying the best practices in our industry — we undertook this book series.