13.07.2015 Views

download as a pdf - Southern California Coastal Ocean Observing ...

download as a pdf - Southern California Coastal Ocean Observing ...

download as a pdf - Southern California Coastal Ocean Observing ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Part II. Ph<strong>as</strong>ed Implementation Plan for DMACSection 1. Functional RequirementsThis document states high-level functional requirements for the Data Management and Communications(DMAC) Subsystem of the Integrated <strong>Ocean</strong> <strong>Observing</strong> System (IOOS). The intendeduse of this document is to supplement the white papers that describe the DMAC subsystems (PartIII of this document) and to rephr<strong>as</strong>e the notions into the formal terminology of a requirementsspecification. The use of the term “requirements” is consistent with that used by the InternationalCouncil on Systems Engineering. 1 As described in the Handbook, this section also is intended “toestablish a datab<strong>as</strong>e of b<strong>as</strong>eline system requirements derived from the source, to serve <strong>as</strong> a foundationfor later refinement and/or revision by subsequent functions in the Systems Engineering processand for a non-ambiguous and traceable flow down of source requirements to the system segments.”2 This section includes requirements of the following types:• Program requirements• Mission requirements• Customer specified constraints• Functional requirements• System requirements• Interface, environmental, and non-functional requirements• Unclear issues discovered in the requirements analysis processThis section is written at a level that primarily addresses mission and customer requirements, alongwith high-level functional and system requirements. It is intended that this section serve <strong>as</strong> an <strong>as</strong>setto be used in subsequent engineering efforts to articulate the detailed system and interface requirementsthat are required to develop a DMAC.GENERAL REQUIREMENTS1. IOOS DMAC Vision1.1. The DMAC Subsystem of the IOOS will knit together the distributed components of IOOSinto a nationwide whole that functions <strong>as</strong> a unified component within the international GOOSframework. The vision for the DMAC Subsystem is not limited to the ingesting and archivingof observations; it includes the data and communications components needed to move dataamong systems and users in a distributed environment. The DMAC Subsystem will be requiredto link observations collected from a broad range of platforms: buoys, drifters, autonomousvehicles, ships, aircraft, satellites, and cabled instruments on the sea floor. Observations1Systems Engineering Handbook, International Council on Systems Engineering, 2000.2Ibid.53

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!