The Unified Process Construction Phase: Best Practices for Completing the Unified Process
Dozens of magazine articles about the third phase of the Unified Process, which encompasses analysis, design, and configuration management.
TABLE OF CONTENTS The Unified Process Construction Phase: Best Practices for Completing the Unified Process
Chapter 8: Parting Words
We have known the fundamentals of the software process for years. One has only to read classic texts such as Fred Brooks' The Mythical Man Month (1995), originally published in the mid-1970s, to see that this is true. Unfortunately, as an industry, we have generally ignored these fundamentals in favor of flashy new technologies promising to do away with all our complexities, resulting in a consistent failure rate of roughly 85%. Seven out of eight projects fail that is the cold, hard truth. Additionally, this failure rate and embarrassments such as the Y2K crisis are clear signs that we need to change our ways. It is time for organizations to choose to be successful, to follow techniques and approaches proven to work in practice, and to follow a mature software process.
A failure rate of roughly 85% implies a success rate of only 15%. Think about it.
8.1 Looking Towards Transition and Production
In a nutshell, the goal of the Construction phase is to create a version of your application so it may be transitioned to your user community. To move into the Transition phase, you must pass the Initial Operational Capability (IOC) milestone (Kruchten, 1999). To pass this milestone, you must achieve:
-
Stability. The produce release should be stable and mature enough to be released to your user community. This means that your software has been tested internally, the applicable
documentation has been written and initially reviewed, and your installation process has been developed and tested...
Copyright CMP Media, Inc. 2000 under license agreement with Books24x7
