Release Plan / Validation Procedures

The specification (or the contract with your client) should contain a rough schedule which marks the major steps of the production and milestones or delivery dates.

If you plan to perform a pre-validation and/or final validation (highly recommended), you should also include the details and schedule for the validation procedures here (see sections , p. and , p. for more information regarding the validation procedures).

In a long-term speech corpus production (one to several years) you will probably not wait until the very end of the project but rather distribute parts of the corpus in releases. In that case the specifications should contain a mile stone plan that defines when and what data will be released (most likely together with the validation procedures for these releases). Also you might define in the specifications an update plan for the already released data because in most cases you or your partners/clients/validation center will find errors in the released parts of the corpus that have to be fixed. These updates are often forgotten in the specification and therefore often no funding is available for error updates.