B.4 Solution Analysis

The root of the problem is that a set of requirements and business rules were missed during analysis.

We return to the Filled Level use case and add the following requirement to the exceptions: "The account setup, workflow task, and captured images are essential to this business process; if any of these fail, delete their partners and repeat this use case until successful."

Here is the use case revised.

Use Case B.2 Enroll Member

Use Case Name :

Enroll Member

Description:

The agency received an application from a person who wanted to join the retirement system. Determine 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 was 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 actor for eligibility information include

    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 the Send Form Letter use case).

7. If any step in the account creation process fails, roll back all of the other steps .

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)

  • An account is made up of

    - A business account (in the custom system)

    - An account in the imaging/document management system

  • Both are required for a valid account.

Technical Requirements:

None

Note that we do not specify how any of the rollbacks will be accomplished. We only want to document what needs to be done.



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