Level II verification came about as a result of the difficulties many software developers had delivering complete source code. If you consider that a software package often consists of hundreds of components, then you will understand how easily this problem can occur.

Examples that we have encountered in practice:

• A component was developed years ago. It is not part of the normal software release system.
• A component was designed by another department or purchased from a third party

The main objective of Level II verification is to verify whether the delivered source code compiles without any problems on a standalone computer, following the build instructions. The steps in the Level II verification procedure are as follows:

1. Software developer deposits the escrow material
2. WorldEscrow compiles the delivered source code on a standalone computer, following the build instructions.
3. Problems or missing data are reported to the supplier, who will then delivers an update of the deposit
4. WorldEscrow then draws up a verification report

This type of verification prevents any potentially incomplete deliveries of material to a great extent. However more thorough and in debt than the Level I verification, the level II doesn’t say anything about usability in comparison to the version and environment that the user uses. Which is something a Level III can verify.