• Created by Unknown User (robyn), last modified on Apr 28, 2014

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

Compare with Current View Page History

« Previous Version 6 Next »

The DM Technical Control Team has responsibility for issues similar to those of a Configuration Control Board. The TCT reviews and approves changes to all baselines in the LSST Data Management System, including proposed changes to the DM functional requirements' (FRS), reference design, or Data Challenge design baselines, the tools to be used (including third-party packages), and standards and policies. Specifically: 

Membership

The TCT is chaired by the DM System QA and Test Lead. The other members include the DM System Scientist and Lead Institution Project Scientists. 

 Responsibilities 

The TCT 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.

The Technical Control Team and the System Architecture Team work in synchrony. The SAT is responsible for creating, establishing, updating, analyzing, proposing the reference and DC designs and changes to them, whether they might affect the FRS, the reference design, or the DC design. The TCT makes sure these changes don't get into the baseline without proper change control. The TCT must involve PM before approving an FRS change, as this might affect the project schedule or cost envelope. Restated more simply, the FRS is baselined, and the Reference Design are baselined, and so should each DC design be baselined. The SAT defines them, the TCT controls baselining and acceptance of changes to the baseline for all 3.

For further clarification, refer to pre- and post-baseline duties.

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 Baseline Change 

Create a Jira Issue describing the proposed change:

  • The Jira Issue should be referenced to component TCT and directed to developer Unknown User (robyn).
  • Issues which reach the TCT should already have been reviewed by the SAT. Include a reference link to, or the commentary on, the SAT decision.

 


  • No labels