Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "COSMOS Design 209234"

(New page: = '''Change History''' = {|{{BMTableStyle}} !align="left"|Name: !align="left"|Date: !align="left"|Revised Sections: |- |Sheldon Lee-Loy |12/12/2007 |<ul><li>Initial version</li></ul> |}...)
(No difference)

Revision as of 01:51, 13 December 2007

Change History

Name: Date: Revised Sections:
Sheldon Lee-Loy 12/12/2007
  • Initial version

Workload Estimation

Rough workload estimate in person weeks
Process Sizing Names of people doing the work
Design
Code
Test
Documentation
Build and infrastructure
Code review, etc.*
TOTAL

'* - includes other committer work (e.g. check-in, contribution tracking)

Requirement

Error handling is required between the data visualization components (outputters, ODAs) and data collection components (management domain, brokers and data managers).

Design

Data visualization components interact with the data collection components through end point references (EPRs). Web client classes are created that allow the data visualization outputters and ODAs to send SOAP request to various data collection components. This architecture is illustrated below:

Dv dc interaction.gif

The Web client classes will catch soap faults that will be wrapped as java exceptions. Data visualization components will c

Implementation

Back to the top