Use Case ID: UC21.0
Use Case Name: Cancel Reply to Peer Request
Created by: jwh
Date Created: Thu Jul 19 22:10:56 2001
Last Updated by: jwh
Date Last Updated: Thu Jul 19 22:10:56 2001

Actor: User Application

Goal: Cancel a reply.

Description: Cancel a reply.

Preconditions:

  1. The engine must be started.
  2. The reply transmission is not complete.
  3. The reply to cancel must be valid.
Post conditions:

None.

Priority: High

Related Use Cases:

UC15.0 - Send Peer Request
UC16.0 - Send Peer Request Async
UC17.0 - Cancel Peer Request
UC20.0 - Reply to Peer Request

Notes and Issues:

None

Event Flow:

  1. The application asks the engine to cancel a reply sent to a peer.
  2. The engine cancels the reply transmission
  3. The engine removes the reply from its in progress list.
Alternate Flows:

UC21.1 Engine is not started

  1. The application asks the engine to cancel a reply message.
  2. The engine returns an error that the it has not been started.

UC21.2 Reply doesn't exist

  1. The application asks the engine to cancel a reply message.
  2. The engine returns an error that the reply doesn't exist.

UC21.3 Reply Already Set

  1. The application asks the engine to cancel a reply message.
  2. The engine returns an error that the engine has already sent the reply.

Sequence Diagrams:

Event Flow Sequence Diagram

Revision History
Name Date Reason for Change Version
       


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