Requirements Hierarchy
These documents are written in scientific language with embedded specifications.
Document | Title | Notes |
---|---|---|
LPM-17 | Science Requirements Document | The fundamental, overall science goals of the project |
LSE-163 | LSST Data Products Definition Document | The data products that are the end deliverables to scientists |
These documents are more formal. They are written in requirements language with source in Enterprise Architect (EA) and traceability matrices.
Document | Title | Notes |
---|---|---|
LSE-29 | LSST Systems Requirements | The top-level formal system requirements |
LSE-30 | Observatory System Specification | Requirements and budgets based on the high-level design |
LSE-61 | Data Management System Requirements | Flowed-down requirements for the Data Management subsystem |
High-Level Operations Plans
These documents describe in prose how various aspects of operating the system will work, including some implicit requirements on the behavior of the system.
Document | Title | Notes |
---|---|---|
Operations Concept Document | In work in EA, not yet published | |
LSE-79 | Commissioning Plan | |
Calibration Plan | In work, not yet published |
Interface Control Documents and Support Documents (Collection-2807)
These documents are intended to comply with LSE-151, the Interface Control & Compliance Management Process. The control documents are written in requirements language with source in EA. The support documents, marked with "(S)", tend to be written in prose.
Document | Title | Notes |
---|---|---|
LSE-69 | Interface between the Camera and Data Management | Camera events and telemetry |
LSE-68 | Camera Data Acquisition Interface | Camera image data |
LSE-130 (S) | Support-Data Exchanges between Data Management and Camera | Camera as-built information provided to DM |
LSE-75 | Control System Interfaces between the Telescope & Data Management | Pointing and WCS feedback to the telescope |
LSE-76 | Infrastructure Interfaces between the Summit Facility and Data Management | Minimal, mostly networking now |
LSE-77 | Infrastructure Interfaces Between Data Management and the Base Facility | Base site |
LSE-239 (S) | Base Facility Data Center Design Requirements | Specifications prepared for design/build contractor |
LSE-78 (S) | LSST Observatory Network Design | Summit and Base LANs and WAN |
LSE-72 | OCS - Data Management Software Communication Interface | DM OCS-visible devices/components and EFD archiving |
LSE-70 (S) | LSST Observatory Control System Communication Architecture and Protocol | OCS middleware communications |
LSE-209 | Software Component to OCS Interface Control Document | States and commands for OCS-visible devices/components |
LSE-74 (S) | System Dictionary and Telemetry Streams | |
LSE-131 | Interface between Data Management and EPO | |
LSE-140 | Auxiliary Instrumentation Interface between Data Management and Telescope | Calibration spectrometer, dome screen, etc. |
DM Design Baseline (Collection-2511)
These documents describe the baseline design of the DM subsystem at a high level. They are written in prose.
Document | Title | Notes |
---|---|---|
LDM-148 | Data Management System Design | |
LDM-132 | Data Management WBS Dictionary | The descriptions in this document tend to be very general; the boundaries are not necessarily clearly drawn. See also the UML use cases below. |
These documents describe the baseline design of the major components of the DM subsystem. They are also written in prose.
Document | Title | Notes |
---|---|---|
LDM-151 | Data Management Applications Design | |
LDM-152 | Data Management Middleware Design | Design at the application isolation and control level |
LDM-135 | Data Management Database Design | Design of the distributed and non-distributed databases containing data products and internal management data |
LDM-153 | Data Management Database Baseline Schema | Notional schemas for the various databases |
LDM-129 | Data Management Infrastructure Design | Design at the hardware and system services level |
LDM-130 | LSST SUI Requirements | In work, current published draft is obsolete |
LDM-131 | Data Management SUI Conceptual Design | |
LDM-156 | Moving Object Pipeline System Design | Probably should not be change-controlled |
Detailed DM Operations Documents (Collection-2511)
The following prose document outlines how various components within the DM subsystem are expected to work in operations, especially in conjunction with other parts of the LSST system.
Document | Title | Notes |
---|---|---|
LDM-230 | Automated Operation of the LSST Data Management System |
Detailed DM Design Documents
Most of these documents are in Confluence here. Some are still in Trac. One, LDM-156 Moving Object Pipeline System Design, is in DocuShare and change-controlled although it probably should not be.
DM Sizing Model (Collection-2511)
These Excel spreadsheets and accompanying prose explanatory documents model the structure, capabilities, capacities, and costs of the DM system.
Document | Title | Notes |
---|---|---|
LSE-81 | LSST Science and Project Sizing Inputs | Requirements from the project level and science-based models |
LSE-82 | LSST Science and Project Sizing Inputs Explanation | |
LDM-138 | Data Management Compute Sizing Model | Derives computing cycles needed based on models of algorithmic processing and estimates based on prototypes |
LDM-140 | Data Management Compute Sizing Explanation | |
LDM-141 | Data Management Storage Sizing and I/O Model | Derives terabytes and gigabytes per second needed based on models of data product storage and retrieval and estimates based on prototypes |
LDM-139 | Data Management Storage Sizing and I/O Explanation | |
LDM-142 | Network Sizing Model | |
LDM-144 | Site Specific Infrastructure Estimation Model | Derives machine details and costs based on compute and storage and network requirements derived in the above spreadsheets |
LDM-143 | Site Specific Infrastructure Estimation Explanation |
DM UML Use Cases (Collection-2511)
These documents, with source in EA, were used for doing initial cost estimates of the DM system and components. They have not been updated as responsibilities have moved between WBS items or as functions have been reallocated, but they do still represent activities that will occur and may help provide some understanding about what different WBS elements are expected to do.