This book is the fourth in a four-volume series that presents a critical review of the Unified Process -- designed to present a more robust software process that addresses your development and production needs. The series provides you with a balanced perspective of the alternative design methodologies available, proposes a synthesized software process that addresses the scope of your real world, and presents materials from the Software Development magazine that will flesh out each of the UP phases. In this series you get the collective wisdom of industry luminaries such as Karl Wiegers, Jim Highsmith, Bertrand Meyer, Johanna Rothman, Warren Keuffel, Larry Constantine, and myself (Scott Ambler). The Transition phase is the fourth of six phases -- Inception, Elaboration, Construction, Transition, Production , and Retirement -- that a system experiences throughout its complete lifecycle. During the Transition phase your project team will focus on testing and validating your complete system, operating the system in parallel with any legacy systems that you are replacing (if applicable), converting legacy databases and systems to support your new release, training the customers of your system, and deploying your system into production. As you perform these activities you will create and/or evolve a wide variety of artifacts: -
Final product baseline (also known as a production baseline) of your system -
Training materials for your system -
Documentation, including user manuals, support documentation, and operations documentation
|