
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
• A component is not part of the escrowed product and source code will not be provided
The main objective of Level II verification is to study as completely as possible whether the source code of each specific component or file of the software/application concerned is present. The steps in the Level II verification procedure are as follows:
1) Software developer deposits the escrow material
2) The user/beneficiary delivers a copy of the software that he is currently using
3) Escrow Europe analyses the components of the software and looks for the corresponding source code
4) Escrow Europe then draws up a verification report
This type of verification prevents any potentially incomplete deliveries of material to a great extent.