HAI Use Case: Terminate specific BES processes/connections
Point Of Contact: Nathan Potter
Description
The Administrator (Admin) uses the HAI to terminate specific BES processes.
Goal
By allowing the Admin to terminate BES processes we enable a human to easily clean up hung or damaged BES connections/processes.
Summary
Once the Administrator selects a BES that's connected to the instance of Hyrax that is being managed they can choose a BES processes to terminate.
Actors
- Administrator
- HAI
- Hyrax
- BES
Preconditions
- The Administrator has an authentication privileges for an HAI.
Triggers
For reasons not specified here, an Admin needs to stop a BES process/connection.
Basic Flow
- The Admin logs into the HAI
- The Admin chooses a BES and views it's processes/connections.
- The Admin chooses a BES process/connection to terminate.
- The Admin clicks a button to terminate the selected process/connection.
- The page (or fragment thereof) is refreshed to show the updated list of BES processes/connections.
Alternate Flow
Here we give any alternate flows that might occur. May include flows that involve error conditions. Or flows that fall outside of the basic flow.
Post Conditions
The BES process indicated by the Admin has been terminated.
Activity Diagram
Here a diagram is given to show the flow of events that surrounds the use case.
Notes
There is always some piece of information that is required that has no other place to go. This is the place for that information.
Resources
In order to support the capabilities described in this Use Case, a set of resources must be available and/or configured. These resources include data and services, and the systems that offer them. This section will call out examples of these resources.
| Resource | Owner | Description | Availability | Source System |
| name | Organization that owns/ manages resource | Short description of the resource | How often the resource is available | Name of system which provides resource |
