Step 1 : Check common CWS requirement (Checklist in flow chart)

- Check if release target of CWS is set correctly.

- Check right adjustment of due dates (plan at least an average of 5 working days for testing in QA).

- Build version should not be too old compared to the current master.
(e.g. 1-2 build if many CWSs were integrated; 3-5 build if only a few CWSs were integrated - release phase -; last build if important changes were made in this build)

- Appropriate information about specific and global risks must be provided, either in the comments section of the EIS status page and/or in one or more QA child tasks.

- All issues must have the status 'Resolved/Fixed'

- All issues must be assigned to a QA members (except those only developers can verify)

- Issues that can only be tested by a developer must have the status 'verified' (set by another developer!)