Module Uses View

2.1 Module Uses View Packet 1: The Science Data Processing Segment (SDPS)

2.1.1 Primary Presentation

		SDPS Element	Uses This Element
Science Data Processing Segment
	Ingest Subsystem
	[etc.]	INGST CSCI	ADSRV CSCI in the Interoperability Subsystem
			STMGT CSCI in the Data Server Subsystem
			SDSRV CSCI in the Data Server Subsystem
			DCCI CSCI in the Communications Subsystem
		other CSCIs within the Ingest Subsystem
	Data Server Subsystem
	[etc.]	DDIST CSCI	MCI CSCI in the System Management Subsystem
			DCCI CSCI in the Communications Subsystem
			STMGT CSCI in the Data Server Subsystem
			INGST CSCI in the Ingest Subsystem
		other CSCIs within the Data Server Subsystem
[etc.]	other subsystems within the Science Data Processing Segment

2.1.2 Element Catalog

2.1.2.1 Elements and Their Properties

Properties of ECS modules are

• Name, given in the following table
• Responsibility, given in the following table
• Visibility: all elements are visible outside their parent
• Implementation information: see Volume II, Chapter 9.

The elements in this view are CSCIs, which are subelements of subsystems as defined in the module decomposition view of Chapter 1.[11]

[11] The excerpt of the module decomposition view in Chapter 1 did not delve to the level of CSCIs. A complete decomposition view would have, documenting their responsibilities there. That would make the element catalog here redundant. In a real documentation package, it would probably consist of pointers or hyperlinks to the information in Chapter 1.

Element Name	Responsibility
INGST CSCI	The INGST CSCI supports a variety of interfaces to external systems. The application-level protocol set up for data transfer is potentially different for each of the external interfaces. As a result, a separate ingest software application is required to facilitate data transfer for each interface. To minimize the software development effort and make it easier to accommodate interfaces to new external systems, data ingest from external systems is categorized, based on common characteristics and ingest processes.
ADSRV CSCI	The Advertising Service (ADSRV) CSCI manages Earth Science related advertisements. The advertisement information is stored persistently in a relational Database Management System (DBMS). The Advertising Service data is replicated within each DAAC using Sybase COTS software.
SDSRV CSCI	The Science Data Server (SDSRV) CSCI manages and provides user access to collections of nondocument (non-hard copy) Earth science data; extracts and modifies data by request; accepts browse, search, and retrieval requests from users; and catalogs data insert requests from other SDPS or CSMS CSCIs, CSCs, and processes. The SDSRV CSCI manages Earth science data as logical collections of related data, via interfaces independent of data formats and hardware configurations inherent in underlying storage technologies. The SDSRV manages interactive sessions with service requesters and informs the service requester of the availability of data and services via the IOS.
DCCI CSCI	The DCCI CSCI consists mainly of COTS software and hardware providing servers, gateways, and software library services to other SDPS and CSMS CSCIs.
DDIST CSCI	The Data Distribution (DDIST) CSCI monitors and controls processing for distribution requests. Data Distribution processing consists of directing the STMGT CSCI to place data for distribution in working storage and creating packing lists, and directing the STMGT CSCI to copy data on to hard media or push data as required via FTP, and sending notifications for pulls completed via FTP. Data handled electronically is either pushed via FTP to a user specified location or placed in a directory to be pulled. If data is to be pulled, once the data is ready, the DDIST CSCI sends an electronic message to the user providing the required information for the user to pull the data. If data is to be distributed via hard media, a complete packing list is generated as well as an inventory list for each hard media generated. The DDIST CSCI has a GUI interface with the administration/operations staff (Admin. /Ops). The GUI provides error conditions and status to operations staff and enables the operations staff to set parameters and control operations including suspending, canceling, and resuming requests, changing the priorities of requests, changing the media type, performing multiple selects, and setting threshold sizes. The DDIST CSCI provides limited automatic error response by suspending requests when most errors are encountered. The hard media types supported are 8mm tape, D3 tape, CD-ROM, and Digital Linear Tape (DLT).
MCI CSCI	The Management Software CSCI (MCI) provides distributed system management support capabilities in the fault, configuration, accountability, performance, and security service areas.
STMGT CSCI	The Storage Management (STMGT) CSCI stores/archives, manages, and retrieves nondocument Earth science data and provides a user-friendly graphical user interface (GUI) for operations. The STMGT CSCI manages all physical storage resources for all the DSS CSCIs and processes including tape robotic archive, RAID disk cache, online storage, and peripheral devices used for ingesting data from and distributing data to hard media such as various hard media sizes or drive types.
[etc.]	[etc.]

2.1.2.2 Relations and Their Properties

The relation type in this view is uses. An element uses another element if the correctness of the first depends on a correct implementation of the second being present. It is not enough for an element to invoke another element; if the behavior of the invoked element does not affect the correctness of the invoking element, it is not used. Similarly, an element may use another element that it does not invoke, if it relies on that element to take an action or to perform a function autonomously.

There are no exceptions or additional uses relations among the elements in this view packet beyond those shown in the primary presentation.

2.1.2.3 Element Interfaces

Interfaces for the elements shown in this view are specified under the corresponding elements in the module decomposition view (Volume II, Chapter 1).

2.1.2.4 Element Behavior

Not applicable.

2.1.3 Context Diagram

The context for this view packet is established by the context diagram shown on page 420 as part of the module decomposition view.

2.1.4 Variability Guide

None.

2.1.5 Architecture Background

[omitted]

2.1.6 Other Information

[omitted]

2.1.7 Related View Packets

• Parent: None in this view. View packets in other views whose scope is the entire system could be considered beyond views parents. They include

  - 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)

  - C&C Pipe-and-Filter View Packet 1: The ECS System (Volume II, Section 5.1, page 439)

  - 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)

• Children: None.[12]

  [12] There may well be finer-grained uses relations shown for a large system such as this one, in which case those view packets would be children of this one.

• Siblings

  - Module Uses View Packet 2: The Communications and System Management Segment (CSMS), (Volume II, Section 2.2, page 430)

  - Module Uses View Packet 3: The Flight Operations Segment (FOS), (Volume II, Section 2.3, page 430)

2.2 Module Uses View Packet 2: The Communications and System Management Segment (CSMS)

[omitted]

2.3 Module Uses View Packet 3: The Flight Operations Segment (FOS)

[omitted]