Use Case Description - Checking

Name of Use Case: Checking

Project: OCCAM

Author	Charlie Paull
Creation Date	27 March 07
Last Update Date
Version	0.1
Diagram	Current APS System for Conversion of OU data

Description
APS staff fill in a checking pro forma. To do this, information from the original P12 database is compared with each of the output datasets for the end recipients. All new courses are checked as is the first last and mid point records. Total numbers of courses are also checked.

Narrative



Conditions

Preconditions	Output files for end recipients have been created. Pro forma is available.
Successful end condition	All files are complete and correct and ready to be sent out. Any failures are correctly identified and removed.
Failed end condition	Incorrect or incomplete data flagged as ready to send to end recipients.

Primary Actors	APS Ltd staff
Secondary Actors

Trigger

Output files for end recipients have been created.

Included Use Cases

None

Main Flow


1. Compare each of the end recipient's final output files with original P12 database.
2. Check totals are the same.
3. Check first last and mid point records are the same.
4. Check all new courses are the same.