5.1 C&C Pipe-and-Filter View Packet 1: The ECS System
5.1.1 Primary Presentation
5.1.2 Element Catalog
126.96.36.199 Elements and Their Properties
Properties of ECS filter components, given in the following table, are
|All data interactions within the ECS are performed against Earth Science Data Types (ESDTs). An ESDT is the logical object that describes both the inventory holdings for particular data and the services (insert, acquire, and so on) that can be applied to that data. Before a user (including DAAC operations) can perform any data services against a data set in the ECS, the ESDT for that data type must be installed. Installation includes defining the collection level and granule level metadata in the inventory (Science Data Server), advertising the data type and its services, defining metadata attribute valids in the Data Dictionary, and defining subscribable data events.
|Science Software Integration & Test (SSI&T) is the process by which Instrument Team developed algorithms get qualified for use in the ECS production environment. Much of this process is algorithm specific and/or manual or semiautomatic. These aspects are not dealt with in this document. However, the reception of the original algorithm package (Delivered Algorithm PackageDAP) and the qualified algorithm package (Science Software Archive PackageSSAP) are automated tasks.
|Once the ESDT is defined, and any production algorithms have been integrated, then the ECS is ready to accept data and generate higher-level products.
|There are a number of ways in which data can be requested in the ECS. If the product exists in the archive, then a user can simply request it for distribution. If the product doesn't exist, but the algorithms for producing the product have been integrated, then the user can request production. Alternatively if the product exists, but has been generated with a set of runtime algorithms different from those desired, then the user can request that the product be reprocessed.
|Many products are produced automatically upon the availability of the necessary input data. But in addition to this "standard" production, the ECS also has the capability to produce products on demand in response to a user request.
|An important feature of the ECS is the ability to reprocess data when either the original production data or algorithm were faulty, or if another user needs different execution parameters.
|Once data is generated or ingested into the ECS, it is made available to other users. The distribution system provides for a flexible data delivery system that can provide data either automatically based on preestablished event triggers, or by direct request.
188.8.131.52 Relations and Their Properties
The only relation in the pipe-and-filter view is attachment, between pipes and filters. It is as shown in the primary presentation.
184.108.40.206 Element Interfaces
220.127.116.11 Element Behavior
5.1.3 Context Diagram
5.1.4 Variability Guide
5.1.5 Architecture Background
5.1.6 Other Information
5.1.7 Related View Packets
- Module Decomposition View Packet 1: The ECS System (Volume II, Section 1.1, page 414)
- Module Layered View Packet 1: The ECS System (Volume II, Section 4.1, page 435)
- Allocation Deployment View Packet 1: The ECS System (Volume II, Section 8.1, page 457)
- Allocation Implementation View Packet 1: The ECS System (Volume II, Section 9.1, page 461)
- Allocation Work Assignment View Packet 1: The ECS System (Volume II, Section 10.1, page 464)
An implementation refinement of the pipe-and-filter view is the C&C Shared-Data View (Volume II, Chapter 6).
Software Architectures and Documentation
Part I. Software Architecture Viewtypes and Styles
The Module Viewtype
Styles of the Module Viewtype
The Component-and-Connector Viewtype
Styles of the Component-and-Connector Viewtype
The Allocation Viewtype and Styles
Part II. Software Architecture Documentation in Practice
Documenting Software Interfaces
Choosing the Views
Building the Documentation Package
Other Views and Beyond
Rationale, Background, and Design Constraints