Use Case ID: UC31.0
Use Case Name: Find Network Service
Created by: jwh
Date Created: Fri Jul 20 15:44:41 2001
Last Updated by: jwh
Date Last Updated: Fri Jul 20 15:4:41 2001

Actor: User Application

Goal: Find a service

Description: Attempts to locate a service locally, for a peer, or for a peer group

Preconditions:

  1. The engine must be started.
Post conditions:

None

Priority: High

Related Use Cases:

UC22.0 - Invoke Network Service
UC23.0 - Invoke Network Service (Async)
UC24.0 - Cancel Service Invocation

Notes and Issues:

None

Event Flow:

  1. The application constructs the search criteria.
  2. The application asks the engine to find all services locally, for a peer, or for a peer group that match the search criteria.
  3. The engine sends the search message to the appropriate peer(s).
  4. For each located service, the engine adds it to an internal list.
  5. After the engine determines the default timeout has elapsed, it returns the service list to the application.
Alternate Flows:

UC31.1 Peer not available

  1. The application constructs the search criteria.
  2. The application asks the engine to find all services locally, for a peer, or for a peer group that match the search criteria.
  3. The engine sends the search message to the appropriate peer.
  4. The engine determines the peer is not available.
  5. The engine informs the application that the peer isn't available.

UC31.2 Peer group not available

  1. The application constructs the search criteria.
  2. The application asks the engine to find all services locally, for a peer, or for a peer group that match the search criteria.
  3. The engine sends the search message to the peer group.
  4. The engine determines the peer group is not available.
  5. The engine informs the application that the peer group isn't available.
Sequence Diagrams:

Event Flow Sequence Diagram

Revision History
Name Date Reason for Change Version
       


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