RDH handles bes:showCatalog request - Revision history

Ndp: /* Resources */

2009-04-29T17:46:46Z

Resources

← Older revision		Revision as of 17:46, 29 April 2009
Line 94:		Line 94:
	\| The data server		\| The data server
	\| Assumed available as it is the framework from within which the RDH operates.		\| Assumed available as it is the framework from within which the RDH operates.
	\| ~~Host system~~ running the BES		\| Hardware running the BES.
	\|}		\|}

Ndp: /* Resources */

2009-04-29T17:46:26Z

Resources

← Older revision		Revision as of 17:46, 29 April 2009
Line 90:		Line 90:
	\|Source System		\|Source System
	\|-		\|-
	\|~~<font size="-2" color="green">''name''</font>~~		\| BES
	\|~~<font size="-2" color="green">''Organization that owns/ manages resource''</font>~~		\| Data Provider
	\|~~<font size="-2" color="green">''Short description of the resource''</font>~~		\| The data server
	\|~~<font size="-2" color="green">''How often~~ the ~~resource is available''</font>~~		\| Assumed available as it is the framework from within which the RDH operates.
	\|~~<font size="-2" color="green">''Name of~~ system ~~which provides resource''</font>~~		\| Host system running the BES
	\|}		\|}

Ndp: /* Post Conditions */

2009-04-29T17:45:32Z

Post Conditions

← Older revision		Revision as of 17:45, 29 April 2009
Line 70:		Line 70:
	== Post Conditions ==		== Post Conditions ==
	<font size="-2" color="green">''Here we give any conditions that will be true of the state of the system after the use case has been completed.''</font>		<font size="-2" color="green">''Here we give any conditions that will be true of the state of the system after the use case has been completed.''</font>

			At the end of the Basic Flow the RDH will have returned to a ready state, awaiting the next transaction.

	== Activity Diagram ==		== Activity Diagram ==

Ndp: /* Triggers */

2009-04-29T17:31:49Z

Triggers

← Older revision		Revision as of 17:31, 29 April 2009
Line 30:		Line 30:
	<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>		<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>

	A client issues a bes:showCatalog command for the Datasets serviced by the RDH.		* A client issues a bes:showCatalog command for the Datasets serviced by the RDH.

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

Ndp: /* Triggers */

2009-04-29T17:31:36Z

Triggers

← Older revision		Revision as of 17:31, 29 April 2009
Line 29:		Line 29:
	== 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>		<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>

			A client issues a bes:showCatalog command for the Datasets serviced by the RDH.

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

Ndp: /* Preconditions */

2009-04-29T17:30:24Z

Preconditions

← Older revision		Revision as of 17:30, 29 April 2009
Line 24:		Line 24:
	== Preconditions ==		== Preconditions ==
	<font size="-2" color="green">''Here we state any assumptions about the state of the system that must be met for the trigger (below) to initiate the use case. Any assumptions about other systems can also be stated here, for example, weather conditions. List all preconditions.''</font>		<font size="-2" color="green">''Here we state any assumptions about the state of the system that must be met for the trigger (below) to initiate the use case. Any assumptions about other systems can also be stated here, for example, weather conditions. List all preconditions.''</font>

			# The BES is installed and configured - including the correct [[Adding the RDH to the BES \| installation and configuration of the RDH]]

	== Triggers ==		== Triggers ==

Ndp: /* Actors */

2009-04-29T17:29:53Z

Actors

← Older revision		Revision as of 17:29, 29 April 2009
Line 18:		Line 18:
	== Actors ==		== Actors ==
	<font size="-2" color="green">''List actors, people or things outside the system that either acts on the system (primary actors) or is acted on by the system (secondary actors). Primary actors are ones that invoke the use case and benefit from the result. Identify sensors, models, portals and relevant data resources. Identify the primary actor and briefly describe role.''</font>		<font size="-2" color="green">''List actors, people or things outside the system that either acts on the system (primary actors) or is acted on by the system (secondary actors). Primary actors are ones that invoke the use case and benefit from the result. Identify sensors, models, portals and relevant data resources. Identify the primary actor and briefly describe role.''</font>


	; client		; client

Ndp: /* Actors */

2009-04-29T17:29:46Z

Actors

← Older revision		Revision as of 17:29, 29 April 2009
Line 18:		Line 18:
	== Actors ==		== Actors ==
	<font size="-2" color="green">''List actors, people or things outside the system that either acts on the system (primary actors) or is acted on by the system (secondary actors). Primary actors are ones that invoke the use case and benefit from the result. Identify sensors, models, portals and relevant data resources. Identify the primary actor and briefly describe role.''</font>		<font size="-2" color="green">''List actors, people or things outside the system that either acts on the system (primary actors) or is acted on by the system (secondary actors). Primary actors are ones that invoke the use case and benefit from the result. Identify sensors, models, portals and relevant data resources. Identify the primary actor and briefly describe role.''</font>


			; client
			: A BES client application

	== Preconditions ==		== Preconditions ==

Ndp: /* Summary */

2009-04-29T17:29:31Z

Summary

← Older revision		Revision as of 17:29, 29 April 2009
Line 11:		Line 11:
	== Summary ==		== Summary ==
	<font size="-2" color="green">''Give a summary of the use case to capture the essence of the use case (no longer than a page). It provides a quick overview and includes the goal and principal actor.''</font>		<font size="-2" color="green">''Give a summary of the use case to capture the essence of the use case (no longer than a page). It provides a quick overview and includes the goal and principal actor.''</font>

			The BES receives a request for a catalog that it identifies as being serviceable by the RDH.

			The RDH uses it's cached list of ODBC Data Sources to build a bes:showCatalog response and then returns the bes:response document to the client.

	== Actors ==		== Actors ==
	<font size="-2" color="green">''List actors, people or things outside the system that either acts on the system (primary actors) or is acted on by the system (secondary actors). Primary actors are ones that invoke the use case and benefit from the result. Identify sensors, models, portals and relevant data resources. Identify the primary actor and briefly describe role.''</font>		<font size="-2" color="green">''List actors, people or things outside the system that either acts on the system (primary actors) or is acted on by the system (secondary actors). Primary actors are ones that invoke the use case and benefit from the result. Identify sensors, models, portals and relevant data resources. Identify the primary actor and briefly describe role.''</font>

Ndp: /* Description */

2009-04-29T17:27:49Z

Description

← Older revision		Revision as of 17:27, 29 April 2009
Line 3:		Line 3:
	== Description ==		== Description ==
	<font size="-2" color="green">''Give a short descriptive name for the use case to serve as a unique identifier.''</font>		<font size="-2" color="green">''Give a short descriptive name for the use case to serve as a unique identifier.''</font>

			The RDH receives and responds to a bes:showCatalog request for the Datasets (ODBC Data Sources) that it is offering.

	== Goal ==		== Goal ==