Use Case ID: |
UC28.0 |
Use Case Name: |
Query Message Status |
Created by: |
jwh |
Date Created: |
Fri Jul 20 14:18:16 2001 |
Last Updated by: |
jwh |
Date Last Updated: |
Fri Jul 20 14:18:16 2001 |
Actor: User Application
Goal: Query the status of a message recently sent.
Description: Query the status of a message recently sent to determine if has
completed.
Preconditions:
- A message was successfully created and transmission has begun.
Post conditions:
None
Priority: High
Related Use Cases:
UC18.0 - Send Peer Message
Notes and Issues:
None
Event Flow:
- The application requests a message to be sent by the engine.
- The engine begins to send the message.
- The application queries the status of the message to determine progress.
- The engine checks if the message transmission has completed.
- The engine returns the result of the check to the application.
Alternate Flows:
UC28.1 Message doesn't exist
- The application requests a message to be sent by the engine.
- The engine begins to send the message.
- The application queries the status of the message to determine progress.
- The engine checks if the message transmission has completed.
- The engine determines that the message doesn't exist or is old and returns
the error to the application.
Sequence Diagrams:
Revision History
Name |
Date |
Reason for Change |
Version |
|
|
|
|
$Id: UC28.0.html,v 1.5 2001/07/26 17:52:19 james Exp $