This page is obsolete, and the Science/Architecture Team has been disbanded. For successor organizations, refer to:

For the overall DM management structure, refer to LDM-294.

Science/Architecture Team (SAT)

The Data Management Science/Architecture Team (SAT) is chaired by the Data Management System Architect and Project Scientist. The SAT is the DM-wide body that is charged with addressing issues of the overall requirements flowdown, architecture, and organization of the design of Data Management, both for the final LSST design and for the Data Challenges.

The designs and other high-level outputs of the SAT become part of the technical baselines for Data Management in the LSST project and for the Data Challenges. Approval and change control for these baselines are managed by the DM Technical Control Team (TCT).


  • Support DM System Architect in ensuring that the DMS meets science requirements
  • Support DM Project Scientist in ensuring DMS has overall scientific integrity
  • Control all DMS internal and external interfaces
  • Perform or delegate due diligence for proposed technical baseline changes; then recommend changes (or no action) to the TCT
  • Decide issues involving internal, non-change-controlled DM architecture and design


  • Co-Chaired by the DM System Architect (Kian-Tat Lim), DM Project Scientist (Mario Juric)
  • Core Members are Institutional Scientific/Technical Leads, currently:
    • Jacek Becla (SLAC Technical)
    • David Ciardi (IPAC Science)
    • Andy Connolly (UW Science/Technical)
    • Gregory Dubois-Felsmann (Interface Scientist and SLAC Science)
    • Mike Freemon + Don Petravick (NCSA Science/Technical)
    • Ron Lambert (NOAO Technical)
    • Robert Lupton (Princeton Science/Technical)
    • Xiuqin Wu (IPAC Technical)


  • Meets at start of each software development phase with DMLT to establish detailed scope/work plan
  • Meets with DMLT for change control (TCT)
  • Supports the System Architect's role in the systems engineering process, notably in the establishment and review of interface requirements and Interface Control Documents with the other LSST subsystems
  • Conducts (or delegates) design reviews and code reviews during the LSST development process
  • Endeavors to instill a productive and ethical engineering culture within DM
  • Commissions Working Groups
    • Working groups are architectural (e.g. Applications, Middleware, Database, Infrastructure, Operations), span subsystems
    • Chaired by a member of the Science/Architecture Team
    • Members include other technical personnel, possibly including outside collaborators


The SAT currently meets weekly. The meetings are not closed, but they are intended as working meetings of the team, to which others will be specifically invited as relevant topics arise on the team's agenda.

Requests to update the DM technical baseline (by adding a new required package, upgrading the version of an existing package, changing our development process, or making non-trivial changes to an LDM-XXX change-controlled document) or proposing a significant new design or interface to be reviewed (e.g. something affecting multiple packages), should be added to the agenda of the next SAT weekly meeting by filing a JIRA issue in the Data Management project with component "SAT".  (Urgent issues may be acted on between weekly meetings if necessary.)

(Information below this point was transferred from Trac and may be outdated.)

Design Reviews and Planning

One of the core functions of the SAT is to carry out design reviews.


The System Architect is currently spending some amount of time looking at the performance of the DC3b DM software. This work is summarized here:

LSST Systems Engineering

The System Architect is developing, within the LSST Systems Engineering SysML model (LSST_SysArch), the requirements and specifications for interfaces with other LSST subsystems, and is involved in the management of these and other dependencies that cross subsystem boundaries.

  • No labels