Use Case Description - Indicate reason for rejection

Name of Use Case: Indicate reason for rejection

Project: Applicant feedback scoping study

Author	Alan Paull
Creation Date	26 Feb 07
Last Update Date	29 Mar 07
Version	1.0
Diagram	Use case diagram

Description
Admissions staff check that each applicant meets the minimum entry requirements for each course. Could be done automatically.

Narrative

Either admissions staff or an automatic system retrieves the formal qualifications and other formally stated attributes of the applicant and compares them with the minimum entry requirements for the course. Those applicants that do not meet the minimum entry requirements and have no circumstances that might enable them to be considered further are allocated a standard code.

Conditions

Preconditions	Applicant has stated how they might satisfy the requirements in a format that can be automatically verified.
Successful end condition	System declares applicant as satisfying minimum entry requirements or not.
Failed end condition	System unable to adjudicate, so admissions staff must intervene

Primary Actors	Application; Course entry requirements system
Secondary Actors	Admissions staff

Trigger

Application submitted

Included Use Cases

None

Main Flow


1. Application submitted to university system.
2. Course entry requirements matched with application attributes.
3. Course entry requirements system declares status as matched or unmatched. Use Case ends.