ing period. It is also important to recognize other related implications of accept- ance such as the end of a test and certification period and the start of warranty period. Another example commonly found in software products is the so-called annual support agreement. Most of these are written around delivery and acceptance of the initial software-licens- ing period. If the agreement is not written that way, it should be. ACCEPTANCE STRATEGIES Depending on the level, size, and scope of the organization and pro- ject, one or more strategies can be used. A large corporation with a global network may have a laboratory where equipment, systems, and application software are assembled and evaluated. The outcome of such a project and output from the total exercise can substantially reduce the level of examination, test, and report writing during the acceptance process. A phased acceptance in the form of alpha and beta testing can serve new or improved software deployment very well. With phased acceptance, the idea is to prove that the product works as promised and expected. The phased approach can also prove that the deployment plan works as well as how effective the documentation is in terms of supporting users when they have a problem. Yet another type of system (e.g., a large enterprise wide accounting system) may have to be examined, tested, evaluated, and accepted in one big exercise involving several people dedicated to the task, with 10 ACCEPTING DELIVERED EQUIPMENT AND SERVICES cooperation and support from the entire accounting department and all the departmental budget coordinators. The challenge is to manage risk while at the same time permitting timely installation and start of operations. ACCEPTANCE OF EQUIPMENT Digital equipment and systems always include some form of soft- ware. After all, digital hardware wouldn't be of much value without the software. Software sometimes goes by other names or euphem- isms such as firmware or micro code. Less often, other software such as interpreters and compilers and ut