Use Case ID: UC30.0
Use Case Name: Query Reply Status
Created by: jwh
Date Created: Fri Jul 20 14:38:16 2001
Last Updated by: jwh
Date Last Updated: Fri Jul 20 14:38:16 2001

Actor: User Application

Goal: Query the status of a response recently sent.

Description: Query the status of a response recently sent to determine if has completed.

Preconditions:

  1. A response was successfully created and transmission has begun.
Post conditions:

None

Priority: High

Related Use Cases:

UC20.0 - Reply to Peer Request

Notes and Issues:

None

Event Flow:

  1. The application requests a response to be sent by the engine.
  2. The engine begins to send the response.
  3. The application queries the status of the response to determine progress.
  4. The engine checks if the response transmission has completed.
  5. The engine returns the result of the check to the application.
Alternate Flows:

UC30.1 Request doesn't exist

  1. The application requests a response to be sent by the engine.
  2. The engine begins to send the response.
  3. The application queries the status of the response to determine progress.
  4. The engine checks if the response transmission has completed.
  5. The engine determines that the response doesn't exist or is old and returns the error to the application.

Sequence Diagrams:

Event Flow Sequence Diagram

Revision History
Name Date Reason for Change Version
       


$Id: UC30.0.html,v 1.4 2001/07/26 01:58:10 james Exp $