HAI Use Case: Administrator Logs into the Hyrax Admin Interface: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
Line 20: Line 20:


== Triggers ==
== Triggers ==
<font size="-2" color="green">''Here we describe in detail the event or events that brings about the execution of this use case. Triggers can be external, temporal, or internal. They can be single events or when a set of conditions are met, List all triggers and relationships.''</font>
One or more of:
* Hyrax needs re configuration.
* Hyrax needs to be restarted.
* The Administrator needs/wants to view the Hyrax logs.


== Basic Flow ==
== Basic Flow ==

Revision as of 14:55, 8 November 2010

Point Of Contact: Nathan Potter

Description

The administrator logs into the Hyrax Admin Interface.

Goal

Provide a secure login and session for Administrators to operate the Hyrax Admin Interface.

Summary

The Administrator uses a web browser to access the URL for the Hyrax Admin Interface. When accessed the server returns a secure authentication challenge. Once the Administrator has provided correct authentication credentials all subsequent interactions with the HAI are secure (encrypted) until the session times out or the Administrator logs off.

Actors

  • Administrator

Preconditions

The Administrator has access too, and authentication credentials for, a running Hyrax server.

Triggers

One or more of:

  • Hyrax needs re configuration.
  • Hyrax needs to be restarted.
  • The Administrator needs/wants to view the Hyrax logs.

Basic Flow

Often referred to as the primary scenario or course of events. In the basic flow we describe the flow that would be followed if the use case where to follow its main plot from start to end. Error states or alternate states that might be highlighted are not included here. This gives any browser of the document a quick view of how the system will work. Here the flow can be documented as a list, a conversation or as a story.(as much as required)

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

Here we give any conditions that will be true of the state of the system after the use case has been completed.

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