Use Case ID: |
UC15.0 |
Use Case Name: |
Send Peer Request |
Created by: |
jwh |
Date Created: |
Thu Jul 19 18:34:56 2001 |
Last Updated by: |
jwh |
Date Last Updated: |
Thu Jul 19 18:34:56 2001 |
Actor: User Application
Goal: Send a request
Description: Send a request and wait for a response
Preconditions:
- The engine must be started.
Post conditions:
None.
Priority: High
Related Use Cases:
UC16.0 - Send Peer Request Async
UC17.0 - Cancel Peer Request
UC27.0 - Handle Peer Request
UC29.0 - Query Request Status
Notes and Issues:
None.
Event Flow:
- The application asks the engine to transmit a request to a peer.
- The engine constructs an appropriate request message.
- The engine sends the query message to the peer.
- After the engine receives the response, the response is returned to the
application.
Alternate Flows:
UC15.1 Engine is not started
- The application asks the engine to transmit a request to a peer.
- The engine returns an error that the it has not been started.
UC15.2 The peer is not available
- The application asks the engine to transmit a request to a peer.
- The engine constructs an appropriate request message.
- The engine sends the query message to the peer.
- The engine determines that the peer is not currently available.
- The engine returns an error that the peer is not available.
UC15.3 Timeout
- The application asks the engine to transmit a request to a peer.
- The engine constructs an appropriate request message.
- The engine sends the query message to the peer.
- The engine determines that the timeout period has been exceeded.
- The engine returns an error that the timeout was exceeded.
Sequence Diagrams:
Revision History
Name |
Date |
Reason for Change |
Version |
|
|
|
|
$Id: UC15.0.html,v 1.6 2001/07/26 17:52:19 james Exp $