ABSTRACT
Being ready for the next major upgrade is the next success recipe. In Chapter 10, we reported that systems experience a major upgrade every §ve to seven years.1 Many times such a refresh is driven by hardware updates, platform revisions, or major commercial o¥-the-shelf (COTS) or open soœware package replacements. Independent of the cause, most maintenance shops view such improvements as opportunities to get things done outside of the normal release cycle. For example, they can make all of the changes that are pending to a piece of platform soœware that is being updated all at once independent of their priorities. As another example, they can ask for and get funding to update an outdated graphical user interface (GUI) because management may be more receptive to making groups of changes rather than others one at a time.
