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

Compare with Current View Page History

« Previous Version 15 Next »

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, etc., i.e. any LDM-xxx baselined document.  The TCT makes sure these changes don't get into the baseline without proper change control. The TCT votes to approve any requirements changes, as these might affect the project schedule or cost envelope.

  • Charter/purpose
    • Ensure that all deliverables are baselined and once baselined only changed when necessary, according to LSST and DM configuration control processes
    • Verifies that specifications and deliverables are of sufficient maturity and quality, and of acceptable impact to cost and schedule, to be baselined (placed under configuration controlled status)
  • 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 PM and the DM PS will make a unilateral decision

  • Responsibilities 
    • Reviews and approves/rejects proposed changes to baselined items
    • 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.
    • Meets at least monthly and more often during periods prior to major reviews and data releases or when there exist urgent requests for approval to change baseline
Meetings and Notices  

The TCT meets at least monthly, and more often during periods prior to major reviews and data challenge integrations, or when developers request expedited approval to change the baseline.  See the TCT Meetings and Notices for the record of decisions taken.

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