Requirements and Design Hierarchy

Contents

Change Control

All LPM- and LSE- prefix documents are managed by the LSST Change Control Board using the change control process described in LPM-19.  All LDM- prefix documents are managed by the DM Technical Control Team using the DM Discussion and Decision Making Process (in particular noting section 3).

If small issues (problems) relevant to DM are noted in any of these documents, JIRA tickets may be filed against the "Requirements Documents" or "Design Documents" components in the DM project.  If larger changes to the documents are thought to be necessary, a JIRA ticket should be filed in the RFC project (with component "DM"); this can be escalated to an LSST Change Request (LCR) if need be.

Some documents are under active development.  Links to relevant work areas are provided below.

Requirements Hierarchy

These documents are written in scientific language with embedded specifications.

These documents are more formal.  They are written in requirements language with source in Enterprise Architect (EA) and traceability matrices.

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.

Interface Control Documents and Support Documents (Collection-5201)

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.

(The full set of LSST system-level ICDs, not just those involving DM, should be available at Collection-2807.)

DM Design Baseline (Collection-2511)

These documents describe the baseline design of the DM subsystem at a high level.  They are written in prose.

These documents describe the baseline design of the major components of the DM subsystem.  They are also written in prose.  Some of these are in the process of being converted from Word to reStructured Text managed through GitHub and published through readthedocs.org in more-easily linkable form – although note that the official baseline version will always be in DocuShare.

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.  This has also been converted to reStructured Text.  A more comprehensive document developed by the NCSA team is expected to replace this one soon.

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.

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.