ADoM - Admissions Domain Map

ADoM Project Home Page

Overview Diagram


Feedback: Retrieve records

Types
  Attribute Label
Description
Feedback: University gives feedback Use Case

The Admissions Officer gets the relevant electronic records about the applicant from the database of applications.

display name Feedback: Retrieve records
present or future future
Related to Scenarios Feedback: University gives feedback
source Improving the provision of feedback to applicants
use Case specification

Narrative

The Admissions Officer confirms the identity of the applicant. He then retrieves the relevant records about the applicant from the applications database, which may include scoring sheets, interview notes, an application form and other assessment details.

Conditions

  • Preconditions Valid request for feedback passed to Admissions Officer by central admissions department
  • Successful end condition Electronic records retrieved from applications database.
  • Failed end condition Electronic records not found.
  • Primary Actors Admissions Officer; applications database
  • Secondary Actors
  • Trigger Applicant identified as an individual whose application was assessed by the department.
  • Included Use Cases Identify applicant Use case: Identify applicant

Main Flow

  1. Admikssions Officer accesses the applications database.
  2. include :: Identify applicant
  3. Admissions Officer confirms the applicant's identity.
  4. Admissions Officer retrieves the applicant's file from the applications database. Use case ends.

  ^ back to top

Return to ADoM Hierarchy

Generated: 12/23/2008, 2:01:37 PM, Greenwich Mean Time

Comments page 0 of 0
Click here to tell us how this relates to what you do.
There are currently 0 comments to display.

 
ADoM is a JISC funded project led by the University of Nottingham, Centre for International ePortfolio Development in partnership with Manchester Metropolitan University, UCAS and APS Ltd.