RDH handles a DDX request - Revision history

Ndp: /* Goal */

2009-04-29T23:40:50Z

Goal

← Older revision		Revision as of 23:40, 29 April 2009
Line 9:		Line 9:
	<font size="-2" color="green">''The goal briefly describes what the user intends to achieve with this use case.''</font>		<font size="-2" color="green">''The goal briefly describes what the user intends to achieve with this use case.''</font>
	<font size="-2" color="red">''Who is the user in question? [[User:Ndp\|ndp]].''</font>		<font size="-2" color="red">''Who is the user in question? [[User:Ndp\|ndp]].''</font>

			Clarify the details of the DDX handling operation: Dispatch, Database interactions, DDS construction etc.

	== Summary ==		== Summary ==

Ndp: /* Goal */

2009-04-29T23:38:39Z

Goal

← Older revision		Revision as of 23:38, 29 April 2009
Line 8:		Line 8:
	== Goal ==		== Goal ==
	<font size="-2" color="green">''The goal briefly describes what the user intends to achieve with this use case.''</font>		<font size="-2" color="green">''The goal briefly describes what the user intends to achieve with this use case.''</font>
			<font size="-2" color="red">''Who is the user in question? [[User:Ndp\|ndp]].''</font>

	== Summary ==		== Summary ==

Ndp: RDH handles get DDX request moved to RDH handles a DDX request

2009-04-29T18:04:22Z

RDH handles get DDX request moved to RDH handles a DDX request

← Older revision	Revision as of 18:04, 29 April 2009
(No difference)

Ndp: /* Resources */

2009-04-29T17:46:39Z

Resources

← Older revision		Revision as of 17:46, 29 April 2009
Line 86:		Line 86:
	\| 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.
	\| ~~N/a~~		\| Hardware running the BES.
	\|-		\|-
	\| ODBC Driver		\| ODBC Driver

Ndp: /* Basic Flow */

2009-04-29T17:44:57Z

Basic Flow

← Older revision		Revision as of 17:44, 29 April 2009
Line 36:		Line 36:
	<font size="-2" color="green">''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)''</font>		<font size="-2" color="green">''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)''</font>

	# The BES receives a request containing bes:get command for a DDX associated with a Data Source in the RDH from a BES client:<tt>		# The BES receives a request containing bes:get command for a DDX associated with a Data Source in the RDH from a BES client:<font color="red">(''How does the BES know the request is for a DDX in the RDH catalog? Will the RDH have it's own catalog? Or will it claim part of the resource URI space? Or something else? [[User:Ndp\|ndp]]'')</font><tt>
	#: <?xml version="1.0" encoding="UTF-8"?>		#: <?xml version="1.0" encoding="UTF-8"?>
	#: <bes:request xmlns:bes="http://xml.opendap.org/ns/bes/1.0#" reqID="[http-8080-1:16:bes_request]">		#: <bes:request xmlns:bes="http://xml.opendap.org/ns/bes/1.0#" reqID="[http-8080-1:16:bes_request]">

Ndp: /* Basic Flow */

2009-04-29T17:36:10Z

Basic Flow

← Older revision		Revision as of 17:36, 29 April 2009
Line 53:		Line 53:
	# The RDH determines which ODBC Data Source is associated with the requested DDX.		# The RDH determines which ODBC Data Source is associated with the requested DDX.
	# The RDH uses the ODBC introspection API to get the structural <font color="red">(''do i mean schema here? [[User:Ndp\|ndp]]'')</font> descriptions of the tables and views held by the ODBC Data Source.		# The RDH uses the ODBC introspection API to get the structural <font color="red">(''do i mean schema here? [[User:Ndp\|ndp]]'')</font> descriptions of the tables and views held by the ODBC Data Source.
	# The RDH instantiates/constructs a DDS class instance in memory that reflects the [[Mapping the ODBC data model to the DAP2 data model \| DAP data model representation of the tables and views]] held by the ODBC Data Source using the information collected in the previous step.		# The RDH instantiates/constructs a DDS class instance in memory that reflects the [[Mapping the ODBC data model to the DAP2 data model \| DAP data model representation of the tables and views held by the ODBC Data Source]] using the information collected in the previous step.
	# The RDH applies any constraint expression to the in memory DDS. (marks all of the projected variables).		# The RDH applies any constraint expression to the in memory DDS. (marks all of the projected variables).
	# The RDH uses the DDS instance to serialize it's constrained DDX representation back to the BES client.		# The RDH uses the DDS instance to serialize it's constrained DDX representation back to the BES client.

Ndp: /* Basic Flow */

2009-04-29T17:35:45Z

Basic Flow

← Older revision		Revision as of 17:35, 29 April 2009
Line 53:		Line 53:
	# The RDH determines which ODBC Data Source is associated with the requested DDX.		# The RDH determines which ODBC Data Source is associated with the requested DDX.
	# The RDH uses the ODBC introspection API to get the structural <font color="red">(''do i mean schema here? [[User:Ndp\|ndp]]'')</font> descriptions of the tables and views held by the ODBC Data Source.		# The RDH uses the ODBC introspection API to get the structural <font color="red">(''do i mean schema here? [[User:Ndp\|ndp]]'')</font> descriptions of the tables and views held by the ODBC Data Source.
	# The RDH instantiates/constructs a DDS class instance in memory that reflects the ~~<u>~~DAP data model representation of the tables and views~~</u>~~ held by the ODBC Data Source using the information collected in the previous step.		# The RDH instantiates/constructs a DDS class instance in memory that reflects the [[Mapping the ODBC data model to the DAP2 data model \| DAP data model representation of the tables and views]] held by the ODBC Data Source using the information collected in the previous step.
	# The RDH applies any constraint expression to the in memory DDS. (marks all of the projected variables).		# The RDH applies any constraint expression to the in memory DDS. (marks all of the projected variables).
	# The RDH uses the DDS instance to serialize it's constrained DDX representation back to the BES client.		# The RDH uses the DDS instance to serialize it's constrained DDX representation back to the BES client.

Ndp: /* Preconditions */

2009-04-29T17:25:14Z

Preconditions

← Older revision		Revision as of 17:25, 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]]
			# The RDBMS database with tables and/or views associated with the Data Source associated with the requested DDX is available.

	== Triggers ==		== Triggers ==

Ndp: /* Post Conditions */

2009-04-29T17:22:34Z

Post Conditions

← Older revision		Revision as of 17:22, 29 April 2009
Line 59:		Line 59:
	== 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: /* Resources */

2009-04-29T17:21:15Z

Resources

@@ Line 77: / Line 77: @@
 |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>
+| N/a
 |}