Data Model and Data Access Architecture in the Geophysical Monitoring System
Abstract not provided.
Abstract not provided.
Abstract not provided.
Abstract not provided.
Abstract not provided.
Abstract not provided.
This document describes a conceptual Data Model for use in the IDC Re-Engineering development project.
Abstract not provided.
Abstract not provided.
SNL’s IDC Reengineering Phase 2 team developed 12 Use Case Realizations (UCRs) during the Elaboration phase. This document describes the changes made to these UCRs after their initial delivery to the IDC.
This document describes a conceptual Data Model for use in the IDC Re-Engineering development project.
This document contains 4 use case realizations generated from the model contained in Rational Software Architect. These use case realizations are the current versions of the realizations originally delivered in Elaboration Iteration 3.
This document contains 4 use case realizations generated from the model contained in Rational Software Architect. These use case realizations are the current versions of the realizations originally delivered in Elaboration Iteration 2.
This document contains 4 use case realizations generated from the model contained in Rational Software Architect. These use case realizations are the current versions of the realizations originally delivered in Elaboration Iteration 1.
This document contains 4 use case realizations generated from the model contained in Rational Software Architect.
This architecturally significant use case describes how the System acquires meteorological data to build atmospheric models used in automatic and interactive processing of infrasound data. The System requests the latest available high-resolution global meteorological data from external data centers and puts it into the correct formats for generation of infrasound propagation models. The system moves the meteorological data from Data Acquisition Partition to the Data Processing Partition and stores the meteorological data. The System builds a new atmospheric model based on the meteorological data. This use case is architecturally significant because it describes acquiring meteorological data from various sources and creating dynamic atmospheric transmission model to support the prediction of infrasonic signal detections.
Abstract not provided.
This architecturally significant use case describes how the System acquires meteorological data to build atmospheric models used in automatic and interactive processing of infrasound data. The System requests the latest available high-resolution global meteorological data from external data centers and puts it into the correct formats for generation of infrasound propagation models. The system moves the meteorological data from Data Acquisition Partition to the Data Processing Partition and stores the meteorological data. The System builds a new atmospheric model based on the meteorological data. This use case is architecturally significant because it describes acquiring meteorological data from various sources and creating dynamic atmospheric transmission model to support the prediction of infrasonic signal detection
This report contains a draft Component Interface Specification (CIS) for an application controlling signal detection calculations. It is an example of the contents and level of detail of information in a CIS. The classes, interfaces, and data types in this report reflect current understanding of system concepts and potential implementation patterns but should not be interpreted as containing the finalized interface specifications, classes, etc. The primary purpose of this report is to discuss the potential OSD APIs represented in class diagrams for the Waveform, QC Mask, and Signal Detection Repository interfaces.
This report contains a draft Component Interface Specification (CIS) for a signal detector. It is an example of the contents and level of detail of information in a CIS. The classes, interfaces, and data types in this report reflect current understanding of system concepts and potential implementation patterns but should not be interpreted as containing the finalized interface specifications, etc.
This initial draft document contains formative data model content for select areas of Re-Engineering Phase 2 IDC System. The purpose of this document is to facilitate discussion among the stakeholders. It is not intended as a definitive proposal.
This document contains 4 use case realizations generated from the model contained in Rational Software Architect.
This document contains the Data Model generated from the model contained in Rational Software Architect.
This initial draft document contains formative data model content for select areas of Re-Engineering Phase 2 IDC System. The purpose of this document is to facilitate discussion among the stakeholders. It is not intended as a definitive proposal.
This initial draft document contains formative data model content for select areas of Re-Engineering Phase 2 IDC System. The purpose of this document is to facilitate discussion among the stakeholders. It is not intended as a definitive proposal.
This initial draft document contains formative data model content for select areas of Re-Engineering Phase 2 IDC System. The purpose of this document is to facilitate discussion among the stakeholders. It is not intended as a definitive proposal.