B.2 Background

This system, being built for a government agency, consists of a number of off-the-shelf components (workflow, imaging, and accounting systems) integrated with proprietary business software. Its overall function is to enroll applicants into a retirement system. The business is triggered when an enrollment form is received. The form is scanned electronically using an enterprise scale imaging system and the original is sent to document storage. The type of form received indicates the business process the sender requested , and the system creates an instance of this process in the workflow system. The next available operator will be assigned this work and will access the document image from the integrated system if the client has an active account that is made available.

Figure B.1. Enroll Retirement System Member

graphics/bfig01.gif

This short description indicates that several systems integrate to handle this business ”imaging, workflow, accounts, and the propriety business systems. Here is the original use case describing the requirements for one activity ” enrolling users. We will work with a high-level use case, as the issue we will explore does not lie in the details.

Use Case B.1 Enroll Member

Use Case Name :

Enroll Member

Description:

The agency received an application from a person who wanted to join the retirement system. Determine his eligibility and, if necessary, record the enrollment details and create the account.

Actors:

Enrollment specialist

Triggers:

A person submitted an application to join the retirement system.

Preconditions:

The Create Process from the Received Mail use case is completed.

Basic Course of Events:

  1. The system notifies the actor that a membership application was received.

  2. The actor accepts the work assignment.

  3. The system displays the received application.

  4. The actor examines the application to determine eligibility.

  5. The system prompts the actor for eligibility information including

    1. Agency of employment

    2. Hours per month

    3. Employment date

  6. The system determines eligibility.

  7. The system prompts the actor to enter data for account creation, including

    1. Name

    2. Address

    3. Social Security Number

  8. The system creates a new account for the member.

    1. New retirement account

    2. Electronic document account

  9. The system moves the enrollment form from the processing queue to the members account.

  10. The system marks the workflow instance as complete.

  11. The system updates the actor's work record to indicate the start and end time of this process.

Exceptions:

6. If the prospective member is found ineligible, the system creates a rejection notice to be printed and mailed (see Send Form Letter use case).

Postconditions:

  • The enrollment form is removed from the "received" queue.

  • The enroll member business process instance is marked as completed.

Business Rules:

Refer to enrollment business rules (for brevity these are not listed here).

Technical Requirements:

None



Use Cases. Requirements in Context
Use Cases: Requirements in Context (2nd Edition)
ISBN: 0321154983
EAN: 2147483647
Year: 2002
Pages: 90

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net