You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Current »

The DM Technical Control Team has responsibility for issues similar to those of the LSST Configuration Control Board, but restricted to those contained within the DM subsystem. The TCT reviews and approves changes to all baselines in the LSST Data Management System, including proposed changes to the DM System Requirements' (DMSR), reference design, sizing model, i.e. any LDM-xxx baselined document.  The TCT makes sure these changes don't get into the baseline without proper change control.  Note that the TCT does not author the Technical Baseline and has no specific technical deliverable charter, but it does validate that the form and content of the Technical Baseline is consistent with LSST project standards such as the System Engineering Management Plan (SEMP).  Specific responsibilities for development of the Technical Baseline and evaluation of the content versus LSST and DM requirements are defined in the LSST Organization and Charter (LDM-294).

  • Charter/purpose
    • Ensure that the DM Technical Baseline (LDM-xxx) documents are baselined and once baselined only changed when necessary, according to LSST and DM configuration control processes

  • Membership
    • Co-Chaired by the DM Project Manager and DM Project Scientist
    • Members include the DM System Architect, DM System Interfaces Scientist, DM SQuaRE Technical Manager
    • For on-line virtual meetings, if a quorum is not reached within one week, the DM Project Manager and the DM Project Scientist will make a unilateral decision

  • Responsibilities
    • Determines when specification and deliverables are of sufficient maturity and quality to be baselined (placed under configuration controlled status) or released. The TCT reviews and approves proposed changes to baselined items.
    • Reviews and approves/rejects proposed changes to baselined items
Meetings and Notices  

The TCT meets whenever a request is made for approval to change baseline

  See the TCT Meetings and Notices for the record of decisions taken.  Note that in R&D, the TCT was responsible for the baselining of software libraries and standards and many decisions are noted about this, but this has since then been delegated to the DM System Architect.

Initiating a Request for a Baseline Change 

The detailed process from start-to-finish is covered in Baseline Change Control.

To start the chain of events, the interested party creates an RFC describing the proposed change, refer to:

Discussion and Decision Making Process

 


  • No labels